release-note-publisher

Draft, refine, and publish bilingual PigeonPod GitHub release notes from commits on the `release` branch. Use when Codex needs to compare commits since the latest published GitHub release, write a new local release note under `dev-docs/release-notes`, align English and Chinese release-note sections after user edits, or create/update a GitHub Release while keeping the markdown H1 as the GitHub release title instead of the release body.

Quality

92%

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, actionable skill body with a clear sequenced workflow, real validation checkpoints, and clean progressive disclosure into a reference and two scripts. The only nit is mild rule duplication between SKILL.md and the style reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but a few rules (H1-as-title handling, omitting Breaking Changes/issue numbers) are restated in SKILL.md despite already appearing in references/release-style.md, which could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for both collect and publish steps with concrete flags (`--repo`, `--branch`, `--notes-file`, `--tag`, `--dry-run`), covering the common cases.	5 / 5
Workflow Clarity	Five clearly sequenced steps with explicit checkpoints: a user review/edit loop in step 4 and a dry-run plus user-confirmation gate before the outward-facing publish in step 5, satisfying validation for a non-trivial operation.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview with well-signaled, one-level-deep references to references/release-style.md and the two scripts (both real bundle files), with content appropriately split and easy to navigate.	5 / 5
	Total	19 / 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, specific description that clearly states capabilities and provides an explicit, multi-scenario 'Use when' trigger. The only minor gap is synonym/extension coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Draft, refine, and publish bilingual PigeonPod GitHub release notes', compare commits, write a local note, align English and Chinese sections, create/update a GitHub Release — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (draft, refine, publish bilingual release notes from commits) and 'when' via a concrete 'Use when Codex needs to...' clause enumerating several trigger scenarios.	5 / 5
Trigger Term Quality	Good keyword coverage with natural terms like 'release notes', 'GitHub release', 'release branch', and 'English and Chinese', but lacks synonyms (e.g. 'changelog') or file extensions that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — bilingual PigeonPod release notes from the `release` branch with H1-as-title handling — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: aizhimou/pigeon-pod
Path: .agent/skills/release-note-publisher/SKILL.md
Commit: d4e69d1

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