CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docs-review

Review, improve, rewrite, author, or plan Storybook documentation in /docs. Use this when asked to review docs, improve a page, rewrite documentation, draft new docs, or advise on docs strategy.

Quality

90%

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.

The body is a well-engineered routing document: a clear two-phase workflow with explicit validation feedback loops, concrete mode-mapping tables, and disciplined offloading of detail to four appropriately-scoped reference files. Its only flaw is minor redundancy in repeating style-guide loading instructions and mode definitions across sections.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains what Storybook or doc types are — but has minor redundancy: storybook-style.md loading instructions appear in three places (reference table, Step 5, Step 6) and mode routing recurs across Steps 1, 4, and 5. This fits 'efficient; minor instances that could be trimmed' rather than 'every token earns its place'.

4 / 5

Actionability

Provides copy-paste commands ('yarn fmt:write', 'yarn docs:check'), a concrete request-pattern-to-mode routing table, explicit intervention thresholds, and a specified strategy-mode deliverable checklist — fully actionable instruction-only guidance with no gaps.

5 / 5

Workflow Clarity

Seven explicitly sequenced steps cleanly split into diagnosis (1-4) and action (5-7), with an explicit validate -> fix -> re-run feedback loop ('Fix any errors reported by yarn docs:check, then run it again to confirm') and clear conditions for skipping validation.

5 / 5

Progressive Disclosure

SKILL.md is a workflow-only overview routing to four real reference files (all verified present) via a File/Owns/When-to-Load table; references are one level deep and ownership rules prevent overlap — clear overview with well-signaled references and easy navigation.

5 / 5

Total

19

/

20

Passed

Description

87%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: it names a specific domain and five concrete actions, and pairs them with an explicit 'Use this when' clause containing natural trigger phrases. The only weaknesses are slightly abstract action verbs and a few missing common synonyms like 'edit' or 'write'.

DimensionReasoningScore

Specificity

Lists five named actions ('Review, improve, rewrite, author, or plan Storybook documentation in /docs'), matching the anchor for several specific actions with minor gaps — e.g. snippet editing covered in the body is absent, and the verbs are more abstract than anchor-5's mechanical actions.

4 / 5

Completeness

Explicitly answers both 'what' (five documentation actions scoped to Storybook docs in /docs) and 'when' ('Use this when asked to review docs, improve a page, rewrite documentation, draft new docs, or advise on docs strategy') with concrete trigger phrases, exactly matching the anchor-5 example.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('review docs', 'improve a page', 'rewrite documentation', 'draft new docs', 'advise on docs strategy'), giving good keyword coverage, though common variants like 'edit', 'write', or 'fix formatting' are missing — so not the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly delimited ('Storybook documentation in /docs') with distinct trigger phrasing, giving minimal conflict risk with generic writing or editing skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

storybookjs/storybook

Path

.agents/skills/docs-review/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.