release-prep

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

Quality

78%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplar of a lean, actionable release-prep checklist: concrete file/line targets, executable commands, a clear sequenced workflow with validation, and well-organized sections needing no external references. No changes are needed to raise the score.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a numbered checklist with exact files and line numbers, a changelog template, and concrete commands, with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Guidance is fully executable — specific files with line numbers (e.g. 'Cargo.toml (line 3): version = "X.Y.Z"'), copy-paste cargo/git commands, and a concrete changelog section template.	3 / 3
Workflow Clarity	The process is clearly sequenced (version bump checklist, changelog entry, post-version-bump steps) and includes explicit validation checkpoints ('verify the build', 'verify tests pass') with a note to omit --locked until Cargo.lock regenerates.	3 / 3
Progressive Disclosure	No bundle files are needed; the skill is a single well-organized document with clearly delineated sections (Arguments, Version Bump Checklist, Changelog Entry, Post-Version-Bump Steps, Important Notes) and one-level-deep structure.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 specific to its niche and uses concrete action verbs, but it omits any explicit 'when to use' trigger clause and its trigger-term coverage is only partial. Adding a 'Use when...' clause and broader natural phrasing would raise the completeness and trigger_term_quality dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when preparing a qsv release, bumping the version, or cutting a new release tag.'

Broaden natural trigger terms to include user-common phrasings like 'release prep', 'new version', 'publish a release', and 'cut a release'.

Make 'across all files' concrete by naming the key files (Cargo.toml, CHANGELOG.md) to push specificity toward 3.

Dimension	Reasoning	Score
Specificity	Names the domain (release prep) and two concrete actions ('bumping versions across all files and updating changelog'), but 'across all files' is unspecific about which files, so it does not reach the comprehensive multiple-action anchor of 3.	2 / 3
Completeness	It states what the skill does but has no 'Use when...' or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('release', 'bumping versions', 'changelog') a user might say, but misses common variations like 'release prep', 'new version', or 'publish'; not the broad coverage of anchor 3.	2 / 3
Distinctiveness Conflict Risk	Tied to a clear niche ('qsv release' with version bumps and changelog) that is unlikely to trigger for unrelated skills; uses third-person voice with no conflict-prone generic language.	3 / 3
	Total	9 / 12 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: 17c10db

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