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".
64
77%
Does it follow best practices?
Impact
—
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 solid skill description with excellent trigger term coverage and completeness, including both 'Use when' and explicit trigger phrases. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond 'build a pipeline'. The Clay-specific focus makes it highly distinctive.
Suggestions
Add more specific concrete actions to the capability description, e.g., 'configure webhook endpoints, set up waterfall enrichment providers, map data columns, and automate prospect list processing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Clay lead enrichment) and mentions some components (Clay tables, webhooks, waterfall enrichment), but doesn't list multiple concrete actions beyond 'build a pipeline'. It could be more specific about what actions are performed (e.g., 'configure webhook triggers, map enrichment columns, set up waterfall fallback providers'). | 2 / 3 |
Completeness | Clearly answers both 'what' (build a complete lead enrichment pipeline using Clay tables, webhooks, and waterfall enrichment) and 'when' (explicit 'Use when' clause with scenarios plus explicit trigger phrases). Both components are present and well-articulated. | 3 / 3 |
Trigger Term Quality | Includes a good range 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 'data enrichment workflows'. These cover natural variations a user would say. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Clay as a platform and lead enrichment pipelines, making it very unlikely to conflict with other skills. The repeated use of 'Clay' as a qualifier creates a clear niche. | 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/verification checkpoints between steps (especially before CRM export) and the monolithic structure that could benefit from splitting detailed configurations into separate files. The error handling table is a nice touch but reactive rather than integrated into the workflow as checkpoints.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Verify enrichment is running by checking that at least one test row populates Work Email before sending the full batch' and 'Test CRM push on a single row before enabling auto-run'.
Convert Step 6 from passive comments into actionable verification commands or checks, such as querying the Clay API for table stats or checking specific row counts.
Consider extracting the ICP scoring formula and CRM export configuration into separate reference files to improve progressive disclosure and reduce the main skill's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary commentary (e.g., 'This is the core use case for 90%+ of Clay users', the bash comment block in Step 6 that's just comments with no executable content). The table schema and error handling table are well-structured but some explanatory text could be trimmed. | 2 / 3 |
Actionability | Provides concrete, executable TypeScript code for webhook submission, specific Clay formula syntax for ICP scoring, a complete JSON payload for CRM export, and detailed step-by-step UI instructions with specific click paths. The guidance is specific enough to follow directly. | 3 / 3 |
Workflow Clarity | The 6-step sequence is clearly laid out and logically ordered, but there are no explicit validation checkpoints or feedback loops. Step 6 is just comments about what to watch rather than actionable verification steps. There's no 'if enrichment fails, do X' recovery loop, and for a pipeline involving batch operations and CRM pushes, this is a gap. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's fairly long and monolithic with no bundle files to offload detail into. The ICP formula, CRM export config, and error handling table could be separate reference files. References to external Clay University docs and the next workflow are good, but the skill itself could benefit from splitting. | 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
05447c0
- 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.