release

Create a release from dev branch. Generates changelog entries from commits, bumps version, and creates a PR to main. TRIGGERS - Use this skill when user says: - "/release" - create a patch release (default) - "/release minor" - create a minor release - "/release major" - create a major release - "make a release", "cut a release", "ship it", "release to main"

Quality

88%

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

77%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.

A highly actionable, well-sequenced release procedure with exemplary validation and recovery loops. Its weaknesses are verbosity (historical storytelling and over-long inline rationale) and a monolithic structure that, for a skill this large, keeps conditionally-needed material inline instead of offloading it to reference files.

Suggestions

Move the 'Recovery: deterministic release CI failure' section (and the full Homebrew formula template) into a reference file (e.g. references/recovery.md, references/formula.rb) and link to them one level deep, so the main body stays a lean overview of the happy path.

Tighten the Step 1.5 inline comments — the multi-line explanation of the BUNDLED_IS_BINARY/version.ts dev-branch code path can be condensed to the key constraint ('use --help, not version, because the bare compile leaves BUNDLED_IS_BINARY=false') without retelling the module-init mechanics.

Trim historical-incident narratives (v0.3.0 stale SHAs, v0.3.10 reset--hard diff explosion) to a single sentence each citing the lesson; keep the rule, drop the incident report.

Dimension	Reasoning	Score
Conciseness	The guidance is accurate and mostly non-obvious (repo-specific bundler gotchas), but at ~555 lines it carries notable padding — long historical-incident narratives (v0.3.0, v0.3.10), the multi-paragraph 'Why this is first' rationale, and over-long inline comments explaining the BUNDLED_IS_BINARY/version.ts code path — so it is efficient-but-could-be-tightened rather than lean.	2 / 3
Actionability	It provides fully executable bash, concrete version-bump arithmetic, a complete regenerable Homebrew formula template, and specific gh/git commands — copy-paste ready, not pseudocode.	3 / 3
Workflow Clarity	A clearly sequenced 12-step process with explicit validation checkpoints (Step 1 state check, Step 1.5 pre-flight smoke, Step 10 asset-count polling with workflow-failure short-circuit and rerun loop) plus a dedicated recovery section — strong feedback loops for these destructive/batch operations.	3 / 3
Progressive Disclosure	Section structure is good (numbered steps, separated Recovery/Rules), but the skill is a 555-line monolith with no bundle reference files — the large formula template and the conditionally-needed recovery procedure are inline rather than split into one-level-deep reference files, matching the score-2 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 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, third-person description that states concrete capabilities and pairs them with an explicit, natural-language trigger list covering slash commands and colloquial phrases. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions — 'Generates changelog entries from commits, bumps version, and creates a PR to main' — matching the score-3 anchor of several specific actions rather than a vague domain label.	3 / 3
Completeness	It explicitly answers both 'what' (create release / generate changelog / bump version / open PR) and 'when' via an explicit 'Use this skill when user says:' trigger list, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	The TRIGGERS block covers natural phrasings users would say — '/release', 'make a release', 'cut a release', 'ship it', 'release to main' — giving good coverage of both slash-command and colloquial forms.	3 / 3
Distinctiveness Conflict Risk	Release cutting with distinct triggers ('/release', 'cut a release', 'release to main') is a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (570 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: coleam00/Archon
Path: .claude/skills/release/SKILL.md
Commit: ace0a41

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