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 solid skill description with strong completeness and distinctiveness. It clearly identifies when to use the skill and includes good trigger terms specific to Clay. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond 'build a pipeline'.
Suggestions
Add more specific concrete actions to the capability description, e.g., 'configure webhook triggers, map enrichment columns, set up waterfall enrichment logic, and export enriched data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (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 logic'). | 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 triggers and a 'Trigger with phrases' section). Both are explicitly stated. | 3 / 3 |
Trigger Term Quality | Includes a good range of natural trigger terms: 'clay lead enrichment', 'enrich contacts in clay', 'clay prospect list', 'clay enrichment pipeline', 'lead generation', 'enriching prospect lists', 'data enrichment workflows'. These cover variations a user would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Clay-specific lead enrichment pipelines, which is a distinct niche. The repeated mention of 'Clay' and specific concepts like 'waterfall enrichment' and 'Clay tables' make it unlikely to conflict with generic data processing or other CRM 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 guidance for building a Clay lead enrichment pipeline with executable code, specific UI instructions, and a useful error handling table. Its main weaknesses are the lack of explicit validation checkpoints between steps (particularly important given credit-consuming enrichment operations) and the monolithic structure that could benefit from splitting detailed configurations into supporting files. The Step 6 monitoring section is notably weak, consisting only of bash comments rather than actionable verification steps.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Send 1 test lead first, verify enrichment columns populate within 60 seconds before sending the full batch' — this is critical for credit-consuming operations.
Replace the Step 6 bash comment block with actionable verification steps: specific things to check in the Clay UI, expected outcomes, and what to do if metrics are below target.
Consider extracting the ICP scoring formula and CRM export configuration into separate bundle files (e.g., formulas/icp-score.md, integrations/hubspot-export.md) to improve progressive disclosure.
| 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 sections are well-structured but could be tighter. | 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 a detailed table schema. Steps are specific with exact UI navigation paths (e.g., '+ Add Column > Find Work Email (Waterfall)'). | 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 validation steps. There's no 'verify enrichment is working before proceeding' checkpoint between steps, which is important for a pipeline involving credit-consuming operations. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and references to external resources and a next-steps skill. However, the skill is quite long (~150 lines of substantive content) and could benefit from splitting detailed formula syntax or CRM configuration into separate reference files. No bundle files exist to offload complexity. | 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
3a2d27d
- 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.