clay-core-workflow-a

Build a complete lead enrichment pipeline using Clay tables, webhooks, and waterfall enrichment. Use when building lead generation features, enriching prospect lists, or creating automated data enrichment workflows. Trigger with phrases like "clay lead enrichment", "clay main workflow", "enrich contacts in clay", "clay prospect list", "clay enrichment pipeline".

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

92%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.

The skill body is tight, highly actionable, and well-sequenced with validation for its batch operation. Its main weakness is progressive disclosure: all detail lives inline in one file rather than being split into navigable reference materials.

Suggestions

Split the large column-schema table, ICP formula, and HTTP API JSON config into dedicated reference files (e.g. references/table-schema.md, references/icp-formula.md) and link to them from the main steps to improve progressive disclosure.

Replace the comment-only Step 6 bash block with an actual runnable command or a concrete verification action (e.g. a curl check against the webhook) rather than describing metrics in prose.

Add an explicit error-recovery retry loop after the webhook send (on result.errors, fix and re-send failed rows) so the batch feedback loop is complete rather than log-only.

Dimension	Reasoning	Score
Conciseness	The body is lean and instructional — it assumes Claude's competence and avoids explaining what Clay or enrichment are, with concrete code and tables earning their tokens; only a minor overview sentence and a comment-only Step 6 block could be tightened, but it does not cross into verbosity.	3 / 3
Actionability	Provides executable TypeScript with validation logic, exact Clay UI menu paths ('+ Add Column > Find Work Email (Waterfall)'), a complete JSON HTTP API config, and a concrete ICP formula — copy-paste ready, matching the score-3 anchor.	3 / 3
Workflow Clarity	A clearly sequenced 6-step pipeline with an explicit validation checkpoint in the batch webhook step ('Validate and deduplicate before sending') and error reporting on failed rows, satisfying the batch-operation feedback requirement.	3 / 3
Progressive Disclosure	Content is well-sectioned but entirely inline in a ~160-line single file with no bundle files splitting out the column schema, formula, or API config; references point only to external Clay University docs and a sibling skill rather than to organized one-level-deep reference files.	2 / 3
	Total	11 / 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.

The description is specific, uses third-person voice, and cleanly separates the capability statement from explicit use-when guidance with natural trigger phrases. It is a strong, low-conflict description that earns full marks across all dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Build a complete lead enrichment pipeline using Clay tables, webhooks, and waterfall enrichment' — naming specific mechanisms rather than vague domain references, matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what ('Build a complete lead enrichment pipeline...') and when ('Use when building lead generation features, enriching prospect lists, or creating automated data enrichment workflows') in third person, matching the score-3 anchor with an explicit Use-when clause.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say — 'clay lead enrichment', 'clay main workflow', 'enrich contacts in clay', 'clay prospect list', 'clay enrichment pipeline' — giving good coverage of likely utterances.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Clay-specific niche with branded, distinctive trigger phrases, making it 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
Path: plugins/saas-packs/clay-pack/skills/clay-core-workflow-a/SKILL.md
Commit: c4eafaf

Reviewed: 1 day 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.