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

—

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.

A detailed, actionable Clay workflow with strong code examples and a clear step sequence, but it is somewhat verbose, lacks a feedback loop for the batch CRM push, and does not split content into bundle reference files.

Suggestions

Replace the Step 6 commented bash block with a concrete check (e.g., an actual API/CLI query or a short verification step) or remove it to tighten conciseness.

Add an explicit validate→fix→retry checkpoint for the CRM HTTP API export (test on a single row, inspect failures, re-run) so the batch operation has a feedback loop.

Move the schema table, ICP formula, and error-handling matrix into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and specific to Clay, but the body runs ~160 lines with padding — notably Step 6 is a bash block of only commented metrics and the ICP formula is verbose; could be tightened without losing clarity.	2 / 3
Actionability	Provides concrete, copy-paste-ready artifacts: a TypeScript webhook batch sender, a JSON HTTP API config, a Clay formula, and specific UI click-paths with credit costs — executable rather than abstract.	3 / 3
Workflow Clarity	The six steps are clearly sequenced and include pre-send validation/dedup, but the batch CRM export lacks an explicit validate→fix→retry feedback loop; per the batch-operations guideline this caps the score at 2.	2 / 3
Progressive Disclosure	Sections are well organized, but at ~160 lines it exceeds the simple-skill threshold and keeps schema, formula, and error-handling content inline with no bundle files (references/scripts/assets are absent) or one-level-deep signaled references.	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, specific description that clearly states what the skill does, when to use it, and supplies natural trigger phrases. It uses an imperative/infinitive voice consistent with the reference examples and avoids fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions/components: "lead enrichment pipeline using Clay tables, webhooks, and waterfall enrichment" — names the domain and several specific mechanisms rather than vague language.	3 / 3
Completeness	Explicitly answers what ("Build a complete lead enrichment pipeline...") and when ("Use when building lead generation features, enriching prospect lists, or creating automated data enrichment workflows") plus explicit trigger phrases.	3 / 3
Trigger Term Quality	Provides natural phrases users would say — "clay lead enrichment", "clay main workflow", "enrich contacts in clay", "clay prospect list", "clay enrichment pipeline" — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Has a clear Clay-specific niche with distinct triggers unlikely to fire for unrelated skills; the repeated "clay" qualifier strongly distinguishes it.	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: 3022dd3

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