clay-upgrade-migration
Navigate Clay plan changes, pricing migrations, and feature upgrades. Use when upgrading Clay plans, migrating to the 2026 pricing model, or adapting integrations to new Clay features. Trigger with phrases like "upgrade clay", "clay migration", "clay pricing change", "clay plan upgrade", "clay new pricing".
74
70%
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-upgrade-migration/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 excellent trigger term coverage and completeness, clearly specifying both what the skill does and when to use it. Its main weakness is that the capability descriptions are somewhat high-level—listing more concrete actions (e.g., 'compare plan tiers', 'map deprecated features to replacements') would strengthen specificity. Overall, it is well-structured and distinctive.
Suggestions
Add more concrete actions beyond 'navigate' and 'adapt'—e.g., 'compare plan tiers, map deprecated features to replacements, update integration configurations for the 2026 pricing model'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay plan changes, pricing migrations, feature upgrades) and some actions (navigate, upgrade, migrate, adapt integrations), but the actions are somewhat general and not deeply concrete—e.g., it doesn't specify what specific tasks like 'compare plan tiers', 'update API endpoints', or 'reconfigure webhooks' are involved. | 2 / 3 |
Completeness | Clearly answers both 'what' (navigate Clay plan changes, pricing migrations, feature upgrades) and 'when' (explicit 'Use when...' clause plus a 'Trigger with phrases like...' section). Both components are present and explicit. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'upgrade clay', 'clay migration', 'clay pricing change', 'clay plan upgrade', 'clay new pricing'. These are realistic phrases a user would say and provide good keyword coverage for the specific domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Clay platform pricing and plan migrations—a very narrow niche. The trigger terms are all Clay-specific, making it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid informational reference for Clay's 2026 pricing migration with useful decision matrices and pricing comparisons. However, it leans more toward documentation than actionable skill guidance—the TypeScript code is helpful but the core migration workflow lacks validation checkpoints and concrete verification steps. The content could be more concise by extracting pricing tables to reference files and removing pseudo-code comment blocks.
Suggestions
Add explicit validation checkpoints to the migration workflow: e.g., 'After switching plans, verify: (1) run test enrichment and confirm credit deduction matches new model, (2) test all webhook endpoints, (3) confirm HTTP API columns if on Growth'
Replace the Step 2 bash comment block with actual actionable guidance or remove it entirely—comments-as-code adds no value for Claude
Extract the pricing comparison tables and provider credit tables into a separate reference file (e.g., CLAY_PRICING_REFERENCE.md) and link to it, keeping SKILL.md focused on the migration workflow
Add a rollback or contingency section: what to do if the migration causes integration failures, and whether reverting to legacy plans is possible before the April 2026 cutoff
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the prerequisites section (Claude doesn't need to be told to have an active account) and the bash comments in Step 2 that are just instructions disguised as code comments. The pricing tables are useful reference material but the overall content could be tightened. | 2 / 3 |
Actionability | The TypeScript credit tracker is concrete and executable, but much of the guidance is descriptive rather than actionable. The Step 2 'code block' is just comments telling you to look at a dashboard, and the curl test in Step 5 is useful but incomplete (no verification of the response). The decision matrix is helpful but the skill leans more toward informational reference than executable guidance. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced and logically ordered, but there are no validation checkpoints or feedback loops for the migration process itself. A plan migration is a potentially disruptive operation, yet there's no 'verify your integrations still work after switching' checklist or rollback guidance. The error handling table partially compensates but is reactive rather than preventive. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but the pricing tables and provider credit comparison tables make this quite long when they could be referenced from a separate file. The single reference to 'clay-ci-integration' at the end is good but the skill would benefit from splitting reference data (pricing tables, provider costs) into separate files. | 2 / 3 |
Total | 8 / 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
3e83543
- 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.