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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/create-storybook-docs/SKILL.md

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.

A lean, well-structured instruction skill with concrete code templates and explicit ordering. Its main weakness is the absence of a validation/verification step in the workflow, which both leaves the user without a correctness check and caps workflow clarity.

Suggestions

Add an explicit verification step at the end of the workflow, e.g. run the Storybook build or typecheck (`tsc --noEmit`) to confirm the new stories and MDX compile and render without errors.

Tighten the intro: the opening line ('Create or update Storybook stories and MDX documentation for Spark UI components.') duplicates the frontmatter description and could be removed or replaced with a one-line pointer to the canonical guidelines file.

Make the Meta definition example fully actionable by noting how `ComponentName` and the `Components/*` title are derived from the target component, so Claude can copy-paste with confidence.

Dimension	Reasoning	Score
Conciseness	The body is efficient — tight lists, code blocks, and no padding about what Storybook is — with only minor instances that could be trimmed (e.g., the opening line restates the description).	4 / 5
Actionability	Provides concrete, near-copy-paste templates (Meta definition block, Usage MDX block) and explicit ordered guidelines; minor gaps remain since templates use ComponentName placeholders and some guidance is declarative rather than executable.	4 / 5
Workflow Clarity	A clear sequence exists (stories file structure, then docs with an exact section order), but there is no validation or verification checkpoint (e.g., typecheck or Storybook render check), and writing multiple files is batch-like, so the score is capped at 3.	3 / 5
Progressive Disclosure	Well-organized with clearly signaled one-level references ('See documentation/contributing/WritingStories.mdx', 'Reference existing stories in...'); no bundle files exist, so all content is inline, leaving minor organization gaps versus a fully split structure.	4 / 5
	Total	15 / 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 description that clearly pairs a concrete capability statement with an explicit trigger clause, well-scoped to a distinct niche. The only soft spot is specificity, where the action verbs are fairly generic and could enumerate more concrete editing operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Spark UI component', 'Storybook') and a couple of concrete actions ('Create or update stories and documentation'), but the actions are generic verbs without comprehensive coverage of what editing entails.	3 / 5
Completeness	Explicitly states 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...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say — 'stories', 'storybook', 'documentation' — in the 'Use when' clause, but omits synonyms and file extensions like .stories.tsx or .doc.mdx.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'Spark UI component' Storybook work, a clear niche with distinct triggers and minimal overlap risk with unrelated skills.	5 / 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: ae95bee

Reviewed: 1 day 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.