clay-performance-tuning

Optimize Clay table enrichment throughput, reduce processing time, and improve hit rates. Use when experiencing slow enrichment, poor email find rates, or needing to process large tables efficiently. Trigger with phrases like "clay performance", "optimize clay", "clay slow", "clay throughput", "clay fast enrichment", "clay batch optimization".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured tuning guide with concrete code and specific thresholds, but the full inline implementations make it verbose and it lacks explicit validation checkpoints for its batch operations. No bundle files are provided, so progressive disclosure rests entirely on section organization.

Suggestions

Add a verification checkpoint after the tuning steps (e.g., re-measure rows/sec and hit rate, compare before/after, revert if no improvement) to close the batch-operation feedback loop and lift workflow clarity.

Move the complete preProcessForClay and scheduler TypeScript implementations into a scripts/ or references/ file, keeping only the key logic and the usage line in SKILL.md, to improve both conciseness and progressive disclosure.

Tighten the 'Why order matters' and rule-of-thumb commentary to one line each so the body assumes Claude's competence without losing the Clay-specific insight.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and the Clay-specific facts (sequential column processing, provider speeds, credit math) earn their place, but the full ~70-line preProcessForClay TypeScript implementation and complete YAML blocks could be tightened; not every token earns its place.	2 / 3
Actionability	Provides executable TypeScript functions, concrete YAML configs, and copy-paste Clay formulas ('ISNOTEMPTY(domain) AND ISNOTEMPTY(first_name) AND ISNOTEMPTY(last_name)') plus a specific error table with numeric thresholds (>10s/row, <40% hit rate).	3 / 3
Workflow Clarity	Six steps are clearly sequenced (Step 1-6) with an error-handling table, but for batch table-enrichment operations there is no explicit validation/verification checkpoint (e.g., confirm hit-rate or processing-time improved after changes), capping the score at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	Sections are well-organized and external references (Clay University URLs, the clay-cost-tuning pointer) are clearly signaled one level deep, but no bundle files exist and substantial inline content (full code implementations, detailed tables) that could be split into reference files keeps everything in one monolithic file.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities, gives an explicit 'Use when' trigger clause, and lists natural trigger phrases scoped to a distinct Clay-specific niche. No first/second-person voice or vague fluff to penalize.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('Optimize Clay table enrichment throughput, reduce processing time, and improve hit rates') tied to a named domain, matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (the three optimization actions) and when ('Use when experiencing slow enrichment, poor email find rates, or needing to process large tables efficiently') with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Six natural phrases a user would actually say ('clay performance', 'optimize clay', 'clay slow', 'clay throughput', 'clay fast enrichment', 'clay batch optimization') give good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Clay-specific niche and Clay-prefixed trigger phrases make it unlikely to fire for an unrelated skill; clearly distinguishable.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clay-pack/skills/clay-performance-tuning/SKILL.md
Commit: 4c47e33

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.