CtrlK
BlogDocsLog inGet started
Tessl Logo

release-notes-generator

Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.

65

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 ./examples/skills/release-notes-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 actionable and well-structured with real bundle references, but loses points for inlined content that duplicates bundle files and for missing validation checkpoints on a batch/write workflow.

Suggestions

Remove the inlined tech-to-product and commit-categories tables (and the CHANGELOG template block) from SKILL.md, keeping only brief summaries that point to the existing reference/asset files to reduce token duplication.

Add an explicit validation checkpoint to the workflow — e.g., 'Review generated notes; confirm PR/Slack output before writing CHANGELOG.md or creating the PR/tag' — as a verify-then-proceed step.

Replace the large ASCII migration-alert box with a compact template and move the full formatting detail into an asset file.

DimensionReasoningScore

Conciseness

The body is information-dense but inlines the tech-to-product and commit-categories tables and a CHANGELOG template that already exist in references/assets, plus a large ASCII migration-alert box — duplicated/padded content that could be tightened.

3 / 5

Actionability

Provides concrete executable commands ('git tag --sort=-v:refname | head -n 1', 'gh api repos/{owner}/{repo}/pulls/{number}', 'git diff <last-tag>..HEAD --name-only -- migrations/'), with minor gaps from placeholders and reliance on repo-specific template paths that are not bundled.

4 / 5

Workflow Clarity

Steps are sequenced, but this batch operation (many commits/PRs) with write actions (CHANGELOG, PR, git tag) lacks explicit validation/verification checkpoints, capping workflow clarity at 3 per the batch/destruction rule.

3 / 5

Progressive Disclosure

Real, clearly-signaled one-level-deep references ('Reference Files' section lists assets/changelog-template.md, assets/slack-template.md, references/tech-to-product-mappings.md, references/commit-categories.md), with a minor gap being the CHANGELOG template duplicated inline and as an asset.

4 / 5

Total

14

/

20

Passed

Description

96%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 states concrete capabilities and provides explicit, natural trigger phrases covering both 'what' and 'when'. Only minor overlap risk with closely related changelog skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits', 'Automatically categorizes changes', 'converts technical language to user-friendly messaging' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers 'what' (generate/categorize/transform release notes) and 'when' with concrete trigger phrases via the 'Use for…' clause.

5 / 5

Trigger Term Quality

'Use for releases, changelogs, version notes, what's new summaries, or ship announcements' provides comprehensive natural synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The 3-format output plus tech-to-product transformation is a clear niche with distinct triggers, but 'changelogs'/'release notes' overlap slightly with generic changelog-generator skills.

4 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
FlorianBruniaux/claude-code-ultimate-guide
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.