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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill changelog-automationOverall
score
78%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities with a named standard (Keep a Changelog), includes an explicit 'Use when...' clause with multiple trigger scenarios, and targets a distinct niche in the release/changelog domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Automate changelog generation from commits, PRs, and releases' and specifies the format standard 'Keep a Changelog format'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Automate changelog generation from commits, PRs, and releases following Keep a Changelog format') AND when ('Use when setting up release workflows, generating release notes, or standardizing commit conventions') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'changelog', 'commits', 'PRs', 'releases', 'release workflows', 'release notes', 'commit conventions'. Good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on changelog generation and release workflows. The combination of 'changelog', 'Keep a Changelog format', and 'release notes' creates distinct triggers unlikely to conflict with general git or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise but critically lacks actionable content. It reads more like a table of contents than executable guidance—Claude would need to consult the referenced playbook for any actual implementation details. The instructions section provides only abstract direction without concrete commands, code examples, or tool-specific configurations.
Suggestions
Add at least one concrete, executable example (e.g., a conventional-commits config snippet or a GitHub Actions workflow fragment for changelog generation)
Include specific tool recommendations with actual commands (e.g., 'npx conventional-changelog -p angular -i CHANGELOG.md -s')
Provide a concrete commit message format example showing input commit and expected changelog output
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of concepts Claude already knows. Every section serves a purpose without padding. | 3 / 3 |
Actionability | The instructions are vague and abstract ('Select a changelog format', 'Configure tooling') with no concrete code, commands, or specific examples. It describes what to do rather than showing how. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence but lack validation checkpoints and specific details. 'Review output for accuracy' is too vague for a workflow involving automated generation. | 2 / 3 |
Progressive Disclosure | Clear structure with appropriate reference to external resource (implementation-playbook.md) for detailed content. The main file serves as a concise overview with one-level-deep navigation. | 3 / 3 |
Total | 9 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.