release-notes

Use when a change may need a .changes note, the Release note gate fails, or deciding whether type: internal or no-release-note applies.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%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 compact, highly actionable reference skill with an executable template and verify command, well-structured with one-level-deep external pointers. The only gap is an explicit feedback loop for when the release-note gate fails validation.

Suggestions

Add an explicit feedback loop under Verify: if `pnpm run release:notes:validate` fails, read the error, fix or label the note, and re-run until it passes.

Dimension	Reasoning	Score
Conciseness	The body is lean: a format spec, a concrete frontmatter template, the type enum, exemption globs, and one verify command, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	It provides a copy-paste-ready frontmatter template, the exact file pattern `.changes/<area>-<slug>.md`, a concrete type enum, specific exemption globs, and the executable command `pnpm run release:notes:validate`.	5 / 5
Workflow Clarity	The flow is clear (author a matching note, skip/label if exempt, then verify) with an explicit Verify checkpoint, but it lacks an explicit validate-fix-retry feedback loop for gate failures.	4 / 5
Progressive Disclosure	A simple, well-sectioned skill under 50 lines that points one level deep to `.changes/README.md` for full format and `tools/release/check-release-note-gate.mjs` for gate policy, both clearly signaled.	5 / 5
	Total	19 / 20 Passed

Description

73%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 tightly scoped, trigger-rich description that excels at 'when' guidance and distinctiveness, but it leans on implied capability rather than stating concrete actions. Adding one explicit 'what' verb (e.g., "Write or label .changes release notes") would lift completeness and specificity.

Suggestions

Lead with an explicit capability verb (e.g., "Author or label .changes release notes") before the 'Use when' clause so 'what' is stated, not implied.

Add a natural synonym such as "changelog" to broaden trigger coverage for users who phrase it that way.

Dimension	Reasoning	Score
Specificity	The description names the domain (release notes / .changes notes) and several concrete decision points ("Release note gate fails", "type: internal", "no-release-note"), but it is trigger-focused rather than enumerating concrete capabilities, so it is not comprehensive.	3 / 5
Completeness	It has an explicit, multi-trigger "Use when..." clause answering 'when', but the 'what' (writing/deciding on release notes) is only implied rather than stated, so it falls short of a fully explicit what-and-when answer.	4 / 5
Trigger Term Quality	Phrases like "a change may need a .changes note", "Release note gate fails", and "type: internal or no-release-note" are natural terms a developer in this repo would say; a few common synonyms (e.g., "changelog") are absent.	4 / 5
Distinctiveness Conflict Risk	The niche is clearly scoped to release-note gating with distinctive triggers ("Release note gate fails", "no-release-note", "type: internal") that are unlikely to fire for unrelated skills.	5 / 5
	Total	16 / 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: 4gray/iptvnator
Path: .claude/skills/release-notes/SKILL.md
Commit: 9a3aa63

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