changelog-generator
Changelog Generator - Auto-activating skill for Technical Documentation. Triggers on: changelog generator, changelog generator Part of the Technical Documentation skill category.
35
Quality
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 template placeholder with minimal useful content. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger term and boilerplate category mention provide no value for skill selection.
Suggestions
Add specific capabilities: 'Generates changelogs from git commit history, formats release notes, creates version summaries following Keep a Changelog format'
Add a 'Use when...' clause with natural triggers: 'Use when the user asks about release notes, version history, CHANGELOG.md, or needs to document what changed between versions'
Include varied trigger terms users would naturally say: 'changelog', 'release notes', 'version history', 'what's new', 'git log summary', 'CHANGELOG.md'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Changelog Generator') without describing any concrete actions. There are no specific capabilities listed like 'generates changelogs from git history' or 'formats release notes'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause. The 'Triggers on' section is redundant and doesn't provide meaningful guidance on when to select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('changelog generator, changelog generator') and miss natural variations users would say like 'release notes', 'version history', 'what changed', 'CHANGELOG.md', or 'git log'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'changelog' is somewhat specific to this domain, the lack of detail about what kind of changelogs or how they're generated could cause overlap with other documentation or git-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 template with no actual content about changelog generation. It contains only meta-descriptions of what a skill should do without any concrete guidance, examples, or actionable instructions. The entire content could be replaced with actual changelog format specifications, commit parsing examples, and version numbering guidance.
Suggestions
Add concrete changelog format examples (e.g., Keep a Changelog format, Conventional Commits parsing)
Include executable code for parsing git commits and generating changelog entries
Provide specific templates showing input (commits) and expected output (changelog sections)
Add validation criteria for changelog entries (required fields, formatting rules, version ordering)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about changelog generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code examples, no specific commands, no actual changelog format specifications. The skill describes what it claims to do rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for generating changelogs, no validation checkpoints, and no actual process to follow. The content is entirely meta-description without substance. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, no examples file, no format specifications. The content is a shallow placeholder with no depth or navigation to actual content. | 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.