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

92%

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

85%

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

A well-structured, highly actionable release-runbook with strong workflow sequencing, validation checkpoints, and appropriately externalized reference materials. The main weakness is minor editorial prose that pads token usage without adding instructional value.

Suggestions

Trim motivational framing ('This is the most important phase', 'the public face of each version', 'This project's community is its lifeblood') to keep the body purely instructional.

Consider moving the detailed release-notes structure (the 8-item outline and writing guidelines) into a reference file, keeping SKILL.md as a leaner overview that links to it.

Replace 'the heart of the notes' style commentary with a one-line functional description of what the section must contain.

Dimension	Reasoning	Score
Conciseness	The bulk is concrete commands and tables, but editorial/motivational lines ('This is the most important phase', 'the public face of each version', 'This project's community is its lifeblood', 'the heart of the notes') add tokens without instructing Claude on what to do, so it could be tightened; not a 1 because no basic concepts are over-explained and the actionable detail earns its place.	2 / 3
Actionability	Executable throughout — concrete git/gh commands, the 7-file version-bump table, `bun run build:*` steps, and `gh release edit` — copy-paste ready with specific examples.	3 / 3
Workflow Clarity	Clear four-phase sequence with explicit validation checkpoints ('Wait for their feedback before proceeding to Phase 2', 'Verify all builds succeed before proceeding', the Pi Parity Gate, 'fix it before proceeding to Phase 4') and before/after-tag checklists, with the immutable-release warning providing an error-recovery guardrail.	3 / 3
Progressive Disclosure	A clear four-phase overview opens the body, and the bulky release-note templates are externalized to references/ with one-level-deep, explicitly signaled links to real files (release-notes-v0.12.0/0.13.0/0.13.1.md), all verified present.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 names concrete actions, provides explicit 'use when' triggers in both formal and colloquial phrasing, and occupies a clear niche unlikely to conflict with other skills. Voice is third-person imperative throughout, incurring no penalty.

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' — matching the highest anchor.	3 / 3
Completeness	Explicitly states both what the skill does (the four actions) and when to use it ('Use this skill whenever... Also trigger when...'), matching the top anchor.	3 / 3
Trigger Term Quality	Covers natural terms users would say ('preparing a release, bumping versions, writing release notes, tagging a release, or publishing') plus colloquial triggers like 'let's ship', 'prep a release', 'what's changed since last release', and 'time to cut a new version'.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to a Plannotator release with distinctive triggers, making conflict with other skills unlikely; not the level below because the niche and triggers are unambiguous.	3 / 3
	Total	12 / 12 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: 193b07e

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