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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%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 concise, highly actionable single-purpose skill with executable examples for canary, latest, and pinned releases. Its main gap is the absence of any post-upgrade validation step for what is a batch package operation, plus minor redundancy between the Usage and Examples sections.

Suggestions

Add a verification checkpoint after the upgrade command (e.g., check that all @storybook/* packages resolve to the target version, or start Storybook to confirm it boots) to satisfy the batch-operation validation requirement.

Trim the redundancy between the generic Usage command ("npx storybook@<VERSION> upgrade") and the three concrete Examples, keeping one canonical form.

Clarify where the <SHA> for the pkg.pr.new canary example comes from (e.g., the Storybook PR that publishes the canary) so the command is fully self-contained.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanation of what Storybook is), but the Usage `<VERSION>` placeholder duplicates the Examples section and "What it does" partly re-states what the command already conveys, leaving minor trims available rather than every token earning its place.	4 / 5
Actionability	Three concrete, copy-paste-ready commands cover the common cases — canary ("npx --yes --allow-remote=all https://pkg.pr.new/storybook@<SHA> upgrade"), latest ("npx storybook@latest upgrade"), and a pinned release ("npx storybook@8.5.0 upgrade") — matching the fully executable anchor.	5 / 5
Workflow Clarity	"Upgrades all `@storybook/*` packages" is a batch operation, and the body includes no validation or verification checkpoint (e.g., confirming installed versions or starting Storybook after the upgrade), so the batch-operation cap of 3 applies despite the single-command simplicity.	3 / 5
Progressive Disclosure	At roughly 50 lines with no need for external references, the skill is well organized into clear sections (Usage, Examples, What it does, Important), satisfying the simple-skill exception for the top anchor.	5 / 5
	Total	17 / 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.

A strong, concise description with an explicit what-and-when structure and concrete trigger contexts. Its only weakness is modest action coverage — the skill is single-purpose, so only one action is named — and a few missing natural synonyms like "update" or "migrate Storybook".

Dimension	Reasoning	Score
Specificity	"Upgrade Storybook to a specific version (canary or release)" names the domain and a single concrete action with two variants, but does not list several distinct actions, matching the 1-2 concrete actions anchor rather than the several-actions anchor.	3 / 5
Completeness	It explicitly answers both what ("Upgrade Storybook to a specific version (canary or release)") and when ("Use this when upgrading Storybook packages in an external app, reproduction, or test project") with concrete trigger contexts, matching the top anchor.	5 / 5
Trigger Term Quality	Natural phrases like "upgrading Storybook packages", "canary", "release", and "external app, reproduction, or test project" give good coverage, though common synonyms such as "update Storybook" or "migrate Storybook" are missing, so it falls short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Storybook" is a specific named tool with distinct triggers (canary, release, Storybook packages), giving it a clear niche with minimal risk of triggering the wrong skill.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: storybookjs/storybook
Path: .agents/skills/storybook-upgrade/SKILL.md
Commit: dc9b30e

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.