exa-upgrade-migration
Upgrade exa-js SDK versions and handle breaking changes safely. Use when upgrading the Exa SDK, detecting deprecations, or migrating between exa-js versions. Trigger with phrases like "upgrade exa", "exa update", "exa breaking changes", "update exa-js", "exa new version".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 'when' guidance. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., updating imports, migrating API calls, handling specific breaking changes). Overall it's a solid description that would enable accurate skill selection.
Suggestions
Add more specific concrete actions to the first sentence, e.g., 'Upgrade exa-js SDK versions, update deprecated API calls, migrate import paths, and resolve breaking changes safely.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (exa-js SDK upgrades) and some actions ('upgrade versions', 'handle breaking changes'), but doesn't list multiple concrete actions like detecting specific deprecations, updating import paths, or migrating specific API calls. | 2 / 3 |
Completeness | Clearly answers both 'what' (upgrade exa-js SDK versions and handle breaking changes) and 'when' (explicit 'Use when...' clause with triggers, plus a 'Trigger with phrases like...' section providing additional guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'upgrade exa', 'exa update', 'exa breaking changes', 'update exa-js', 'exa new version', plus 'deprecations' and 'migrating between exa-js versions'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting the exa-js SDK specifically. The trigger terms are all exa-specific and unlikely to conflict with other skills unless there were multiple exa-related 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 solid upgrade/migration skill with strong actionability and workflow clarity. The step-by-step process with validation checkpoints and rollback procedures is well-designed. The main weaknesses are moderate verbosity (the inline verification script is lengthy and the breaking changes section is speculative) and the lack of bundle files to support progressive disclosure.
Suggestions
Extract the lengthy verification TypeScript script into a separate bundle file (e.g., verify-upgrade.ts) and reference it from the SKILL.md to improve progressive disclosure and conciseness.
Trim the breaking changes section to only include confirmed, documented changes rather than speculative comments like '// has been stable' — or remove it until actual breaking changes are known.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary verbosity. The verification script is quite long and could be more concise. Comments like '// Import style (has been stable)' and '// Constructor (has been stable)' explain things Claude already knows. The breaking changes section is mostly speculative ('if upgrading from a very old version, check') rather than definitive. | 2 / 3 |
Actionability | The skill provides fully executable bash commands and TypeScript code at each step. The upgrade verification script is copy-paste ready with concrete API calls, the rollback procedure has specific commands, and the checklist provides clear actionable items. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 5 steps with explicit validation checkpoints: npm test after install, a dedicated verification script that checks all API methods, a rollback procedure if tests fail, and a comprehensive checklist. The feedback loop (test → fail → rollback → verify) is well-defined. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but the verification script is quite long inline when it could be a separate file. The reference to 'exa-ci-integration' at the end is good progressive disclosure, but no bundle files exist to support it. The error handling table and checklist are well-organized. | 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
a04d1a2
- 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.