CtrlK
BlogDocsLog inGet started
Tessl Logo

storybook

Use when: starting, checking, or using the Storybook dev server; looking up Primer React component stories, props, or documentation; previewing component variants; writing or verifying Storybook stories; using the primer-storybook MCP to explore components. Covers starting Storybook, checking if it is running, and using MCP tools (list-all-documentation, get-documentation, get-storybook-story-instructions, preview-stories) to look up components.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced skill body with executable commands and explicit validation checkpoints. The main improvement would be de-duplicating the rules that appear in both the workflow and the final Rules section to tighten token efficiency.

Suggestions

Remove the duplicated guidance in the Rules section that already appears as workflow steps (e.g. 'always call list-all-documentation before get-documentation' and 'never invent props'), keeping the Rules section only for rules not already stated inline.

If the tool table grows, consider moving the per-tool usage notes into a references file and keeping only the workflow in SKILL.md.

DimensionReasoningScore

Conciseness

Lean, executable body with no concept over-explanation; docked one point because the 'always list first', 'never invent props', and 'call instructions before writing' rules are restated in both the workflow and the Rules section.

4 / 5

Actionability

Copy-paste-ready curl/npm/poll commands, concrete MCP tool names, a tool_search regex pattern, and exact ID-format examples (e.g. 'components-button') make the guidance fully executable.

5 / 5

Workflow Clarity

Two clearly sequenced steps with explicit validation checkpoints (curl pre-flight, poll-until-ready) and error-recovery feedback ('will fail silently', 'never call get-documentation without an ID from this list').

5 / 5

Progressive Disclosure

Well-organized single-file structure with no external references needed; slightly over the 50-line simple-skill threshold and the tool table/workflow could in principle be split out, so it stops short of the idealized 5.

4 / 5

Total

18

/

20

Passed

Description

92%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 states both what the skill does and when to use it, with concrete trigger phrases and named MCP tools. The only minor gap is a lack of synonym/extension coverage, which keeps trigger term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (starting/checking/using the dev server, looking up stories/props/docs, previewing variants, writing stories) plus named MCP tools, giving comprehensive coverage.

5 / 5

Completeness

Explicit 'Use when:' trigger clause plus a clear 'what' ('Covers starting Storybook, checking if it is running, and using MCP tools ... to look up components') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural phrases like 'Storybook', 'component stories', 'props', 'previewing component variants', and 'writing Storybook stories'; not a 5 because the domain offers few synonyms/file extensions to cover.

4 / 5

Distinctiveness Conflict Risk

Narrow niche (Storybook + primer-storybook MCP) with distinctive triggers like 'Primer React component stories' makes accidental activation by other skills unlikely.

5 / 5

Total

19

/

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
primer/react
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.