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.
60
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.cursor/skills/create-storybook-docs/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its domain (Storybook + Spark UI) and includes an explicit 'Use when' clause with natural trigger terms. The main weakness is that the capability listing could be more granular—it stays at a high level with 'create or update' rather than enumerating specific actions like configuring controls, writing MDX, or adding interaction tests.
Suggestions
Add more specific concrete actions such as 'configure args/controls', 'write MDX documentation pages', or 'add interaction tests' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Storybook stories for Spark UI components) and some actions (create, update stories and documentation), but doesn't list more granular concrete actions like 'add interaction tests', 'configure args/controls', or 'write MDX docs'. | 2 / 3 |
Completeness | Clearly answers both 'what' (create or update Storybook stories and documentation for Spark UI components) and 'when' (explicit 'Use when' clause covering adding stories, updating documentation, or improving component documentation in Storybook). | 3 / 3 |
Trigger Term Quality | Includes natural keywords a user would say: 'Storybook', 'stories', 'documentation', 'Spark UI component', 'add stories', 'update documentation', 'component documentation'. These cover the most common ways a user would phrase such requests. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Storybook', 'stories', and 'Spark UI component' creates a clear niche that is unlikely to conflict with other skills. The specificity to both the tool (Storybook) and the component library (Spark) makes it highly distinctive. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable structural guide for creating Storybook stories and MDX documentation with clear ordering conventions and some concrete code snippets. However, it falls short on full actionability (examples are partial templates), lacks validation/verification steps for confirming stories work correctly, and includes some content that could be tightened or better organized with clearer references to supporting files.
Suggestions
Add a complete, end-to-end example showing a full stories file and corresponding MDX file for a simple component, rather than just fragments.
Include a validation step such as 'Run `npm run storybook` and verify the component renders in all story variants before committing'.
Make the reference to existing examples more specific — link to one concrete component's stories file as a canonical example rather than using a glob pattern.
Remove or condense the 'When to Use' section since trigger conditions are better handled by the skill's YAML metadata, not the body content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary scaffolding like the 'When to Use' section which is more about triggering conditions than actionable instruction. The bullet lists are reasonably tight but could be tighter. | 2 / 3 |
Actionability | Provides concrete code snippets for Meta definition and MDX usage sections, but many instructions are descriptive rather than executable (e.g., 'Include all variants and states', 'Document each sub-component separately'). The stories and MDX examples are partial templates rather than fully copy-paste ready examples. | 2 / 3 |
Workflow Clarity | The ordering of sections and stories is clearly specified, which is helpful. However, there's no validation or verification step — no guidance on how to confirm stories render correctly, no feedback loop for catching errors in MDX syntax or story configuration. | 2 / 3 |
Progressive Disclosure | References `documentation/contributing/WritingStories.mdx` and existing component stories as further reading, which is good. However, the inline content is somewhat lengthy for an overview, and the references at the end are vague ('Reference existing stories in packages/components/src/*/...') rather than clearly signaled with specific file links. | 2 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- leboncoin/spark-web
- Commit
76a3678
- 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.