CtrlK
BlogDocsLog inGet started
Tessl Logo

storybook-upgrade

Upgrade Storybook to a specific version (canary or release). Use this when upgrading Storybook packages in an external app, reproduction, or test project.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/storybook-upgrade/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

The content is actionable and well-structured for a simple single-purpose skill, with concrete npx commands covering common cases. Its main weakness is the absence of any validation or verification step for a batch package-upgrade operation.

Suggestions

Add a verification step after the upgrade (e.g., check package.json versions are in sync, run `npm ls @storybook/*`, or start Storybook to confirm it boots) to satisfy the batch-operation validation expectation.

Replace or supplement the unfilled <VERSION> placeholder in the Usage block with a one-line note on how to find a valid canary SHA or release version.

Trim the 'What it does' section, which largely restates the intro and the command behavior, to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and command-focused, with only minor redundancy between the intro, 'What it does', and 'Why this matters' sections that could be trimmed.

4 / 5

Actionability

Provides concrete executable commands across canary, latest, and specific-release examples, but the primary Usage block uses an unfilled <VERSION> placeholder with no guidance on locating a version/SHA.

4 / 5

Workflow Clarity

A rough sequence is described in 'What it does', but this is a batch operation (upgrades all @storybook/* packages) with no validation or verification checkpoint, capping the score at 3 per the destructive/batch guideline.

3 / 5

Progressive Disclosure

A short single-purpose skill with no bundle files and clear section headers; per the simple-skills note, well-organized sections alone warrant a 5.

5 / 5

Total

16

/

20

Passed

Description

82%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.

The description clearly communicates a specific niche and provides explicit what/when guidance with concrete trigger contexts. It is slightly limited on action breadth but otherwise strong.

DimensionReasoningScore

Specificity

Names the domain (Storybook) and one concrete action ('Upgrade Storybook to a specific version'), but does not enumerate multiple specific actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

Explicitly states what it does ('Upgrade Storybook to a specific version') and when to use it ('Use this when upgrading Storybook packages in an external app, reproduction, or test project') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage including 'Storybook', 'upgrading Storybook packages', 'canary or release', and 'external app, reproduction, or test project', though a few synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Storybook version upgrades) with distinct triggers, yielding minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
storybookjs/storybook
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.