mcp-release-prep

Prepare an MCP server and plugin release by bumping versions across all files and updating changelog

Quality

71%

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/mcp-release-prep/SKILL.md

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.

This is a high-quality, operationally precise release-prep skill: concrete commands, exact edit points, validation gates, and explicit gotchas. Its only real weakness is that everything lives in one long file with no progressive disclosure into supporting references.

Suggestions

Move the opening binary-version precedent (20.0.0–22.0.1) and historical asides into a short 'Precedent / deprecated patterns' note to keep the top of the file lean and protect conciseness against time-sensitive version rot.

Consider extracting the Cowork Plugin component inventory and the Documentation footer sweep into a references/RELEASE-CHECKLIST.md so the main SKILL.md reads as an overview with one-level-deep detail.

Trim a few narrative parentheticals (e.g. 'Harmless in practice: prior artifacts live on their GitHub release...') that, while accurate, do not change the action Claude must take.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes project knowledge rather than explaining basics, but the opening version-precedent list (20.0.0–22.0.1) and a few narrative asides ('Harmless in practice...') could be trimmed; the version numbers are time-sensitive prose not isolated in a deprecated section.	4 / 5
Actionability	Guidance is fully executable: exact file paths and fields to edit, plus copy-paste-ready commands (npm install --package-lock-only, git grep, git log --grep, npm run build/test, gh release upload) covering the common release cases.	5 / 5
Workflow Clarity	A clear checklist (Core/Conditional/Documentation) sequences the work with explicit validation gates — the git grep sweep 'must come back clean before packaging' and 'npm test is the real gate' — and feedback loops plus a destructive-operation warning (clean:bundles deleting artifacts).	5 / 5
Progressive Disclosure	Sections are well-organized and clearly signaled, but the skill is a ~180-line monolithic SKILL.md with no bundle files or one-level-deep references to split detail into, so it does not fully earn the top anchor reserved for clear overview-plus-references structure.	4 / 5
	Total	18 / 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 states a clear purpose and two concrete actions but omits any explicit 'when to use' trigger clause and offers limited keyword variety. It is specific enough to be distinct but not yet comprehensive.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when cutting an MCP server or plugin release, bumping versions, or updating the changelog.'

Include natural synonyms/file markers users might say, such as 'release prep', 'version bump', or 'CHANGELOG'.

Optionally enumerate the key files touched (package.json, manifest.json, CHANGELOG.md) to raise specificity from 1-2 actions to several.

Dimension	Reasoning	Score
Specificity	Names the domain ('MCP server and plugin release') and two concrete actions ('bumping versions across all files', 'updating changelog'), but the coverage is not comprehensive — fewer than 'several specific actions'.	3 / 5
Completeness	It clearly answers 'what' (prepare a release via version bumps and changelog) but provides no 'Use when...' or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant keywords are present ('release', 'version', 'changelog', 'MCP', 'plugin') but it lacks natural synonyms or variations a user might say, and there is no explicit trigger phrasing.	3 / 5
Distinctiveness Conflict Risk	The MCP/plugin release niche is clearly distinct with low conflict risk, though 'version bumping' could overlap marginally with a generic release-management skill.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: dathere/qsv
Path: .claude/skills/mcp-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.