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.
80
Quality
78%
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 ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/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 well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities with a named standard (Keep a Changelog), and includes an explicit 'Use when...' clause with multiple natural trigger scenarios. The description is concise yet comprehensive.
| 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 trigger guidance. | 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, appropriately delegating detailed content to an external resource. However, it severely lacks actionability - the instructions are too abstract to be useful without concrete examples, specific tool configurations, or executable commands. The skill tells Claude what to do conceptually but not how to do it practically.
Suggestions
Add at least one concrete example of a conventional commit format and the expected changelog output it produces
Include specific tool commands or configuration snippets (e.g., for standard-version, semantic-release, or conventional-changelog)
Add a validation step to verify generated changelogs before publishing (e.g., checking for empty sections, proper formatting)
| 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, specific tool commands, and feedback loops for error recovery. The workflow is too high-level to be immediately executable. | 2 / 3 |
Progressive Disclosure | Clear structure with appropriate delegation to a single external resource (implementation-playbook.md) for detailed content. The main file serves as a concise overview with well-signaled reference. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- duclm1x1/Dive-Ai
- Commit
20ba150
- 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.