cut-release

Cut a new release of the Detail CLI by bumping the version in Cargo.toml and merging to main. Use when asked to "cut a release", "bump the version", "publish a new version", or similar.

Quality

83%

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

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

The body is a well-sequenced, actionable release runbook with concrete templates and validation gates. Adding brief error-recovery guidance for failed cargo check or CI would round out the workflow.

Suggestions

Add a short feedback loop for failures (e.g., if 'cargo check' fails, fix and re-run before proceeding) to push workflow_clarity toward 5.

De-duplicate the release.yml outcome list between 'How It Works' and 'Step 4' to tighten conciseness.

Include the explicit git branch/PR commands rather than relying on templates with X.Y.Z placeholders to make guidance fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly lean and project-specific (release.yml behavior, version-bump rules) with minor redundancy between the 'How It Works' list and Step 4's merge outcomes.	4 / 5
Actionability	Provides concrete templates (PR title 'chore: release vX.Y.Z', branch 'release/vX.Y.Z'), an executable 'cargo check', and a verify URL, but uses X.Y.Z placeholders and omits explicit git/PR creation commands.	4 / 5
Workflow Clarity	Clear four-step sequence with explicit validation checkpoints (cargo check compiles, wait for CI to pass, verify release after merge), though it lacks error-recovery feedback loops for failed checks.	4 / 5
Progressive Disclosure	A self-contained single-purpose skill with no need for external references, organized into clear headed sections; per the simple-skill note, well-organized sections suffice.	5 / 5
	Total	17 / 20 Passed

Description

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

The description is strong: it pairs a concrete what statement with explicit, natural trigger phrases and a well-scoped niche. Minor gap is breadth of action coverage and missing synonyms.

Dimension	Reasoning	Score
Specificity	Names two concrete, specific actions — 'bumping the version in Cargo.toml and merging to main' — with a concrete file target, which exceeds the generic 1–2 action anchor though coverage is narrow.	4 / 5
Completeness	Explicitly answers both what ('Cut a new release... by bumping the version in Cargo.toml and merging to main') and when ('Use when asked to...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users actually say ('cut a release', 'bump the version', 'publish a new version') but lacks synonyms/file extensions for comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Scoped to the Detail CLI release workflow with distinct trigger phrases and a specific file (Cargo.toml), giving it a clear niche with minimal conflict risk.	5 / 5
	Total	18 / 20 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: usedetail/cli
Path: .claude/skills/cut-release/SKILL.md
Commit: 5e8ba56

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.