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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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-structured, information-dense skill with real executable code and useful decision matrices, but it is monolithic (no reference files), embeds time-sensitive dates inline, and lacks explicit validation checkpoints in its migration workflow. The comment-only code blocks blur the line between guidance and runnable examples.

Suggestions

Move legacy plan details and date-bound information into a clearly labeled 'Legacy / Deprecated' section so the main flow stays evergreen and concise.

Add explicit validation checkpoints to the migration workflow (e.g., 'verify webhook returns 200 before proceeding', 'confirm feature availability per tier after plan change') since plan changes are destructive.

Replace the comment-only audit block with a concrete checklist or an actual API/curl call to fetch plan and credit usage, and split the pricing reference tables and code samples into reference files (e.g., references/pricing-2026.md, references/credit-tracker.ts) referenced from the overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with dense tables and lean code, but time-sensitive dates ('available until April 10, 2026', 'March 2026+') sit inline rather than in a deprecated/old-patterns section, and the audit 'bash' block is comment-only prose describing manual dashboard steps.	2 / 3
Actionability	Provides genuinely executable TypeScript (CreditTracker) and a real curl webhook test, but two fenced code blocks (Step 2 audit, Step 4 optimization) are entirely comments/pseudocode rather than runnable code, fitting the 'pseudocode instead of executable code' anchor.	2 / 3
Workflow Clarity	Five steps are clearly sequenced and an Error Handling table gives reactive recovery guidance, but plan migration is potentially destructive (features can disappear) and there are no explicit validation checkpoints in the flow, which caps this dimension at 2 per the rubric.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a single monolithic file with no bundle files at all; substantial inline content (pricing tables, integration code) that could be split into references is kept inline, and the only navigation points to a sibling skill and external URLs.	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 description that clearly answers both 'what' and 'when' with explicit, natural trigger phrases scoped to a distinct niche. The only weakness is that the action verbs ('navigate', 'adapt') lean slightly abstract rather than naming concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ('plan changes, pricing migrations, and feature upgrades', 'adapting integrations'), but verbs like 'Navigate' and 'adapt' are relatively abstract compared to the concrete multi-action anchor at level 3.	2 / 3
Completeness	Explicitly states what the skill does ('Navigate Clay plan changes, pricing migrations, and feature upgrades') and when to use it ('Use when upgrading Clay plans, migrating to the 2026 pricing model...') with explicit trigger phrases, satisfying both what and when.	3 / 3
Trigger Term Quality	Provides good coverage of natural phrases a user would actually say — 'upgrade clay', 'clay migration', 'clay pricing change', 'clay plan upgrade', 'clay new pricing' — across several common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow, product-specific niche (Clay plan upgrades / 2026 pricing migration) with distinct triggers, making conflict with other 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
Commit: 3022dd3

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