CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mcp-release-prep

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/mcp-release-prep/SKILL.md
SKILL.md
Quality
Evals
Security

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 strong, highly actionable release checklist: exact edit points, executable commands, and validation gates tied to real failure modes the repo has hit before. The only deductions are minor repetition (minimum_qsv_version enforcement stated twice) and a moderately long single-file body that could offload peripheral sections to references.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, repo-specific facts (single edit point for minimum_qsv_version, the clean:bundles deletion gotcha, [skip ci] making npm test the real gate) with almost no explanation of concepts Claude already knows. Not 5 because the minimum_qsv_version 'enforced in 3 places' note is repeated in both the Conditional section and Important Notes, and the Cowork section restates version-source details.

4 / 5

Actionability

Fully executable throughout: exact file paths and JSON field names, copy-paste bash (git grep -n '<old>', the LAST_TAG snippet, npm run mcpb:package, gh release upload), and precise commit message formats. Common cases are concretely covered.

5 / 5

Workflow Clarity

A clear Core -> Conditional -> Documentation -> changelog -> verification -> publishing sequence with explicit validation checkpoints: npm test flagged as the real gate, the grep sweep that 'must come back clean before packaging', the command-count verification, and 'Check the binary release is complete before pushing'. Validation is present, so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well organized with clear section headers, so navigation is easy. Not 5 because at ~175 lines, content such as the Cowork plugin component inventory and command-count verification could live in a separate reference file rather than inline.

4 / 5

Total

18

/

20

Passed

Description

61%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, domain-specific 'what' with two concrete actions, but omits any 'use when' trigger guidance, which caps completeness and limits its discoverability. Keyword coverage is good though missing a few natural synonyms like 'publish'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when releasing the qsv MCP server or updating its version, changelog, or minimum qsv version.'

Mention additional concrete actions from the body (verification, packaging, publishing) to raise specificity and keyword coverage, e.g. '...run build/tests, package the .mcpb and .plugin artifacts, and upload the GitHub release.'

Include natural synonyms users might say such as 'publish', 'version bump', and 'release checklist' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('MCP server and plugin release') and two concrete actions ('bumping versions across all files and updating changelog'), matching the 1-2-concrete-actions anchor. It is not 4 because verification, packaging, and publishing actions that the body actually covers are absent, leaving minor-to-real gaps in coverage.

3 / 5

Completeness

Has a clear 'what' (prepare a release by bumping versions and updating the changelog) but no 'Use when...' clause or equivalent trigger guidance; the rubric explicitly caps this at 3.

3 / 5

Trigger Term Quality

Includes natural phrases users would say: 'release', 'bumping versions', 'changelog', 'MCP server', 'plugin'. Not 5 because common synonyms such as 'publish', 'version bump', or 'version numbers' are missing.

4 / 5

Distinctiveness Conflict Risk

'MCP server and plugin release' is a fairly distinct niche with specific triggers. Not 5 because generic terms like 'release' and 'changelog' could overlap with other release-prep or versioning skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

dathere/qsv

Path

.claude/skills/mcp-release-prep/SKILL.md

Reviewed

Table of Contents

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.