release-prep

Prepare a qsv release by bumping versions across all files and updating changelog

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/release-prep/SKILL.md

Quality

Content

75%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 highly actionable with concrete commands, exact file locations, and a clear sequenced workflow including validation, weakened mainly by the verbose, time-stamp-heavy Cross-repo constraints narrative that could be tightened or externalized.

Suggestions

Tighten or externalize the Cross-repo constraints narrative, moving the 21.1.0/22.0.1 verification detail into a separate reference file or a condensed "current state" summary.

Add an explicit error-recovery loop after the build/test verification steps (e.g. "If the build fails, fix and re-run before proceeding").

Move time-sensitive installer version numbers (v1.1.2, dates) into a clearly marked "current as of" or deprecated-style block so they don't penalize conciseness when they go stale.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean and task-relevant, but the Cross-repo constraints section is a verbose ~50-line narrative with time-sensitive version numbers and dates ("21.1.0", "22.0.1", "2026-08-09") inlined in the main flow rather than in a deprecated/old-patterns section, which the guidelines penalize.	3 / 5
Actionability	Copy-paste-ready commands ("cargo build --locked --bin qsv -F all_features", "qsv --update-mcp-skills"), exact file paths with line numbers ("Cargo.toml (line 3)"), and a complete changelog template fully cover the common cases.	5 / 5
Workflow Clarity	A clear numbered sequence (version checklist → changelog → post-bump steps) with explicit validation (build and test verification) and a checklist is present; it falls short of 5 only because there is no explicit validate→fix→retry feedback loop for the build/test steps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references and one-level structure; the long inlined Cross-repo constraints section could arguably live in a separate reference file, a minor organization gap that keeps it at 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

53%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 clearly states what the skill does for a well-defined niche, but omits any explicit "when to use it" trigger guidance and has only moderate keyword coverage, landing it in the mid-range across most dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when preparing or cutting a qsv release, bumping the version, or writing the release changelog."

Broaden keyword coverage with synonyms users actually say (publish, ship, cut a release, version bump).

Distinguish from the sibling skill in the description itself, e.g. "for the qsv binary release (not the MCP server release)."

Dimension	Reasoning	Score
Specificity	"bumping versions across all files and updating changelog" names the qsv-release domain plus two concrete actions, matching the 1-2-actions anchor; it stops short of the several-specific-actions coverage needed for a 4.	3 / 5
Completeness	The "what" is clear ("Prepare a qsv release by bumping versions across all files and updating changelog") but there is no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like "qsv release", "bumping versions", and "updating changelog" are present, but common synonyms (publish, ship, cut a release, version bump) are missing, fitting the some-keywords-but-missing-variations anchor rather than the 4's good-coverage bar.	3 / 5
Distinctiveness Conflict Risk	The qsv-release niche is clearly specific with low conflict risk, but the body references a closely related `/mcp-release-prep` skill, indicating minor overlap risk with a sibling release skill rather than the minimal-risk 5.	4 / 5
	Total	13 / 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: dathere/qsv
Path: .claude/skills/release-prep/SKILL.md
Commit: a46782a

Reviewed: about 2 hours 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.