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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured, but its instructions are abstract rather than executable and it points to a resource file (resources/implementation-playbook.md) that is missing from the bundle. Adding concrete tooling examples and creating the referenced playbook would most improve it.

Suggestions

Add concrete, executable guidance to the Instructions section — e.g., named tools (conventional-changelog, release-please, semantic-release) and example commands or config snippets instead of abstract steps like 'Configure tooling to generate and publish notes'.

Create the referenced resources/implementation-playbook.md (or remove the dangling reference) so the progressive-disclosure pointer resolves to a real file.

Strengthen workflow_clarity by adding an explicit validation/checkpoint step, such as verifying generated notes against actual commits before publishing, with a fix-and-retry loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no concept-explaining padding, assuming Claude's competence; every section (Use when / Do not use / Instructions / Safety / Resources / Limitations) earns its place.	3 / 3
Actionability	Instructions are high-level and abstract ('Select a changelog format', 'Configure tooling to generate and publish notes') with no concrete commands, named tools, or examples; it describes rather than instructs, though naming Keep a Changelog and commit conventions lifts it above pure vagueness.	2 / 3
Workflow Clarity	A clear 5-step sequence is present, but the only checkpoint is the soft 'Review output for accuracy', with no explicit validate→fix→retry loop, so checkpoints remain implicit.	2 / 3
Progressive Disclosure	The skill is short with well-organized sections and points detail to 'resources/implementation-playbook.md', but that referenced file does not exist in the bundle, so the one-level-deep navigation is broken.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it names a specific niche, uses natural trigger terms, and explicitly pairs 'what' with 'when'. It is only slightly limited by clustering actions around the single verb 'Automate' rather than enumerating more concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Automate changelog generation from commits, PRs, and releases', 'following Keep a Changelog format'), but the actions cluster around a single verb rather than listing multiple granular operations, so it is not fully comprehensive.	2 / 3
Completeness	Clearly states what it does (automate changelog generation following Keep a Changelog format) and gives an explicit 'Use when' clause covering release workflows, release notes, and commit conventions.	3 / 3
Trigger Term Quality	Covers natural terms users actually say — 'commits, PRs, and releases', 'release workflows', 'release notes', 'commit conventions' — giving good keyword coverage rather than a single term.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (changelog/release notes) with distinct triggers tied to commits, PRs, releases, and Keep a Changelog, making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 5e71bba

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.