write-release-notes

Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. "write release notes for v1.32.0", "generate release notes for the latest release", "create changelog for v2.0").

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%Weight 40%Scale 1-5

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

A well-structured, highly actionable workflow with concrete scripts, a validation feedback loop, and clean sectioning. The only weakness is mild verbosity in the template and tone-guidelines sections that could be trimmed without losing clarity.

Suggestions

Tighten the embedded markdown template by replacing bracketed instructional prose (e.g. 'Be factual but upbeat', 'Use active voice') with terse field hints, since the Tone & Style section already covers these rules.

Consider consolidating the 11 Tone & Style bullets into 5-6 grouped rules (e.g. merge the 'no implementation details' and 'no PR/issue references' bullets under a single 'What to omit' rule) to reduce token load.

Move the contributors-filter core-team list and the fallback commit-listing command into a short reference block or keep them but trim the surrounding prose.

Dimension	Reasoning	Score
Conciseness	Largely efficient and free of concepts Claude already knows, but the embedded markdown template and the 11-bullet Tone & Style section carry some instructional padding ('Be factual but upbeat', descriptive placeholders) that could be tightened.	4 / 5
Actionability	Provides copy-paste-ready commands (fetch-release-data.sh, validate-release-notes.sh), a concrete categorization table, a fallback gh api command, and a fully specified output template — covering the common cases.	5 / 5
Workflow Clarity	A clear 7-step sequence (Fetch → Categorize → Write → Tone → Contributors → Validate → Output) with an explicit validation checkpoint and a FAIL→trim→re-run feedback loop in step 6.	5 / 5
Progressive Disclosure	Well-organized into numbered sections with two bundled scripts referenced by clear paths that map to real files in ./scripts/; references are one level deep and content is appropriately inline for a single-purpose skill.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

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

A strong, third-person description that states concrete capabilities and provides explicit trigger guidance with realistic example phrasings. It is concise yet comprehensive, with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Fetches the release from GitHub', 'retrieves every linked PR's title and description', 'synthesizes all changes into a polished, user-facing release note' — giving comprehensive coverage of the skill's behavior.	5 / 5
Completeness	Explicitly answers both 'what' (fetch release, retrieve PRs, synthesize notes) and 'when' with a clear 'Use when...' clause and concrete trigger examples, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrases ('write release notes for v1.32.0', 'generate release notes for the latest release', 'create changelog for v2.0') plus synonyms (release notes, changelog) and concrete version-tag examples.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (GitHub release notes for a version tag) with distinct triggers and version-tag examples, minimizing overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tailcallhq/forgecode
Path: .forge/skills/write-release-notes/SKILL.md
Commit: 6ed5d37

Reviewed: 24 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.