clay-migration-deep-dive
Migrate to Clay from other enrichment tools or consolidate multiple data sources into Clay. Use when migrating from ZoomInfo, Apollo, Clearbit, or custom enrichment scripts to Clay, or consolidating fragmented enrichment workflows. Trigger with phrases like "migrate to clay", "clay migration", "switch to clay", "replace zoominfo with clay", "consolidate enrichment tools".
68
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clay-pack/skills/clay-migration-deep-dive/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 trigger terms, explicit 'Use when' and 'Trigger with' clauses, and a clearly distinctive niche. Its main weakness is that the 'what' portion could be more specific about the concrete actions involved in the migration process beyond just 'migrate' and 'consolidate'.
Suggestions
Add more specific concrete actions to the capability description, e.g., 'Maps data fields between platforms, configures Clay enrichment waterfall replacements, validates migrated data, and documents API transition steps.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (migration to Clay from enrichment tools) and some actions (migrate, consolidate), but doesn't list multiple specific concrete actions like mapping fields, configuring API connections, or validating data post-migration. | 2 / 3 |
Completeness | Clearly answers both 'what' (migrate to Clay from other enrichment tools or consolidate data sources) and 'when' (explicit 'Use when' clause with specific scenarios, plus a 'Trigger with phrases' section listing exact user phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including specific competitor names (ZoomInfo, Apollo, Clearbit), natural phrases users would say ('migrate to clay', 'switch to clay', 'replace zoominfo with clay'), and the general concept ('consolidate enrichment tools'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche — Clay migration from named competitors. The combination of 'Clay' + 'migration' + specific tool names makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but overly verbose migration guide that explains too many concepts Claude already understands and includes illustrative code that isn't truly executable. The workflow structure is reasonable with clear weekly phases, but lacks explicit validation gates and rollback criteria at critical decision points. The content would benefit significantly from being trimmed to essential decision points and concrete configurations rather than sample TypeScript interfaces.
Suggestions
Cut the content by 50%+: remove the TypeScript audit interface/sample data (Claude can generate these), remove explanatory comments like 'ZoomInfo is expensive', and focus on the actual Clay-specific configuration patterns and decision criteria.
Add explicit validation gates with concrete thresholds: e.g., 'Do not proceed past Step 3 unless Clay hit rate is within 5% of legacy provider hit rate on a 500-contact sample.'
Replace illustrative TypeScript stubs with actual executable Clay webhook configurations or API calls that can be directly used.
Extract the field mapping YAML and table configuration into separate bundle files, keeping SKILL.md as a concise workflow overview with references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200 lines. It explains concepts Claude already knows (what Clay is, what enrichment tools do), includes lengthy TypeScript interfaces and sample data that are illustrative rather than executable, and pads with unnecessary context like 'ZoomInfo is expensive' comments. The audit interface, sample stack data, and comparison functions are mostly boilerplate that don't add actionable value. | 1 / 3 |
Actionability | The code examples are structured but largely illustrative rather than truly executable—the TypeScript snippets define interfaces and stub functions without real implementations (e.g., enrichViaClay and enrichViaLegacy are referenced but never defined). The YAML configurations are pseudo-configurations for Clay rather than actual executable configs. The field mapping and table configuration provide useful guidance but aren't copy-paste ready. | 2 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with weekly timelines, and Step 6 includes a checklist. However, validation checkpoints are weak—Step 3's parallel run says 'Target: Clay should match or exceed current hit rates' but provides no concrete threshold or decision criteria for proceeding vs. rolling back. The gradual traffic migration lacks explicit validation gates between percentage increases. | 2 / 3 |
Progressive Disclosure | The content is largely monolithic with all details inline. The migration type table, field mapping, and all code examples are embedded in a single long document. There's a reference to 'clay-advanced-troubleshooting' at the end, but no bundle files exist to support it. The inline content (especially the audit TypeScript and parallel run code) could be split into referenced files. | 2 / 3 |
Total | 7 / 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.