release-notes

Generates polished GitHub release notes for a ToolHive release by analyzing every merged PR, cross-referencing linked issues, dispatching expert agents to assess breaking changes, and producing a formatted release body. Use when the user provides a GitHub release URL, tag name, or says "release notes".

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/release-notes/SKILL.md

Quality

Content

65%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 detailed, well-sequenced multi-phase workflow with strong actionability, weakened by a missing bundle file, inlined reference-grade content, and the absence of an explicit completeness check for the batch PR-classification step.

Suggestions

Add an explicit completeness verification after Phase 2 classification: confirm the count of categorized PRs plus dependency PRs equals the total PRs listed in Phase 1 Step 3 before composing the release notes.

Provide the missing TEMPLATE.md file referenced in Phase 4, or inline the template structure directly — the link currently points to a file that does not exist in the bundle.

Tighten token budget by removing duplication: drop the Usage Examples section (it repeats the Arguments block) and consolidate the 'Omit empty sections' guidance to a single location.

Dimension	Reasoning	Score
Conciseness	Largely efficient and assumes Claude's competence (no explanation of gh, PRs, or releases), but contains minor redundancy — the Usage Examples section repeats the Arguments block and 'Omit empty sections' appears in both Phase 4 and Important Notes.	4 / 5
Actionability	Provides concrete executable commands (gh release view, gh api compare, gh pr view/diff, gh release edit) and specific expert-agent prompts, with minor gaps such as the placeholder git-tag prior-resolution one-liner and the missing template file.	4 / 5
Workflow Clarity	The five-phase sequence is clear with an approval gate before the destructive publish step, but this batch workflow (classifying every PR) lacks an explicit completeness verification that all PRs were accounted for, which the rubric caps at 3 for batch operations.	3 / 5
Progressive Disclosure	Section structure is well organized into phases, but the only external reference ([TEMPLATE.md](TEMPLATE.md)) is a broken pointer with no such file in the bundle, and detailed classification tables and agent mappings that could live in separate files are inlined.	3 / 5
	Total	14 / 20 Passed

Description

92%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 concretely states capabilities and provides explicit trigger guidance. Only minor weakness is trigger-term synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'analyzing every merged PR', 'cross-referencing linked issues', 'dispatching expert agents to assess breaking changes', 'producing a formatted release body' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ('Generates polished GitHub release notes...') and when ('Use when the user provides a GitHub release URL, tag name, or says "release notes"') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural triggers users would say — 'GitHub release URL, tag name, or says "release notes"' — but misses common synonyms like 'changelog' or 'what's changed', so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (ToolHive release notes generation) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: stacklok/toolhive
Path: .claude/skills/release-notes/SKILL.md
Commit: ccabad6

Reviewed: about 13 hours 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.