changelog-generator
Changelog Generator - Auto-activating skill for Technical Documentation. Triggers on: changelog generator, changelog generator Part of the Technical Documentation skill category.
35
3%
Does it follow best practices?
Impact
93%
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/changelog-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 repeats the skill name and category without providing any substantive information about what the skill does or when it should be used. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates changelogs from git commit history, formats entries by version, categorizes changes into added/changed/fixed/removed sections.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to generate a changelog, create release notes, summarize changes between versions, or update CHANGELOG.md.'
Include natural keyword variations users might say: 'changelog', 'release notes', 'version history', 'what changed', 'CHANGELOG.md', 'git log summary'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Changelog Generator') and its category ('Technical Documentation') but does not describe any concrete actions like parsing commits, formatting entries, or generating release notes. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name and completely lacks a 'when should Claude use it' clause with explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'changelog generator' repeated twice. It misses natural user phrases like 'changelog', 'release notes', 'what changed', 'version history', 'CHANGELOG.md', or 'generate changelog'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'changelog generator' is somewhat specific to a niche task, which reduces conflict risk slightly, but the lack of concrete actions and the broad 'Technical Documentation' category label could cause overlap with other 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 with no substantive content. It describes what a changelog generator skill would do in abstract terms but provides zero actual instructions, code examples, formats, or workflows. It is entirely non-functional as a skill file.
Suggestions
Add concrete changelog format examples (e.g., Keep a Changelog format) with actual markdown templates showing expected input (git log/commits) and output (formatted changelog entries).
Provide executable code or commands for generating changelogs, such as git log parsing commands, conventional commit parsing scripts, or integration with tools like conventional-changelog or auto-changelog.
Define a clear workflow: 1) gather commits since last release, 2) categorize by type (feat/fix/breaking), 3) generate formatted entries, 4) validate output structure.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual actionable content that teaches how to generate changelogs.
| 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 actionable content. Every token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples, no specific steps for generating changelogs. The 'capabilities' section lists vague promises ('step-by-step guidance', 'production-ready code') but delivers none of them. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill contains no process for actually generating a changelog. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no references to detailed materials, no structured sections with real content, and no navigation to supporting files. The sections that exist are purely boilerplate. | 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
4dee593
- 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.