CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-release-prep

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

52

Quality

57%

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

65%

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 exact paths, fields, and commands arranged in a clear checklist, supported by a verification section. Its main gaps are minor repetition, missing error-recovery feedback loops, and a monolithic structure with no reference split.

Suggestions

Add explicit feedback loops in Verification Steps, e.g. "If `npm run build` or `npm test` fails, fix the error and re-run before packaging."

De-duplicate the "independent of qsv version" and three-place minimum_qsv_version sync points so each appears once (Core/Conditional) and the Important Notes only cross-reference.

Consider moving the Cowork Plugin detail block into a referenced file (e.g. COWORK.md) with a one-line pointer, to improve progressive disclosure and trim the main skill.

DimensionReasoningScore

Conciseness

The body is lean and checklist-driven with exact fields and commands, but it repeats the "independent of qsv" point and the three-place minimum_qsv_version sync, and spends lines explaining what a .plugin artifact is — it could be tightened.

2 / 3

Actionability

It gives exact file paths, precise field names ("version":, MINIMUM_QSV_VERSION), and copy-paste-ready bash/git snippets plus npm commands — fully executable guidance.

3 / 3

Workflow Clarity

A clear numbered checklist plus a Verification section sequences the work well, but there are no explicit validate→fix→retry feedback loops for this batch operation, which the rubric caps at 2.

2 / 3

Progressive Disclosure

Content is well-organized into labeled sections, but it is a monolithic single SKILL.md with no one-level-deep references and exceeds the 50-line simple-skill threshold, so file-level disclosure is absent.

2 / 3

Total

9

/

12

Passed

Description

50%

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 competent and names a clear domain with two real actions, but it lacks any "Use when..." trigger guidance and stops at moderate specificity. Every dimension lands at the middle anchor as a result.

Suggestions

Add an explicit trigger clause, e.g. "Use when preparing or cutting an MCP server / plugin release, bumping versions, or updating the changelog."

Expand the action list beyond two verbs to mention the changelog generation and multi-file sync explicitly (e.g. "bump versions across package.json, manifests, and agent files; sync minimum qsv version; generate a changelog entry").

Include natural user phrasings such as "release", "version bump", "cut a release", and "changelog" to improve trigger coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names two concrete actions ("bumping versions across all files", "updating changelog") but "across all files" is generic and it stops short of the multi-action comprehensive list required for a 3.

2 / 3

Completeness

It clearly states what the skill does, but provides no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

"release", "bumping versions", and "changelog" are natural terms, but there is no trigger clause and common phrasings a user might say are under-covered.

2 / 3

Distinctiveness Conflict Risk

The MCP server/plugin release niche is fairly specific, but without an explicit trigger it could still overlap with generic version-bump or release-prep skills.

2 / 3

Total

8

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
dathere/qsv
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.