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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-sequenced migration guide with concrete configs and a verification checklist, weakened by incomplete code scaffolding, a missing rollback loop for the destructive cutover, and broken/orphaned reference signaling. The body leans monolithic while its one 'see also' link dangles and its actual reference file goes unused.

Suggestions

Fix progressive disclosure: link the existing references/implementation-guide.md from the body (e.g., under a 'Deep dive' section) and either create clay-advanced-troubleshooting or remove the dangling Next Steps reference.

Add an explicit rollback/feedback loop to Step 5's traffic cutover — e.g., 'if Clay hit rate drops below legacy baseline at any percentage, revert clayPercentage and re-validate' — so the destructive cutover has an error-recovery path.

Tighten actionability: replace undefined-method scaffolding (enrichViaClay/enrichViaLegacy, the audit/compare stubs) with either concrete Clay SDK calls or clearly-labeled illustrative pseudocode, and correct the 'monthlyCoost' typo.

Dimension	Reasoning	Score
Conciseness	Mostly efficient executable code rather than concept-explanation fluff, but carries illustrative sample data (full provider cost/volume records, comments like 'ZoomInfo is expensive') and verbose class scaffolding that could be tightened; it is not the lean 'every token earns its place' of a score-3.	2 / 3
Actionability	Provides concrete, largely copy-paste-ready YAML field mappings and Clay table configs, but several TypeScript blocks are scaffolding calling undefined methods (enrichViaClay, enrichViaLegacy) and a typo ('monthlyCoost') signals incompleteness, matching the score-2 'missing key details' anchor.	2 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced with week labels and a Step-6 verification checklist, but the destructive cutover (100% to Clay, legacy disabled, subscription cancellation) lacks an explicit rollback/feedback loop in the body, capping clarity at 2 per the destructive-operations rule.	2 / 3
Progressive Disclosure	Has organized sections and a real bundle file (references/implementation-guide.md), but that file is never linked from the body while the body's only forward reference ('clay-advanced-troubleshooting') points to a non-existent file — references are present but poorly signaled, fitting the score-2 anchor.	2 / 3
	Total	8 / 12 Passed

Description

90%

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, third-person description that clearly states both capability and trigger conditions with natural keyword coverage and a distinct niche. Its only soft spot is specificity, which names two actions rather than a comprehensive list of concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('Migrate to Clay from other enrichment tools', 'consolidate multiple data sources into Clay'), but does not enumerate a broad set of specific capabilities the way the score-3 example does.	2 / 3
Completeness	Explicitly answers both what ('Migrate to Clay... or consolidate multiple data sources') and when ('Use when migrating from ZoomInfo, Apollo, Clearbit, or custom enrichment scripts to Clay, or consolidating fragmented enrichment workflows'), with an explicit trigger-phrases clause.	3 / 3
Trigger Term Quality	Provides a rich set of natural phrases users would say ('migrate to clay', 'clay migration', 'switch to clay', 'replace zoominfo with clay', 'consolidate enrichment tools') plus named tools (ZoomInfo, Apollo, Clearbit).	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Clay migration from named competitor tools) with distinct, tool-specific triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 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: 02d6341

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