test-release

Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).

Quality

83%

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

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 thorough, highly actionable release-smoke-test workflow with excellent sequencing and validation. It is held back only by length/redundancy and the absence of any progressive disclosure into separate reference files for a skill this large.

Suggestions

Split the detailed per-test Common-failures catalogs and the archon-stable dual-homebrew restore procedure into a references/ file (e.g. TROUBLESHOOTING.md) referenced one level deep from the relevant phases, reducing the SKILL.md footprint.

Remove the Key behaviors section or fold only any non-duplicate items into the phases it restates, since each behavior is already covered inline.

Tighten the archon-stable restore Note and verbose Common-failures prose to the essential regression pointers, trimming tokens without losing the actionable diagnosis.

Dimension	Reasoning	Score
Conciseness	The body is command- and criteria-driven with no concept padding, but at ~470 lines it carries redundancy (the Key behaviors section reiterates the phases) and verbose Common-failures / archon-stable-restore prose that could be tightened.	2 / 3
Actionability	Every phase provides fully executable bash with concrete pass criteria and expected-output examples (e.g. "Expected: Archon CLI v0.3.1, Build: binary"), making it copy-paste ready.	3 / 3
Workflow Clarity	The Phase 1–6 sequence is explicit with validation checkpoints (prerequisite checks, release-exists verification, user confirmation, always-run uninstall) and feedback loops that abort on failure, satisfying the destructive-operation validation requirement.	3 / 3
Progressive Disclosure	No bundle files (references/scripts/assets) exist and the skill is a single monolithic ~470-line document; detailed procedures like the archon-stable restore logic and per-test failure catalogs are inline where a one-level-deep reference would help.	2 / 3
	Total	10 / 12 Passed

Description

90%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, well-structured description that clearly states what it does, when to use it, natural trigger phrases, and what it is not for. The only mild weakness is specificity, which centers on a single action rather than enumerating several.

Dimension	Reasoning	Score
Specificity	"Verify a released archon binary works end-to-end via a specific install path" names the domain and a concrete action, but it is one primary action rather than the multiple distinct actions the level-3 anchor calls for.	2 / 3
Completeness	It explicitly answers both what ("Verify a released archon binary works end-to-end via a specific install path") and when ("Use when: cutting a new release, reproducing a user bug report..."), plus a NOT-for clause.	3 / 3
Trigger Term Quality	The explicit Triggers block lists natural phrases a user would actually say ("test the release", "smoke test the binary", "did the release binary work", "test 0.3.1 via brew"), giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The released-binary / specific-install-path niche is distinct, and the "NOT for" clause explicitly disambiguates it from dev testing and the full validate suite, making conflicts unlikely.	3 / 3
	Total	11 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: coleam00/Archon
Path: .claude/skills/test-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.