release-devbox

Cut a Devbox CLI release — recommend the version bump, write the release notes, and drive the draft or publish flow. Use when asked to release devbox, cut a version, ship 0.x.y, publish a release, or when a release is stuck partway through and needs diagnosing or resuming.

Quality

94%

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

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

An operationally dense, highly actionable release runbook with strong sequencing and validation checkpoints. Its main weakness is monolithic structure — some sizable template/reference blocks are inlined where one-level-deep reference files could reduce load.

Suggestions

Move the house-style release-notes template (the ```markdown block in section 3) into a references/release-notes-template.md and link to it, keeping only the rules inline.

Consider extracting the troubleshooting table and 'Known breakage' section into a references/troubleshooting.md to shorten the main body.

Tighten the 'Why the order is what it is' anecdotes to one-line rationales, keeping the rule but dropping the per-incident narrative.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence — no explaining of git/goreleaser basics — but the 'Why the order is what it is' section carries some historical narrative (0.17.3/0.17.5 anecdotes) that could be trimmed without losing operational value.	4 / 5
Actionability	Fully executable guidance throughout: concrete `devbox run` commands, a copy-paste `gh api` notes-generation call, and a complete `node scripts/release.ts` invocation with all flags plus a troubleshooting table of specific `gh run list` commands.	5 / 5
Workflow Clarity	A clear four-step sequence with an explicit sign-off checkpoint ('get explicit sign-off before running anything'), resumability feedback loops ('fix the cause and re-run the same command'), and a detailed stuck-release recovery table.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and a concise overview up top, but it is a ~200-line monolith with no bundle references; the house-style notes template and troubleshooting table are sizable blocks that could optionally live in separate reference files.	4 / 5
	Total	18 / 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.

A strong, specific description that clearly states both the capability and the trigger conditions with natural user phrasing. Third-person imperative voice is used correctly throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'recommend the version bump', 'write the release notes', 'drive the draft or publish flow', plus diagnosing/resuming stuck releases — giving comprehensive coverage of the release task.	5 / 5
Completeness	Explicitly answers both what ('Cut a Devbox CLI release — recommend the version bump, write the release notes, and drive the draft or publish flow') and when (a concrete 'Use when...' clause with multiple trigger phrases).	5 / 5
Trigger Term Quality	The 'Use when' clause covers natural synonyms a user would say — 'release devbox', 'cut a version', 'ship 0.x.y', 'publish a release', and 'release is stuck' — with good variation.	5 / 5
Distinctiveness Conflict Risk	Targets a narrow niche (Devbox CLI releases) with distinctive triggers like 'ship 0.x.y' and 'release devbox', making conflict with unrelated skills minimal.	5 / 5
	Total	20 / 20 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
relative_links	Relative link issues: 4 suspicious	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: jetify-com/devbox
Path: .agents/skills/release-devbox/SKILL.md
Commit: 277290e

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