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
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 boilerplate template with no substantive content beyond the skill name. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The repeated trigger term and generic category label provide almost no value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates release notes from git commit history, pull requests, and changelogs. Formats version summaries with categorized changes (features, bug fixes, breaking changes).'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about release notes, changelogs, version summaries, what's new documentation, or needs to document changes between software versions.'
Remove the redundant duplicate trigger term and expand with natural variations users would say, such as 'changelog', 'version notes', 'release summary', 'what changed', '.md release docs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Technical Documentation') and the skill name ('Release Notes Generator') but does not describe any concrete actions. There are no specific capabilities listed like 'summarizes changelogs', 'extracts commit history', or 'formats release notes'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just the skill name repeated. There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'release notes generator' repeated twice. It misses natural variations users would say like 'changelog', 'release summary', 'version notes', 'what's new', or 'release documentation'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'release notes' is somewhat specific and unlikely to conflict with many other skills, but the lack of detail about what it actually does (e.g., does it generate from git logs? from JIRA tickets?) makes it somewhat ambiguous within a documentation skill category. | 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 placeholder with no substantive content. It contains only generic boilerplate descriptions that restate the skill name without providing any actionable guidance, concrete examples, templates, or workflows for generating release notes. It fails on every dimension of the rubric.
Suggestions
Add a concrete release notes template with sections (e.g., New Features, Bug Fixes, Breaking Changes, Deprecations) and example entries showing the expected format and tone.
Include an executable workflow: e.g., 1) Parse git log/changelog, 2) Categorize changes by type, 3) Generate markdown output, 4) Validate against a schema or checklist—with actual code or commands for each step.
Provide at least one complete input→output example (e.g., given a list of commits or PR descriptions, produce a formatted release notes document).
Remove all generic boilerplate ('This skill provides automated assistance...', 'Follows industry best practices...') and replace with domain-specific, actionable content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, contains no domain-specific information, and every section restates the same vague concept ('release notes generator') without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no templates, no examples of actual release notes, no format specifications. Every bullet point is abstract and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to disclose progressively. | 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
3a2d27d
- 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.