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.
79
Quality
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/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 with good progressive disclosure to external resources. However, it severely lacks actionability - the main instructions are abstract guidance without any concrete code examples, specific tool configurations, or executable commands that would make this immediately useful.
Suggestions
Add concrete code examples for at least one changelog tool (e.g., conventional-changelog, release-please) with executable configuration snippets
Include a specific commit message format example with input/output like: 'feat(auth): add OAuth support' -> changelog entry
Provide a minimal working configuration file (e.g., .releaserc.json or release-please-config.json) that can be copy-pasted
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations. It assumes Claude understands concepts like conventional commits and semantic versioning without defining them. | 3 / 3 |
Actionability | The instructions are vague and abstract ('Select a changelog format', 'Configure tooling') with no concrete code, commands, or specific tool recommendations. Nothing is copy-paste ready or executable. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence but lack validation checkpoints, specific commands, or feedback loops. The workflow is more of a high-level checklist than actionable guidance. | 2 / 3 |
Progressive Disclosure | Clear structure with appropriate references to external resources (implementation-playbook.md) for detailed content. Navigation is well-signaled and one level deep. | 3 / 3 |
Total | 9 / 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
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.