CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, actionable upgrade workflow with executable code, explicit validation, and a rollback path. Its main weaknesses are mild redundancy (checklist duplicating steps, repetitive verification blocks) and lack of file-splitting for the long inline verification script.

Suggestions

Move the Step 3 verification TypeScript into a scripts/verify-upgrade.ts file and reference it from SKILL.md to improve progressive disclosure and reduce inline length.

Tighten conciseness by collapsing the four repetitive try/catch blocks in the verification script into a loop over the methods, and prune the Upgrade Checklist items that merely restate the step instructions.

Replace the Step 1 'Changelog' line that only prints the repository URL with an actual changelog fetch or a direct link, so the command delivers what its label promises.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no concept-explanation fluff, but the Upgrade Checklist restates the step instructions and the Step 3 verification function repeats four near-identical try/catch blocks that could be tightened into a loop.

2 / 3

Actionability

Provides fully executable bash (with set -euo pipefail) and a complete TypeScript verification script, plus concrete rollback commands — copy-paste ready guidance throughout.

3 / 3

Workflow Clarity

Five clearly sequenced steps with explicit validation (npm test, the verification script) and a rollback feedback loop for error recovery, satisfying the validation requirement for a dependency-changing operation.

3 / 3

Progressive Disclosure

Sections are well organized, but the skill is over 50 lines with no bundle files, and the long inline verification script is content that could be split into a scripts/ file rather than living entirely in SKILL.md.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-targeted: it names concrete upgrade/migration actions, provides an explicit Use-when clause with natural trigger phrases, and occupies a distinct exa-js niche. It uses appropriate third-person/imperative voice with no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in the domain — 'Upgrade exa-js SDK versions', 'handle breaking changes', 'detecting deprecations', 'migrating between exa-js versions' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers both what (upgrade exa-js SDK versions and handle breaking changes) and when, with an explicit 'Use when...' clause plus trigger phrases, so completeness is not capped at 2.

3 / 3

Trigger Term Quality

Explicit trigger phrases ('upgrade exa', 'exa update', 'exa breaking changes', 'update exa-js', 'exa new version') are natural terms a user would say when needing this skill, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The exa-js-specific niche and 'exa'-prefixed triggers make it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.