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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with concrete Clay-specific code, settings, and syntax, but is held back by verbosity in full code listings, absent validation checkpoints for its batch operations, and a monolithic structure with no progressive file disclosure.

Suggestions

Add explicit verification checkpoints to the workflow (e.g., 'After reordering columns and adding conditional rules, run a 100-row sample and compare hit rate and credits consumed before/after') to lift workflow_clarity above 2.

Tighten the two TypeScript examples to minimal illustrative snippets, or move the full preProcessForClay and scheduler implementations into a scripts/ file referenced one level deep, improving both conciseness and progressive_disclosure.

Split detailed reference material (the column-speed table, waterfall-depth configs, error-handling table) into a references/ file linked from a concise overview, enabling progressive_disclosure to reach the score-3 anchor.

Dimension	Reasoning	Score
Conciseness	The ~215-line body is mostly efficient and free of basic-concept padding, but two full TypeScript implementations (pre-processing function with interfaces plus usage, and the scheduler) are more than needed to convey the pattern and could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript, real Clay formula syntax ('ISNOTEMPTY(domain) AND ISNOTEMPTY(first_name)'), concrete provider lists ('apollo, hunter'), and copy-paste-ready YAML configs — matching the score-3 anchor for executable, specific guidance.	3 / 3
Workflow Clarity	Steps 1–6 are clearly numbered, but the skill involves batch operations (large-table processing, CRM pushes) with no explicit validation/verification checkpoints such as measuring hit rate before/after or confirming credit savings, which caps workflow clarity at 2 per the rubric's batch-operation guideline.	2 / 3
Progressive Disclosure	Sections are well-organized, but no bundle files exist and all content — including full code implementations that could live in scripts/ — is inline in a 215-line monolithic SKILL.md with no one-level-deep file references, so it does not reach the score-3 'appropriately split' anchor.	2 / 3
	Total	9 / 12 Passed

Description

100%

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, well-crafted description that concretely states capabilities, supplies explicit 'Use when' triggers and a list of natural trigger phrases, and occupies a distinct niche unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — 'Optimize Clay table enrichment throughput, reduce processing time, and improve hit rates' — matching the score-3 anchor for multiple specific actions; imperative voice matches the rubric's good examples so no voice penalty applies.	3 / 3
Completeness	Explicitly answers both what ('Optimize Clay table enrichment throughput...') and when ('Use when experiencing slow enrichment, poor email find rates, or needing to process large tables efficiently') with explicit trigger guidance, so it is not capped at 2 for a missing 'Use when' clause.	3 / 3
Trigger Term Quality	Provides six natural phrases users would say — 'clay performance', 'optimize clay', 'clay slow', 'clay throughput', 'clay fast enrichment', 'clay batch optimization' — giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Clay-specific niche with distinct triggers ('clay throughput', 'clay batch optimization') that are unlikely to fire for unrelated skills.	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
Commit: 6e3a65f

Reviewed: 4 days 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.