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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clay-pack/skills/clay-core-workflow-a/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong completeness and distinctiveness. It clearly identifies both what the skill does and when to use it, with explicit trigger phrases. The main weakness is that the capability description could be more granular, listing specific concrete actions rather than the high-level 'build a complete pipeline'.
Suggestions
Expand the capability description with more specific actions, e.g., 'create Clay tables, configure webhook triggers, set up waterfall enrichment columns, map and normalize contact data fields' instead of the general 'build a complete pipeline'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Clay lead enrichment) and mentions some components (Clay tables, webhooks, waterfall enrichment), but the actions are somewhat high-level ('build a complete pipeline') rather than listing multiple distinct concrete actions like 'create tables, configure webhooks, set up waterfall enrichment columns, map data fields'. | 2 / 3 |
Completeness | Clearly answers both 'what' (build a lead enrichment pipeline using Clay tables, webhooks, and waterfall enrichment) and 'when' (explicit 'Use when' clause with trigger scenarios and a 'Trigger with phrases' section listing specific phrases). | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms: 'clay lead enrichment', 'clay main workflow', 'enrich contacts in clay', 'clay prospect list', 'clay enrichment pipeline', plus broader terms like 'lead generation', 'enriching prospect lists', and 'automated data enrichment workflows'. Good coverage of what users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Clay' as the platform and the niche focus on lead enrichment pipelines with Clay-specific components (Clay tables, waterfall enrichment). Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that provides concrete code examples, specific UI instructions, and a clear multi-step workflow for Clay lead enrichment. Its main weaknesses are the lack of explicit validation checkpoints within the workflow (important for batch data operations) and some verbosity that could be trimmed. The error handling table is useful but would be more effective if validation steps were integrated into the workflow itself.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Verify webhook delivery by checking Clay table for new rows before proceeding' and 'Confirm enrichment columns have populated before enabling CRM export'.
Convert Step 6 from bash comments into actionable verification steps, such as querying the Clay API for enrichment completion rates or providing a concrete script to check results.
Trim unnecessary commentary like 'This is the core use case for 90%+ of Clay users' and the explanatory text in column purpose descriptions that Claude can infer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary commentary (e.g., 'This is the core use case for 90%+ of Clay users') and the Step 6 monitoring section is essentially comments in a bash block with no executable content. Some column descriptions in the schema table are obvious. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for webhook submission, concrete Clay formula syntax for ICP scoring, specific JSON payloads for CRM export, and detailed UI click-paths for waterfall enrichment setup. The guidance is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-6) and logically ordered, but there are no explicit validation checkpoints or feedback loops. For a pipeline involving batch data operations and CRM pushes, there should be verification steps (e.g., verify enrichment completed before CRM export, validate webhook delivery). The error handling table partially compensates but is reactive rather than built into the workflow. | 2 / 3 |
Progressive Disclosure | Has reasonable structure with clear sections and references to external resources and a next-steps pointer to workflow B. However, the inline content is quite long and some sections (like the full ICP formula and CRM export config) could be split into referenced files. The prerequisites reference `clay-install-auth` which is good progressive disclosure. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3e83543
- Reviewed
Table of Contents
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.