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

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/clay-pack/skills/clay-migration-deep-dive/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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

A reasonably structured, code-heavy migration guide with a clear weekly sequence, but it is held back by stub methods, a few redundant comments, missing validation feedback loops on the batch cutover, and a broken/unused reference structure.

Suggestions

Implement or mark as pseudocode the stubbed methods (enrichViaClay, enrichViaLegacy) and trim obvious comments like '// ZoomInfo is expensive' to lift conciseness and actionability to 3.

Add an explicit validation checkpoint between the parallel run (Step 3) and full traffic migration (Step 5) — e.g. 'proceed only if Clay hit rate >= legacy hit rate on the 500-contact sample' — to introduce the feedback loop the batch cutover requires.

Either create a clay-advanced-troubleshooting reference or repoint the 'Next Steps' line to the existing references/implementation-guide.md so body references resolve to real bundle files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code/YAML with no concept-explanation fluff, but it carries redundant inline comments (e.g. '// ZoomInfo is expensive', '// Just developer time') and could be tightened to earn score 3.	2 / 3
Actionability	Provides concrete TypeScript/YAML the user can adapt, but several methods are stubs (enrichViaClay/enrichViaLegacy are unimplemented, generateMigrationReport only logs), keeping it from being fully copy-paste ready.	2 / 3
Workflow Clarity	A clear 6-step weekly sequence exists and Step 6 has a checklist, but the batch traffic-shift cutover and parallel-run lack explicit validation/retry checkpoints; per the rubric, batch/destructive ops without feedback loops cap this at 2.	2 / 3
Progressive Disclosure	The body has some structure but its only reference (clay-advanced-troubleshooting) is not a real bundle file, while the actual bundle file (references/implementation-guide.md) is never linked from the body, leaving navigation unclear.	2 / 3
	Total	8 / 12 Passed

Description

90%Weight 40%Scale 1-3

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, well-structured description with explicit what/when guidance and natural trigger terms covering named providers. The only weakness is specificity, which names the domain and two actions rather than a fuller enumeration of concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('enrichment tools', 'Clay') and the two core actions (migrate/consolidate), but does not enumerate a comprehensive list of concrete actions as the score-3 anchor requires.	2 / 3
Completeness	Explicitly answers what ('Migrate to Clay... consolidate multiple data sources into Clay') and when via a 'Use when...' clause naming concrete provider/source scenarios.	3 / 3
Trigger Term Quality	Natural phrases users would actually say are well covered: 'migrate to clay', 'clay migration', 'switch to clay', 'replace zoominfo with clay', 'consolidate enrichment tools'.	3 / 3
Distinctiveness Conflict Risk	The Clay-migration niche is specific and the triggers reference named providers (ZoomInfo, Apollo, Clearbit), making conflict with unrelated skills unlikely.	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
Path: plugins/saas-packs/clay-pack/skills/clay-migration-deep-dive/SKILL.md
Commit: 0540a62

Reviewed: about 7 hours 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.