release-notes-generator
Release Notes Generator - Auto-activating skill for Technical Documentation. Triggers on: release notes generator, release notes generator Part of the Technical Documentation skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/release-notes-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that provides almost no useful information for skill selection. It merely restates the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. Claude would struggle to know when to select this skill over others.
Suggestions
Add specific actions the skill performs, e.g., 'Generates release notes by analyzing git commits, categorizing changes (features, fixes, breaking changes), and formatting them in standard changelog format.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about changelogs, version notes, release summaries, what's new documentation, or preparing release announcements.'
Add keyword variations users might naturally say: 'changelog', 'version history', 'what changed', 'release summary', 'CHANGELOG.md', 'version bump notes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Release Notes Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of analyzing commits, formatting notes, categorizing changes, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use cases or trigger guidance beyond the skill name itself). | 1 / 3 |
Trigger Term Quality | The 'Triggers on' field redundantly lists 'release notes generator' twice, providing no natural keyword variations. Missing obvious terms like 'changelog', 'version notes', 'what's new', 'release summary', or 'version history'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'release notes' is a somewhat specific domain, the lack of detail about what distinguishes this from general documentation skills or changelog tools creates moderate overlap risk with other Technical Documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell containing only meta-description and trigger phrases without any actual instructional content. It fails completely as a skill because it provides zero actionable guidance on how to generate release notes - no templates, no examples, no format specifications, no workflow for extracting changes from commits or issues.
Suggestions
Add a concrete release notes template with sections (e.g., Features, Bug Fixes, Breaking Changes, Deprecations) and example entries
Include executable code or commands for extracting changes from git commits, PRs, or issue trackers
Define a clear workflow: 1) Gather changes 2) Categorize by type 3) Write user-facing descriptions 4) Format output
Provide example input (e.g., list of commits) and expected output (formatted release notes) to make the skill actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about release notes generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code examples, no templates, no specific commands, no actual release notes format or structure. The content describes what the skill supposedly does without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for generating release notes, no process for gathering changes, no validation of output format. The skill claims to provide 'step-by-step guidance' but contains zero steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual content to organize. There are no references to detailed materials, examples, or templates that would be expected for a release notes generator. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.