Tessl • The management layer for AI agent skills

SkillPublic

write-stories

The rules for writing Storybook stories in a project. They cover which states get a story, the imports, play functions, and mocks for network requests and modules.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

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

This is a well-designed thin delegating skill: lean, concrete, and unambiguous about running the project's story-writing rules command before writing stories. The only minor gap is the absence of a version-check method or failure fallback around the prerequisite and command steps.

Dimension	Reasoning	Score
Conciseness	The ~15-line body is lean and assumes Claude's competence: no explanation of what Storybook is or how stories work, and every line is an operative rule (version prerequisites, where to run commands, escalation, the exact command to run). Even the version detail ("11.0.0-alpha.x", "-beta.x or -rc.x", "0.0.0-pr-*") is required operational information, not padding.	5 / 5
Actionability	The core instruction is a copy-paste-ready command — "Run `npx storybook skills write-stories` in a command of its own, without `head` or `tail`, before you write a component or a story" — plus concrete skill invocations (/storybook-init, /storybook-upgrade), exact version patterns, and concrete escalation and working-directory guidance, fully covering the common case.	5 / 5
Workflow Clarity	The sequence — verify prerequisites (installed, 11.0+), run the command from the right package, handle sandbox/network, then follow the command's output — is clear, and the delegation design makes the single main action unambiguous. It is not a 5 because no method is given to verify the Storybook version and there is no fallback if the skills command fails or produces no output.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files; the project-specific rules are fetched dynamically via the npx command, so no static reference files are needed. Content is appropriately inlined and organized (numbered prerequisites followed by short standalone rules), meeting the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

66%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 is specific and domain-distinct with good natural terminology, but it lacks any explicit "when to use" trigger clause, which both caps completeness and leaves activation guidance implicit. Adding a concrete trigger sentence would resolve the main weakness.

Suggestions

Add an explicit trigger clause, e.g., "Use when writing or updating Storybook stories, adding play functions, or mocking network requests or modules for a story."

Include natural trigger synonyms such as "CSF", "Component Story Format", or ".stories.tsx" so the skill matches how users commonly refer to stories.

Lead with an active third-person verb (e.g., "Write Storybook stories following the project's rules for states, imports, play functions, and mocks") to state capabilities as actions rather than topics.

Dimension	Reasoning	Score
Specificity	The description lists several concrete coverage areas — "which states get a story, the imports, play functions, and mocks for network requests and modules" — giving specific, non-generic content. It falls short of a 5 because these are topic nouns rather than concrete actions the skill performs, and above a 3 because it covers more than 1-2 specific items.	4 / 5
Completeness	The "what" is clear — rules for writing Storybook stories covering states, imports, play functions, and mocks — but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The "when" is only weakly implied by the domain itself.	3 / 5
Trigger Term Quality	"Storybook stories", "play functions", and "mocks for network requests and modules" are natural terms users would say when needing this skill. It is not a 5 because common variations like "CSF", "Component Story Format", ".stories.tsx", or "story file" are absent.	4 / 5
Distinctiveness Conflict Risk	Storybook story-writing with play functions and mocks is a clear, mostly distinct niche. Minor overlap risk remains with closely related Storybook skills (the body references /storybook-init and /storybook-upgrade), keeping it below a 5.	4 / 5
	Total	15 / 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: storybookjs/storybook
Path: code/lib/claude-plugin/skills/write-stories/SKILL.md
Revision: 7c89155

Reviewed: 14 hours ago

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.

write-stories

Table of Contents

Is this your skill?