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 trigger terms and clear 'what/when' guidance. Its main weakness is that the capability description could be more specific about the concrete actions performed (e.g., endpoint mapping, schema updates, auth changes). Overall it would perform well in skill selection scenarios.
Suggestions
Add more specific concrete actions beyond 'manage upgrades and migrations' — e.g., 'Maps deprecated endpoints to new equivalents, updates request/response schemas, handles authentication 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 'Trigger with phrases like' providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'apollo upgrade', 'apollo migration', 'update apollo api', 'apollo breaking changes', 'apollo deprecation' — these are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Apollo.io API migrations specifically, with distinct trigger terms that are unlikely to conflict with other skills. The combination of 'Apollo' + 'API' + 'upgrade/migration' is highly distinctive. | 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 migration skill with a clear 5-step workflow including validation checkpoints (shadow testing, post-migration grep checks) and rollback mechanisms (feature flags). Its main weakness is verbosity—the full inline code blocks make the skill quite long when a more concise overview with references to detailed implementation files would be more token-efficient. The domain-specific knowledge about Apollo's breaking changes is genuinely valuable and not something Claude would inherently know.
Suggestions
Extract the detailed TypeScript implementations into separate referenced files (e.g., audit-script.ts, migration-map.ts) and keep SKILL.md as a concise overview with key patterns and workflow steps.
Trim the ENDPOINT_MAP and MIGRATION_RULES to show 2-3 representative examples each with a comment like '// see full list in migration-map.ts' to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and provides useful migration-specific knowledge, but includes some unnecessary verbosity—full TypeScript interface definitions, extensive inline comments, and the `Current State` shell command section add tokens without proportional value. The code blocks are longer than needed for conveying the patterns. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for each step—audit scripts, migration maps with concrete regex patterns, feature-flagged implementations, shadow testing, and cleanup bash commands. The endpoint mappings and migration rules are specific and copy-paste ready. | 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 feature flags provide a rollback mechanism. The error handling table adds explicit recovery guidance. | 3 / 3 |
Progressive Disclosure | The content is mostly monolithic—all code is inline in a single file rather than being split into referenced files. The references to external docs and the 'Next Steps' link to apollo-ci-integration are good, but the main body could benefit from separating the detailed code into referenced files while keeping the SKILL.md as a concise overview. | 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
70e9fa4
- 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.