CtrlK
BlogDocsLog inGet started
Tessl Logo

apollo-upgrade-migration

Manage Apollo.io API upgrades and endpoint migrations. Use when upgrading Apollo API versions, migrating to new endpoints, or updating deprecated API usage. Trigger with phrases like "apollo upgrade", "apollo migration", "update apollo api", "apollo breaking changes", "apollo deprecation".

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

The body is actionable and concise, with executable code for every step of a clear audit-to-cleanup migration workflow. Its main gaps are implicit validation gating before destructive cleanup and an orphaned reference file that is not linked from the overview.

Suggestions

Add an explicit gated checkpoint after the Step 4 shadow test (e.g. 'Only proceed to cleanup when old and new result counts match; otherwise investigate parameter renames first') to satisfy the destructive-operation validation requirement.

Link references/implementation-guide.md from the body (e.g. a '## Implementation details — see [implementation-guide.md](references/implementation-guide.md)') and move the duplicated full audit/feature-flag/parallel-testing code there, keeping SKILL.md as an overview.

Tighten the Step 5 cleanup section with a verification checklist (confirm zero deprecated patterns via grep) before instructing feature-flag removal.

DimensionReasoningScore

Conciseness

The body is lean and code-dense with minimal prose, and it never explains concepts Claude already knows; the brief Overview adds relevant domain context rather than padding, so most tokens earn their place.

3 / 3

Actionability

Each step ships complete, executable TypeScript or bash with imports and concrete patterns (audit grep, migration rules, feature flags, shadow test, cleanup commands), making the guidance copy-paste ready.

3 / 3

Workflow Clarity

The five steps are clearly sequenced and include a shadow test (Step 4) and cleanup greps (Step 5), but there is no explicit gated checkpoint ('only proceed when the shadow test matches') before the destructive cleanup, so validation stays implicit.

2 / 3

Progressive Disclosure

A references/implementation-guide.md bundle exists but is never linked or signaled from the SKILL.md body, and full code blocks are inlined that overlap the reference, so content that could live one level deeper is kept inline.

2 / 3

Total

10

/

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 well-formed description that clearly states the skill's purpose, gives explicit 'Use when' guidance, and lists natural trigger phrases in a distinct niche. The only weakness is that the capability statement stays at a high level rather than enumerating concrete actions.

DimensionReasoningScore

Specificity

The phrase 'Manage Apollo.io API upgrades and endpoint migrations' names the domain and a couple of high-level actions, but it does not list multiple concrete actions (e.g. audit, compatibility layer, shadow test) the way the score-3 anchor does.

2 / 3

Completeness

It explicitly answers both what ('Manage Apollo.io API upgrades and endpoint migrations') and when ('Use when upgrading Apollo API versions, migrating to new endpoints, or updating deprecated API usage') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Trigger phrases like 'apollo upgrade', 'apollo migration', 'update apollo api', 'apollo breaking changes', and 'apollo deprecation' are natural terms a user would actually say, giving good coverage; voice is third person so no penalty applies.

3 / 3

Distinctiveness Conflict Risk

Apollo.io API migration is a clear, narrow niche with distinct trigger phrases, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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