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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 distinctiveness. It explicitly provides both 'Use when' guidance and trigger phrases, making it easy for Claude to select appropriately. The main weakness is that the capability description could be more specific about the concrete actions performed beyond the high-level 'manage upgrades and migrations'.
Suggestions
Add more specific concrete actions such as 'Maps deprecated endpoints to new equivalents, updates request/response schemas, handles authentication changes, and resolves breaking changes between API versions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io API) and some actions (upgrades, endpoint migrations, updating deprecated usage), but doesn't list multiple concrete specific actions like mapping old endpoints to new ones, updating request/response schemas, or handling authentication changes. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage Apollo.io API upgrades and endpoint migrations) and 'when' (explicit 'Use when...' clause plus a 'Trigger with phrases like...' section providing concrete trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'apollo upgrade', 'apollo migration', 'update apollo api', 'apollo breaking changes', 'apollo deprecation'. These are realistic phrases a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Apollo.io API migrations specifically. The combination of 'Apollo.io' with 'API upgrades' and 'endpoint migrations' creates a clear, distinct identity unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with a clear multi-step migration workflow, concrete TypeScript code, and good error handling guidance. Its main weakness is that it's quite long for a SKILL.md — the detailed code implementations would be better placed in referenced bundle files, with the SKILL.md serving as a concise overview. Some minor verbosity in the overview section could also be trimmed.
Suggestions
Move the detailed TypeScript implementations (audit script, migration map, feature flags, shadow test) into separate bundle files and reference them from SKILL.md with brief descriptions of what each does.
Trim the Overview paragraph — remove the parenthetical explanation of what breaking changes Apollo has made historically, as this is covered by the migration rules themselves.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably focused but includes some unnecessary verbosity — the `Current State` shell command is unexplained, the Overview paragraph explains what breaking changes are (Claude knows this), and the full TypeScript audit script is quite long when a more concise version with key patterns would suffice. The migration rules map is useful but could be more compact. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for each step — audit script, migration map, feature flags, shadow testing, and cleanup bash commands. Code is concrete, copy-paste ready, and includes specific endpoint patterns, regex replacements, and environment variable names. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced: audit → define migration rules → feature-flag the migration → shadow test old vs new → cleanup. It includes validation via shadow testing (Step 4) with result comparison, post-migration grep checks (Step 5), and the feature flag approach provides a rollback mechanism. The error handling table adds explicit recovery guidance. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with ~150+ lines of inline code that could benefit from being split into referenced files (e.g., the audit script, migration map, and feature flags as separate files). The reference to 'apollo-ci-integration' in Next Steps is good, but the main content is heavy for a SKILL.md overview. No bundle files are provided to offload the detailed code. | 2 / 3 |
Total | 10 / 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
3a2d27d
- 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.