clay-load-scale

Scale Clay enrichment pipelines for high-volume processing (10K-100K+ leads/month). Use when planning capacity for large enrichment runs, optimizing batch processing, or designing high-volume Clay architectures. Trigger with phrases like "clay scale", "clay high volume", "clay large batch", "clay capacity planning", "clay 100k leads", "clay bulk enrichment".

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 strong executable examples and a useful error table, but it is somewhat padded and lacks explicit validation checkpoints for its batch/destructive workflows. Progressive disclosure is weakened by an existing reference file that is not linked from the body.

Suggestions

Add explicit validation/checkpoint steps to the batch and auto-delete workflows (e.g., verify queued counts vs. sent/failed, confirm destination receipt before deletion) to support a validate-fix-retry feedback loop.

Link references/implementation-guide.md from the body (e.g., under a "## Load testing & benchmarks" section) so the bundle reference is clearly signaled one level deep, and fix the plain-text Clay University line to a real markdown link.

Trim inline console.log "TIP" lines and self-explanatory comments to reduce token overhead and improve conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code, but includes some redundant commentary (e.g., inline console.log TIP lines and explanatory comments Claude could infer) that could be tightened; not quite lean enough for the top anchor.	2 / 3
Actionability	Provides complete, executable TypeScript (capacity planner, BullMQ batch processor, webhook rotator) plus a concrete YAML table strategy — copy-paste ready and specific, matching the top anchor.	3 / 3
Workflow Clarity	Steps are sequenced (Step 1–5) and an error-handling table exists, but batch and destructive operations (stream-through auto-delete) lack explicit validation checkpoints or validate-fix-retry feedback loops, capping the score at 2 per the rubric.	2 / 3
Progressive Disclosure	A bundle reference (references/implementation-guide.md) exists but is never linked from the body; the body instead points to a non-bundled skill (clay-reliability-patterns) and an unlinked Clay University mention, so structure is present but references are not clearly signaled.	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.

The description is well-crafted: third person, concise, explicit "Use when" clause, and a rich set of natural trigger phrases. It clearly communicates both capability and trigger context with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "planning capacity for large enrichment runs, optimizing batch processing, or designing high-volume Clay architectures" — matching the anchor for specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Scale Clay enrichment pipelines for high-volume processing") and when ("Use when planning capacity...") with an explicit trigger clause, hitting the top anchor.	3 / 3
Trigger Term Quality	Provides natural phrases a user would say ("clay scale", "clay high volume", "clay large batch", "clay capacity planning", "clay 100k leads", "clay bulk enrichment") with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (high-volume Clay scaling 10K-100K+ leads) with distinct triggers unlikely to conflict with other 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: 02d6341

Reviewed: about 2 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.