changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/changelog-automation/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly communicates what the skill does and when to use it. It uses third person voice, includes specific concrete actions, references a well-known standard (Keep a Changelog), and provides an explicit 'Use when' clause with natural trigger terms. The description is concise yet comprehensive, covering the key use cases without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'changelog generation from commits, PRs, and releases', 'setting up release workflows', 'generating release notes', 'standardizing commit conventions'. Also references a specific format standard (Keep a Changelog). | 3 / 3 |
Completeness | Clearly answers both 'what' (automate changelog generation from commits, PRs, and releases following Keep a Changelog format) and 'when' (explicit 'Use when' clause covering release workflows, release notes, and commit conventions). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'changelog', 'commits', 'PRs', 'releases', 'release notes', 'release workflows', 'commit conventions', 'Keep a Changelog'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around changelog generation and release note automation. The specific mention of Keep a Changelog format, commits, PRs, and release workflows makes it unlikely to conflict with other skills like general git skills or CI/CD skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a skeleton that delegates all substantive content to an external playbook file while providing only vague, abstract instructions at the top level. It lacks any concrete code, commands, tool names, or specific examples that would make it actionable. The boilerplate sections (when to use, limitations) consume tokens without adding meaningful guidance.
Suggestions
Add concrete, executable examples: include at least one conventional commit format example, a sample tool configuration (e.g., conventional-changelog, release-please, or standard-version config), and a sample generated changelog output.
Replace the abstract instruction steps with specific commands and a clear workflow sequence, e.g., '1. Install release-please: `npm install release-please` 2. Configure `.release-please-manifest.json`...'
Remove or significantly trim the generic 'Limitations' section and 'Use/Do not use' sections — these consume tokens without teaching Claude anything it doesn't already know.
Bring key patterns from the implementation playbook into the main skill as a quick-start section so the skill is useful on its own without requiring the external file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is relatively brief but includes some unnecessary sections like 'Use this skill when' and 'Do not use this skill when' that are boilerplate rather than actionable content. The 'Limitations' section contains generic disclaimers that don't add value specific to changelog automation. | 2 / 3 |
Actionability | The instructions are entirely vague and abstract — 'Select a changelog format,' 'Enforce commit conventions,' 'Configure tooling' — with no concrete commands, code examples, tool names, or specific configuration snippets. There is nothing copy-paste ready or executable. | 1 / 3 |
Workflow Clarity | The steps are high-level directives without clear sequencing, specific tools, validation checkpoints, or error recovery. 'Review output for accuracy' is the only hint at validation but lacks any concrete mechanism. The workflow essentially says 'do the thing' without explaining how. | 1 / 3 |
Progressive Disclosure | There is a reference to `resources/implementation-playbook.md` for detailed patterns, which is good one-level-deep disclosure. However, the top-level content is so thin that it provides almost no useful overview — it's essentially an empty shell pointing elsewhere, making the reference feel like a crutch rather than progressive disclosure. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
93c57b2
- 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.