create-storybook-docs

Create or update Storybook stories and documentation for a Spark UI component. Use when the user wants to add stories, update documentation, or improve component documentation in Storybook.

Quality

81%

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

68%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 a compact, well-structured instruction set with concrete code snippets and exact ordering rules for both stories and MDX documentation. Its main weakness is workflow clarity: there is no cross-file sequence or validation/verification step (such as confirming stories render), and a few directives remain abstract.

Suggestions

Add a short end-to-end sequence (e.g., check for an existing stories/doc file first, write the stories file, then the doc file, then verify by rendering or building Storybook) so the workflow has explicit checkpoints.

Include one complete worked example of a story (e.g., a Default story with play function or args) and a minimal ArgTypes usage snippet to make the abstract directives like 'Include all variants and states' concrete.

Trim the 'When to Use' section, which repeats the frontmatter description, and consolidate the Reference and Examples sections into one clearly labeled pointer to the repo's canonical guidelines.

Dimension	Reasoning	Score
Conciseness	The body is lean and list-driven with no re-teaching of concepts Claude already knows (e.g., what Storybook is). Minor redundancy: the 'When to Use' section largely restates the frontmatter description, which could be trimmed, so anchor 4 fits better than 5.	4 / 5
Actionability	Provides an executable Meta code snippet, exact section ordering for the doc file, and a copy-adaptable MDX usage block. Some guidance remains vague ('Include all variants and states', 'Document each sub-component separately') with no full worked story example, keeping it below anchor 5.	4 / 5
Workflow Clarity	Steps are listed per file (e.g., 'Required Stories (in order)', exact doc section ordering) but there is no overall sequence across the two deliverables and no verification checkpoint (e.g., confirming stories render or docs build). This matches anchor 3: sequence present but checkpoints missing or implicit.	3 / 5
Progressive Disclosure	The body is well-organized into clear sections, and its references ('documentation/contributing/WritingStories.mdx', 'packages/components/src/*/ComponentName.stories.tsx') are one level deep and clearly signaled under dedicated Reference and Examples headings. No bundle files exist, and the small amount of inline content is appropriately placed, though referencing external repo paths rather than bundled detail files leaves minor organization gaps versus anchor 5.	4 / 5
	Total	15 / 20 Passed

Description

83%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 states both what it does and when to use it, with concrete trigger phrasing and a well-scoped niche around Spark UI components in Storybook. Minor gaps in keyword coverage (no file extensions or synonyms like MDX/docs) keep trigger term quality and specificity just below top marks.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ('Create or update Storybook stories and documentation for a Spark UI component'), with only minor coverage gaps (e.g., MDX docs are mentioned in the body but not the description). It lists several specific actions but is not fully comprehensive, matching anchor 4 rather than 5.	4 / 5
Completeness	Explicitly answers both: what ('Create or update Storybook stories and documentation for a Spark UI component') and when ('Use when the user wants to add stories, update documentation, or improve component documentation in Storybook') with concrete trigger phrases, matching anchor 5 exactly.	5 / 5
Trigger Term Quality	Natural phrases like 'add stories', 'storybook', and 'update documentation' would be said by users needing this skill. A few natural terms are missing (synonyms like 'docs', file patterns like '.stories.tsx' or 'MDX'), so it falls between anchors 3 and 5, noticeably above the midpoint.	4 / 5
Distinctiveness Conflict Risk	'Spark UI component' plus 'Storybook' carves a clear niche with minimal conflict risk, but the generic term 'documentation' leaves minor overlap with general documentation skills, so anchor 4 fits better than 5.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: leboncoin/spark-web
Path: .cursor/skills/create-storybook-docs/SKILL.md
Commit: da35814

Reviewed: 12 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.