changelog-creator
Changelog Creator - Auto-activating skill for DevOps Basics. Triggers on: changelog creator, changelog creator Part of the DevOps Basics skill category.
35
3%
Does it follow best practices?
Impact
92%
0.96xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/changelog-creator/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 extremely minimal and fails to communicate what the skill does or when it should be selected. It reads more like a label than a functional description, providing no concrete actions, no natural trigger terms beyond the skill name, and no explicit usage guidance.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates changelogs from git commit history, formats release notes, and updates CHANGELOG.md files.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a changelog, generate release notes, summarize commits, or update CHANGELOG.md.'
Remove the redundant duplicate trigger term ('changelog creator' listed twice) and expand with natural variations users might say, such as 'release notes', 'version history', 'git log summary'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Changelog Creator') without describing any concrete actions. There is no mention of what it actually does—no verbs like 'generates', 'parses', 'formats', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term is 'changelog creator' repeated twice. It misses natural variations users would say like 'changelog', 'release notes', 'version history', 'CHANGELOG.md', 'generate changelog', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Changelog Creator' is somewhat specific to a niche (changelog generation), which reduces conflict risk slightly, but the lack of concrete detail means it could overlap with other DevOps or 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—a template with placeholder text that provides no actual instruction on creating changelogs. It contains no executable code, no changelog format examples, no tool recommendations, and no concrete workflow. It reads as auto-generated boilerplate with zero educational or operational value.
Suggestions
Add concrete changelog format examples (e.g., Keep a Changelog format) with actual markdown templates showing expected input/output
Include executable commands or scripts for auto-generating changelogs from git history (e.g., `git log --oneline --since='last tag'` or tools like conventional-changelog)
Define a clear workflow: 1) gather commits since last release, 2) categorize changes (feat/fix/breaking), 3) format into changelog entry, 4) validate against Keep a Changelog spec
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual instructional 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, commands, or concrete guidance. Every token is wasted on describing the skill rather than teaching anything. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no examples of changelog formats, no concrete steps for creating a changelog. The 'capabilities' section describes what it could do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain only boilerplate descriptions. There are no references to external files, no structured content to navigate, and no meaningful organization of actual instructional material. | 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
1531b64
- 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.