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 placeholder that provides almost no useful information beyond the skill's name. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select it. The repeated trigger term and boilerplate category reference suggest this was auto-generated without human refinement.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates release notes from git history, changelogs, or version diffs. Formats version updates with categorized changes (features, 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 software releases.'
Include common variations of trigger terms users might say: 'changelog', 'version notes', 'what's new', 'release summary', 'software update notes', 'CHANGELOG.md'.
| 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 version updates'. | 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 wouldn't overlap heavily with most other skills, but the lack of detail about what it actually does and the generic 'Technical Documentation' category could cause confusion with other documentation-related 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 with no substantive content. It contains only meta-descriptions of what it claims to do without any actual instructions, code examples, templates, or workflows for generating release notes. It provides zero value to Claude as a skill file.
Suggestions
Add a concrete workflow for generating release notes, e.g., steps to gather commits/PRs, categorize changes, and format output with a specific template.
Include an executable example showing input (e.g., a list of git commits or PR titles) and expected output (a formatted release notes document in markdown).
Provide a release notes template with sections like 'Breaking Changes', 'New Features', 'Bug Fixes', 'Deprecations' and show how to populate each section.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual actionable content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no templates, no examples of actual release notes generation. The skill describes rather than instructs, offering only vague claims like 'provides step-by-step guidance' without any actual steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract bullet points claiming the skill 'provides step-by-step guidance' without delivering any. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to external files, and no structured navigation. The sections are superficial headers over repetitive placeholder text. | 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
c8a915c
- 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.