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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A well-structured, highly actionable upgrade guide with executable code, validation, and rollback. Tightening the redundant Current State section and inlining the failure-to-rollback linkage would lift it further.

Suggestions

Remove or merge the 'Current State' shell snippets with Step 1 to eliminate redundant version-check commands.

In Step 2, explicitly branch on 'npm test' failure (e.g., 'if tests fail, proceed to Step 5 Rollback') to make the validation feedback loop inline rather than implicit.

Tighten the Error Handling table so each Solution points to a concrete command or section instead of a generic instruction like 'Check SDK changelog'.

DimensionReasoningScore

Conciseness

Mostly lean and executable with well-chosen code, but minor redundancy exists (the 'Current State' shell snippets overlap Step 1) and the Error Handling table is somewhat generic.

4 / 5

Actionability

Provides copy-paste-ready bash scripts using 'set -euo pipefail', a complete TypeScript verification script exercising search/searchAndContents/findSimilar/getContents, and a concrete rollback procedure.

5 / 5

Workflow Clarity

Five clearly sequenced steps plus an upgrade checklist, a verification script, and an explicit rollback feedback loop; the main upgrade path does not inline the 'if tests fail, rollback' linkage, a minor validation gap.

4 / 5

Progressive Disclosure

Well-organized into clear sections with a one-level Next Steps pointer to 'exa-ci-integration' and external resource links; no bundle files exist, and at ~150 lines the under-50-line simple-skill exception does not apply.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

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

A strong, specific description that clearly conveys purpose and trigger conditions with natural phrasing. It could enumerate a broader range of distinct capabilities, but covers the upgrade domain well.

DimensionReasoningScore

Specificity

Names the exa-js SDK domain and several concrete actions ('Upgrade exa-js SDK versions', 'handle breaking changes', 'detecting deprecations', 'migrating between exa-js versions'), but the actions are all upgrade-subtasks rather than a comprehensive set of distinct capabilities.

4 / 5

Completeness

Explicitly states both what ('Upgrade exa-js SDK versions and handle breaking changes safely') and when ('Use when upgrading the Exa SDK, detecting deprecations, or migrating'), plus concrete trigger phrases.

5 / 5

Trigger Term Quality

Lists natural user phrases with synonyms — 'upgrade exa', 'exa update', 'exa breaking changes', 'update exa-js', 'exa new version' — which a user would plausibly say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (exa-js SDK upgrade/migration) with distinctive exa-specific triggers, minimizing overlap with other skills.

5 / 5

Total

19

/

20

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.