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.
54
61%
Does it follow best practices?
Impact
—
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 its purpose, uses natural trigger terms, and includes an explicit 'Use when' clause. It follows third-person voice, names a specific standard (Keep a Changelog), and covers the key scenarios that would lead a user to need this skill. The description is concise yet comprehensive.
| 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 | Occupies a clear niche around changelog generation and release note automation. The specific mention of Keep a Changelog format, commits, PRs, and release workflows makes it highly distinguishable from general git or documentation 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 table of contents with no substantive content. It lacks any concrete examples, executable code, specific tool recommendations (e.g., conventional-changelog, release-please, standard-version), commit format templates, or configuration snippets. The body defers all useful content to a referenced playbook that doesn't exist in the bundle, leaving the skill nearly useless on its own.
Suggestions
Add concrete examples of conventional commit formats (e.g., `feat(auth): add JWT support`) and a sample Keep a Changelog output block.
Include at least one specific tool recommendation with executable configuration (e.g., a `release-please` config or `conventional-changelog` CLI command).
Replace the abstract instruction steps with a concrete workflow: e.g., 1) configure commitlint, 2) set up changelog generator, 3) validate output with specific commands.
Remove the generic 'Limitations' boilerplate and use those tokens for actionable content instead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Use this skill when' and 'Do not use this skill when' sections add moderate value but are somewhat verbose for what they convey. The 'Limitations' section contains generic boilerplate that doesn't add skill-specific value. The instructions themselves are lean but vague. | 2 / 3 |
Actionability | The instructions are entirely abstract ('Select a changelog format', 'Enforce commit conventions', 'Configure tooling') with no concrete commands, tool names, code examples, configuration snippets, or specific commit format templates. There is nothing executable or copy-paste ready. | 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 vague and there's no feedback loop for fixing issues. The workflow essentially says 'do the thing' without showing how. | 1 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for detailed content, which is a reasonable one-level-deep reference. However, no bundle files are provided, so we can't verify the reference exists or contains useful content. The main file itself is too thin — it defers almost everything to the playbook without providing a useful quick-start overview. | 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
f5dc9e3
- 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.