clay-migration-deep-dive
Execute Clay major re-architecture and migration strategies with strangler fig pattern. Use when migrating to or from Clay, performing major version upgrades, or re-platforming existing integrations to Clay. Trigger with phrases like "migrate clay", "clay migration", "switch to clay", "clay replatform", "clay upgrade major".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-migration-deep-dive76
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 completeness and trigger term coverage. It explicitly addresses when to use the skill and provides specific trigger phrases. The main weakness is that the capabilities could be more concrete - listing specific migration actions rather than high-level strategies would improve specificity.
Suggestions
Add more concrete actions beyond 'strangler fig pattern' - e.g., 'migrate data models', 'convert API endpoints', 'transform webhook handlers' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay migration) and mentions some actions like 'strangler fig pattern', 'major version upgrades', and 're-platforming', but doesn't list multiple concrete specific actions - it's more about scenarios than detailed capabilities. | 2 / 3 |
Completeness | Clearly answers both what (execute Clay re-architecture and migration with strangler fig pattern) and when (migrating to/from Clay, major version upgrades, re-platforming). Includes explicit 'Use when' clause and 'Trigger with phrases' section. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'migrate clay', 'clay migration', 'switch to clay', 'clay replatform', 'clay upgrade major'. Good coverage of variations users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on Clay platform migrations specifically. The combination of 'Clay' + migration/replatform terminology creates a distinct trigger profile unlikely to conflict with general migration or other platform skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This migration skill provides a solid workflow structure with clear phases, validation steps, and rollback procedures. However, it suffers from incomplete code examples that are more illustrative than executable, and could be more concise by removing placeholder functions and generic interface definitions that don't add actionable guidance.
Suggestions
Replace placeholder functions (getDataTypes, analyzeDependencies, etc.) with actual implementation examples or remove them entirely if they're context-dependent
Complete the transform() method with a concrete example showing actual field mapping between old and new formats
Move detailed code examples (adapter layer, data migration) to separate reference files and keep SKILL.md as a concise overview with quick-start commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary scaffolding like the generic interface definitions and placeholder functions (getDataTypes, analyzeDependencies) that don't add actionable value. The ASCII diagrams for strangler fig pattern are helpful but the overall content could be tightened. | 2 / 3 |
Actionability | Provides concrete code examples but many are incomplete or pseudocode-like (transform function with just a comment, placeholder async functions). The bash commands are executable, but TypeScript examples often lack implementation details needed to be truly copy-paste ready. | 2 / 3 |
Workflow Clarity | Clear phased approach with explicit week-by-week timeline, validation steps after migration, and a dedicated rollback plan. The workflow includes validation checkpoints (validateClayMigration) and error handling tables, making the multi-step process well-sequenced. | 3 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but it's somewhat monolithic with all details inline. References to external resources exist but the skill could better leverage separate files for detailed code examples or the data migration scripts. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.