CtrlK
BlogDocsLog inGet started
Tessl Logo

minor-release

Write the changelog entry for a new minor or major Storybook release. Use when preparing a CHANGELOG.md entry for a X.Y.0 version.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/minor-release/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-sequenced changelog-writing skill with concrete commands and useful style examples. The main weaknesses are minor verbosity in the guardrail rules and an optional rather than enforced validation checkpoint.

Suggestions

Tighten the first Rules bullet to a single directive (e.g., "The two helper scripts live at <paths>; just run them — do not read their source or search elsewhere."),

Promote --dry-run to an explicit Step 4 checkpoint ("Run with --dry-run, review the composed section, then run without --dry-run to write") to add a clear validate-then-write feedback loop.

Consider trimming one of the three full examples (e.g., keep 10.3.0 and 10.0.0, summarize 10.1.0) to reduce token cost while preserving single- and multi-group plus major-version coverage.

DimensionReasoningScore

Conciseness

Mostly lean instructional content with no concept-padding, but the first Rules bullet is wordy ("Do not search... Do not look in... Do not read the script source") and three full multi-line examples could be trimmed; fits the efficient-with-minor-trims anchor rather than a 5.

4 / 5

Actionability

Provides copy-paste-ready commands (get-summary, write-section) with [version], --verbose, --dry-run, and a complete stdin heredoc example covering the common cases; fully executable.

5 / 5

Workflow Clarity

A clear four-step sequence with a --dry-run verification checkpoint before the potentially section-overwriting write; not a 5 because the dry-run is offered as an option rather than an enforced validate-then-write feedback loop.

4 / 5

Progressive Disclosure

A single well-organized file with clearly labeled sections (Rules, Steps 1-4, Writing style, Examples) and no nested references; the inlined examples are justified as the authoritative style reference, fitting good-structure-with-minor-gaps rather than a 5 since nothing is split out.

4 / 5

Total

17

/

20

Passed

Description

73%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 clear, third-person description that answers both what and when for a well-scoped niche. It is short on action breadth (one action) and lacks synonyms such as "release notes".

Suggestions

Add one or two more concrete actions (e.g., "select highlights and compose the highlights section") to lift specificity toward a 4-5.

Broaden the trigger with natural user phrasing and synonyms, e.g. "Use when the user asks to write or draft release notes / changelog entries for a Storybook X.Y.0 release."

DimensionReasoningScore

Specificity

Names the domain ("new minor or major Storybook release") and one concrete action ("Write the changelog entry"), matching the domain-plus-1-2-actions anchor; not a 4 because only a single action is given rather than several.

3 / 5

Completeness

Explicitly states both what ("Write the changelog entry for a new minor or major Storybook release") and when ("Use when preparing a CHANGELOG.md entry for a X.Y.0 version"); not a 5 because the trigger does not enumerate user-mention scenarios.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ("changelog entry", "CHANGELOG.md", "Storybook", "minor or major release", "X.Y.0 version") with good coverage; not a 5 because synonyms like "release notes" are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear narrow niche (Storybook X.Y.0 release changelog) with distinct triggers and minimal conflict risk, including explicit scoping away from patch releases.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
storybookjs/storybook
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.