release

Bump the Plano version across all required files. Use when preparing a release.

Quality

87%

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

100%

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

A tight, fully actionable version-bump procedure with concrete commands, an explicit confirm-before-proceeding checkpoint, an exclusion guard, and a verification summary. It is appropriately concise for a single-purpose skill and needs no external references.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative throughout, with no concept-explanation padding; every line (including the file list) carries essential operational information.	3 / 3
Actionability	It provides concrete, executable guidance — specific file paths, a worked version-transform example ('0.4.11 → 0.4.12'), and a copy-paste-ready command ('cd cli && uv lock').	3 / 3
Workflow Clarity	The batch operation is clearly sequenced with explicit checkpoints: confirm with the user before proceeding, an exclusion guard for lock files, and a final old→new summary that serves as verification.	3 / 3
Progressive Disclosure	This short (~23 line), single-purpose skill has no need for external references and is well-organized into intro, file list, guards, lock step, and summary, which fits the simple-skill exception.	3 / 3
	Total	12 / 12 Passed

Description

75%

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 concise, well-triggered description that clearly states both its purpose and when to invoke it, with a distinct project-scoped niche. Its main weakness is specificity — it names only one action and has limited trigger-term variation.

Suggestions

List the concrete actions involved (e.g., update version strings across files and refresh the uv lock file) to lift specificity toward a 3.

Broaden trigger terms to cover natural variations users might say, such as 'version bump', 'new release', or 'cut a release'.

Dimension	Reasoning	Score
Specificity	It names a concrete action ('Bump the Plano version') and the domain, but lists only one action rather than multiple specific concrete actions, so it falls short of a 3.	2 / 3
Completeness	It answers both what ('Bump the Plano version across all required files') and when, with an explicit 'Use when preparing a release' trigger clause.	3 / 3
Trigger Term Quality	'Use when preparing a release' is a natural trigger, but coverage is thin and omits common variations like 'version bump', 'new version', or 'cut a release'.	2 / 3
Distinctiveness Conflict Risk	Scoping to 'the Plano version' plus a distinct release trigger gives it a clear niche unlikely to overlap with unrelated skills.	3 / 3
	Total	10 / 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: katanemo/plano
Path: .claude/skills/release/SKILL.md
Commit: d23e276

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.