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

100%

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

100%Weight 40%Scale 1-3

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

Well-structured skill body: concise overview, executable commands, a sequenced workflow with validation checkpoints for the destructive publish step, and one-level-deep references that all resolve to real bundle files.

Dimension	Reasoning	Score
Conciseness	Lean body with no concept explanations Claude already knows; commands and bullets are tight, and the H1 rule is repeated only to reinforce a non-obvious constraint rather than as padding.	3 / 3
Actionability	Provides fully executable `python3 ... collect_release_context.py` and `publish_release.py` commands with real flags and a `--dry-run` variant, ready to copy-paste.	3 / 3
Workflow Clarity	Five clearly sequenced steps with a user-review gate (step 4) and a dry-run -> confirm -> publish checkpoint (step 5) for the irreversible publish action.	3 / 3
Progressive Disclosure	Overview plus a Resources section pointing one level deep to the real `references/release-style.md` and two real scripts; all referenced paths verified to exist in the bundle.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 with concrete actions, an explicit 'Use when' trigger clause, and a clearly bounded niche. Third-person voice is maintained throughout, with no vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Draft, refine, and publish bilingual PigeonPod GitHub release notes' plus 'compare commits', 'align English and Chinese', and 'create/update a GitHub Release'.	3 / 3
Completeness	Answers both what (draft/refine/publish bilingual release notes from commits) and when via an explicit 'Use when Codex needs to...' clause enumerating concrete triggers.	3 / 3
Trigger Term Quality	Uses natural terms a user would say — 'release notes', 'GitHub release', 'commits on the release branch', 'English and Chinese' — covering the request space well.	3 / 3
Distinctiveness Conflict Risk	A clear niche — bilingual PigeonPod release notes from the `release` branch — with distinct triggers unlikely to overlap with other skills.	3 / 3
	Total	12 / 12 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: 27a1e11

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