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

75%

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-upgrade-migration/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 well-structured, information-dense migration guide with real executable code and decision matrices, but it mixes comment-only guidance with runnable code, lacks validation feedback loops, and keeps all time-sensitive and reference-worthy content inline in a single file.

Suggestions

Isolate legacy/time-sensitive details (old plan table, 'April 10, 2026' cutoff) under an explicit 'Legacy / Deprecated' section so conciseness is not penalized for inline dates.

Add a validate→fix→retry checkpoint after the webhook migration test (e.g., assert the response, retry on failure, then verify HTTP API columns) to lift workflow clarity.

Convert Step 2's commented audit block into an executable checklist or script, or move the provider cost table and legacy plan reference into a references/ file linked one level deep from the body.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but time-sensitive dates ('April 10, 2026', 'March 2026+') and version numbers sit inline in active sections rather than in an 'old patterns'/'deprecated' block, which the rubric penalizes.	2 / 3
Actionability	Step 3's CreditTracker class and Step 5's curl command are executable, but Step 2's audit block and Step 4's code are comment-only manual guidance rather than runnable code, leaving the guidance partially incomplete.	2 / 3
Workflow Clarity	The five steps are clearly sequenced and a webhook test exists, but there is no explicit validate→fix→retry feedback loop for an operation (plan change) that can break integrations, capping clarity at 2.	2 / 3
Progressive Disclosure	Sections are well organized, but the ~150-line body is monolithic with no bundle files, and content like the provider cost table or legacy-plan reference could be split into one-level-deep references.	2 / 3
	Total	8 / 12 Passed

Description

100%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, third-person description that names concrete actions, provides an explicit Use-when trigger with natural keyword variations, and carves out a distinct niche. Minor cosmetic issue: the multi-line YAML folding leaves blank lines mid-sentence, but the content is complete and clear.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Navigate Clay plan changes, pricing migrations, and feature upgrades' and 'adapting integrations to new Clay features' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (navigate plan changes/migrations/upgrades) and when ('Use when upgrading Clay plans, migrating to the 2026 pricing model, or adapting integrations').	3 / 3
Trigger Term Quality	Covers natural phrases a user would say ('upgrade clay', 'clay migration', 'clay pricing change', 'clay plan upgrade', 'clay new pricing') with good variation.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear Clay-specific pricing/migration niche with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	12 / 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-upgrade-migration/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.