exa-upgrade-migration
Analyze, plan, and execute Exa SDK upgrades with breaking change detection. Use when upgrading Exa SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade exa", "exa migration", "exa breaking changes", "update exa SDK", "analyze exa version".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-upgrade-migration74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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-crafted skill description that excels in completeness and distinctiveness by clearly specifying the Exa SDK domain and providing explicit trigger phrases. The main weakness is that the capability descriptions could be more concrete about specific actions performed during the upgrade process.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Exa SDK) and lists actions (analyze, plan, execute upgrades, breaking change detection), but the actions are somewhat general upgrade-related terms rather than highly specific concrete operations like 'extract deprecation warnings' or 'generate migration scripts'. | 2 / 3 |
Completeness | Clearly answers both what (analyze, plan, execute Exa SDK upgrades with breaking change detection) and when (upgrading versions, detecting deprecations, migrating to new API versions) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'upgrade exa', 'exa migration', 'exa breaking changes', 'update exa SDK', 'analyze exa version'. These are realistic phrases a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Exa SDK specifically. The explicit naming of 'Exa' throughout and specific trigger phrases make it highly unlikely to conflict with other upgrade or migration skills for different SDKs. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable upgrade workflow with useful concrete examples for import and configuration changes. However, it suffers from a vague Step 4 that undermines actionability, and lacks explicit validation/retry loops for handling breaking changes. The structure and progressive disclosure are good, but the core upgrade workflow needs tighter guidance.
Suggestions
Replace Step 4's vague 'update as needed' with specific instructions: check for TypeScript errors, run tests, identify failing imports/methods, then reference the Examples section for common patterns
Add explicit validation checkpoint after fixing breaking changes: 'Run npm test && npm run typecheck - if errors persist, review the specific error messages and apply relevant patterns from Examples section'
Move the compatibility table from 'Error Handling' to a more appropriate section or rename it - it's version compatibility info, not error handling guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary elements like the 'Prerequisites' section listing obvious items (Git, test suite) and the 'Output' section which describes expected outcomes rather than instructions. | 2 / 3 |
Actionability | Provides concrete bash commands and TypeScript examples, but Step 4 'Handle Breaking Changes' is vague ('Update import statements, configuration, and method signatures as needed') without specific guidance. The examples section helps but is disconnected from the workflow. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but lacks explicit validation checkpoints. Step 3 runs 'npm test' but doesn't specify what to do if tests fail. No feedback loop for iterating on breaking changes - just 'update as needed' without verification steps. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate length for a SKILL.md, and one-level-deep references to external resources (Exa Changelog, Migration Guide) and related skill (exa-ci-integration). Content is appropriately structured without being monolithic. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 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.