CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

component-docs

Look up the components of a project with Storybook, with their props and usage examples, to answer questions about them or to reuse them instead of building duplicates. Use when the project's agent instructions (such as AGENTS.md) or the user ask for it. For a UI change, use ui-workflow, which includes the same component lookup.

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

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

An exemplary lean skill body: prerequisites with explicit fallbacks, execution context for monorepos and sandboxes, and a single copy-paste command as the entry point, with no wasted tokens. The only improvement space is minor executable detail, such as the command to check the Storybook version before deciding on the upgrade path.

DimensionReasoningScore

Conciseness

The ~15-line body is lean with zero padding and assumes Claude's competence; the version details ("11.0 or later", "11.0.0-alpha.x", "0.0.0-pr-*") are functional prerequisites for the skills subcommand, not date-conditional deprecated guidance, so every token earns its place.

5 / 5

Actionability

"Run `npx storybook skills component-docs` and follow its output" is copy-paste ready and branches (fallback to source files, monorepo package, sandbox escalation) are concrete, but no command is given to check the installed Storybook version and the fallback "read the components' source files instead" is high-level.

4 / 5

Workflow Clarity

A simple single-purpose skill with an unambiguous action and explicit fallback for every branch (not installed, older version with user-approval gate on /storybook-upgrade, blocked network); it is a read-only lookup so no validation loop is required.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and none exist in the bundle; the numbered prerequisites, execution-context notes, and final command are well organized for a skill of this size.

5 / 5

Total

19

/

20

Passed

Description

78%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 description with concrete third-person capabilities, an explicit use-when clause, and excellent conflict disambiguation against ui-workflow. Its main weakness is trigger phrasing: the when-clause leans on an indirect "ask for it" instead of naming concrete natural-language triggers like component library, existing components, or design system.

DimensionReasoningScore

Specificity

"Look up the components of a project with Storybook, with their props and usage examples", "to answer questions about them", and "reuse them instead of building duplicates" list several concrete third-person actions, though they cluster around a single lookup operation with minor coverage gaps.

4 / 5

Completeness

The description answers both what ("Look up the components... with their props and usage examples") and when ("Use when the project's agent instructions (such as AGENTS.md) or the user ask for it"), but the trigger phrase "ask for it" is indirect rather than a concrete trigger phrase.

4 / 5

Trigger Term Quality

Natural terms like "components", "Storybook", "props", "usage examples", "reuse", and "AGENTS.md" are present, but common variations such as "component library", "design system", or "existing components" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Storybook component lookup) and explicitly disambiguates from the closest related skill: "For a UI change, use ui-workflow, which includes the same component lookup."

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

storybookjs/storybook

Path

code/lib/claude-plugin/skills/component-docs/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.