release-plannotator

Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging a release, or publishing. Also trigger when the user says things like "let's ship", "prep a release", "what's changed since last release", or "time to cut a new version".

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

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 thorough, highly actionable multi-phase release skill with strong validation checkpoints, real one-level references, and no padding of general knowledge. The only weak spot is minor verbosity in the Phase 4 security/pipeline prose.

Suggestions

Tighten the Phase 4 step-3 pipeline bullet list and the SBOM-scope/exceptions/immutable-releases prose into a condensed reference block or move finer detail to a linked reference file to reduce the inline token load.

Consider extracting the SBOM/Grype/CycloneDX attestation verification commands into a short reference script the body points to, keeping the SKILL.md overview lean while preserving the executable commands.

Dimension	Reasoning	Score
Conciseness	Largely efficient and assumes Claude's competence — it never explains what git tags or version bumps are — but the Phase 4 pipeline description (SBOM/Grype/SLSA/CycloneDX prose, immutable-releases note, exceptions block) is dense and could be tightened in places without losing project-specific detail.	4 / 5
Actionability	Provides copy-paste-ready commands throughout — `git tag`/`git push`, `gh pr view`, `bun run build:*`, `gh attestation verify`, `sha256sum --check` — covering the common release cases with executable, specific guidance.	5 / 5
Workflow Clarity	Four phases are explicitly sequenced with checkpoints at every risky boundary ('present the draft for review before proceeding', 'Wait for their feedback', 'Verify all builds succeed before proceeding', Pi Parity Gate, 'fix it before proceeding to Phase 4', 'investigate the logs... before retrying') plus a full before/after-tagging checklist and feedback loops for this destructive release operation.	5 / 5
Progressive Disclosure	Clear phase/step overview with well-signaled, one-level-deep references to real bundle files (release-notes-v0.13.0.md, v0.12.0.md, v0.13.1.md), each annotated with its contributor profile so the right pattern is easy to pick.	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.

The description is exemplary: third-person voice, comprehensive concrete actions, explicit 'Use when' triggers with both formal and casual phrasing, and a distinct niche. It satisfies every anchor at the top of each dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline' — giving comprehensive coverage of the release workflow.	5 / 5
Completeness	Explicitly answers both what (draft notes, bump versions, build, kick off pipeline) and when ('Use this skill whenever the user mentions... Also trigger when the user says...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-language coverage including both formal triggers ('preparing a release, bumping versions, writing release notes, tagging a release, or publishing') and casual synonyms users actually say ('let's ship', 'prep a release', 'what's changed since last release', 'time to cut a new version').	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Plannotator release) with distinct, specific triggers that are unlikely to fire for unrelated skills.	5 / 5
	Total	20 / 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: 3 missing	Warning

	Total	15 / 16 Passed

Repository: backnotprop/plannotator
Path: .agents/skills/release/SKILL.md
Commit: 79cb016

Reviewed: 1 day 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.