CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-stories

Run the Storybook story tests of a project, with their accessibility checks, and fix what fails.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./code/lib/claude-plugin/skills/test-stories/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, delegation-style skill body: every line adds non-obvious operational guidance (version gates, monorepo cwd, sandbox escalation, no head/tail) and the main action is a single unambiguous command. The only deductions are minor — version-pattern verbosity and failure-handling specifics deferred to the command's output rather than written inline.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what Storybook is, and lines like 'Run every Storybook CLI command from the package where Storybook is installed (in a monorepo often a leaf package such as packages/ui)' deliver non-obvious, high-value guidance. The prerelease version-pattern enumeration ('11.0.0-alpha.x, -beta.x or -rc.x', '0.0.0-pr-*') is version-number detail that could be tightened, keeping it below anchor 5.

4 / 5

Actionability

The core guidance is a concrete, copy-paste-ready command — 'Run npx storybook skills test-stories in a command of its own, without head or tail' — with precise execution conditions (correct package, sandbox escalation). However, the specifics of handling failing tests and accessibility violations are delegated to the command's output rather than stated, a minor gap versus anchor 5's 'specific examples cover the common cases'.

4 / 5

Workflow Clarity

Prerequisites are a clearly numbered, conditionally gated sequence (install via /storybook-init only with approval; version floor with upgrade rules), followed by one unambiguous main action. The fix-failures feedback loop — central to the skill's purpose — is only implicit in the body ('follow its output ... how to handle failing tests'), a minor validation gap versus anchor 5; the no-cap contexts (destructive/batch/XML/DB) do not apply, so it sits above anchor 3.

4 / 5

Progressive Disclosure

This is a sub-50-line single-file skill with no bundle directories, and its details are delegated exactly one level deep and clearly signaled: the CLI command's output for test-running/failure handling, and /storybook-init and /storybook-upgrade with explicit conditions. Per the rubric's simple-skill note, well-organized short content with no need for external references scores 5.

5 / 5

Total

17

/

20

Passed

Description

70%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 concise, third-person description with concrete actions and a distinct, well-scoped niche. Its main weakness is the complete absence of 'when to use this' trigger guidance, which both caps completeness and leaves trigger-term coverage short of synonyms like 'a11y'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to run story tests, Storybook tests, a11y/accessibility checks on stories, or to fix failing stories.'

Include common synonyms users actually say — 'a11y', 'test stories', 'interaction tests', 'Storybook test-runner' — to broaden trigger-term coverage.

Optionally mention the scope of fixes (e.g. story code, a11y violations) to sharpen the 'what' toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('Storybook story tests') and three concrete actions — 'Run the Storybook story tests', 'with their accessibility checks', 'fix what fails' — with only minor gaps such as setup/upgrade handling. It lists several specific actions rather than the 1-2 of anchor 3, but is not comprehensive enough for anchor 5.

4 / 5

Completeness

The 'what' is clear (run story tests with accessibility checks and fix failures), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not anchor 2 because the 'what' is concrete, not vague; not anchor 4 because 'when' is entirely absent rather than just implicit.

3 / 5

Trigger Term Quality

Includes natural phrases users would say — 'Storybook', 'story tests', 'accessibility checks', 'fix what fails' — but misses common variations like 'a11y', 'test stories', or 'interaction tests'. Good coverage with a few natural terms missing matches anchor 4; anchor 5 requires synonyms and extensions.

4 / 5

Distinctiveness Conflict Risk

The Storybook story-test-with-accessibility niche is highly specific with distinct triggers, so it is unlikely to fire for unrelated test or a11y skills. Clear niche with minimal conflict risk matches anchor 5; anchor 4 would require some overlap with closely related skills.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

storybookjs/storybook

Path

code/lib/claude-plugin/skills/test-stories/SKILL.md

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.