apollo-upgrade-migration
Plan and execute Apollo.io SDK upgrades. 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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-upgrade-migration87
Quality
83%
Does it follow best practices?
Impact
99%
1.67xAverage score across 3 eval scenarios
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 excellent trigger term coverage and clear completeness. The main weakness is that the capabilities could be more specific - it describes the general task (upgrades/migrations) but doesn't enumerate the concrete actions Claude would perform during such upgrades.
Suggestions
Add 2-3 specific concrete actions like 'update authentication patterns', 'refactor deprecated endpoint calls', or 'migrate rate limiting configurations' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io SDK) and some actions (upgrades, migrating, updating deprecated usage), but lacks specific concrete actions like 'update authentication methods', 'refactor endpoint calls', or 'handle schema changes'. | 2 / 3 |
Completeness | Clearly answers both what (plan and execute Apollo.io SDK upgrades) and when (explicit 'Use when...' clause with scenarios plus 'Trigger with phrases' providing concrete examples). | 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 developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Apollo.io SDK specifically. The combination of 'Apollo' with upgrade/migration terminology creates a distinct trigger profile 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 strong, actionable skill for Apollo API migrations with excellent workflow clarity and executable code examples. The main weakness is verbosity - the comprehensive inline code (audit scripts, compat layers, rollout strategies) makes it token-heavy when some content could be externalized. The phased rollout approach with explicit rollback procedures demonstrates good safety practices.
Suggestions
Extract the full audit script (apollo-audit.ts) to a separate referenced file, keeping only a brief description and usage example inline
Move the Kubernetes YAML and gradual rollout implementation details to a separate ROLLOUT.md file, referencing it from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose elements like the full audit script that could be referenced externally. The Kubernetes YAML and gradual rollout code add bulk that may not be needed for every upgrade scenario. | 2 / 3 |
Actionability | Provides fully executable code throughout - bash commands for auditing, complete TypeScript scripts for compatibility layers, feature flags, and parallel testing. All examples are copy-paste ready with realistic patterns. | 3 / 3 |
Workflow Clarity | Clear 4-step migration process with explicit phases (Canary → Gradual → Full), validation through parallel testing, and explicit rollback procedures. The workflow includes feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is monolithic - the full audit script and compatibility layer code could be split into separate reference files. References to external resources are present but inline content is heavy. | 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 | |
- 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.