CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prepare-release

Prepare a new release for the C# MCP SDK. Assesses Semantic Versioning level (PATCH/MINOR/MAJOR), bumps the version, runs ApiCompat and ApiDiff, reviews documentation, updates changelogs, drafts release notes, and creates a pull request with all release artifacts. Use when asked to prepare a release, start a release, create a release PR, or assess what the next release should be.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 process skill: every step is executable with exact commands, validation gates and error-recovery loops are built in at each fragile point, and detailed procedures are properly delegated to real one-level-deep reference files. The single soft spot is length — the Edge Cases section duplicates several in-step rules and Step 10b over-justifies — which keeps conciseness at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — no SemVer, git, or NuSet tutorials — and nearly every line is operational, but there is measurable redundancy: the ~30-entry Edge Cases section restates rules already given in-step (ancestry stop, "Unnecessary suppressions found", badge switching), and Step 10b carries multi-sentence justification prose (e.g., the maintainer-acknowledgement rationale) that could be tightened. This fits anchor 4's 'efficient; minor instances of over-explanation that could be trimmed' rather than anchor 3, since nothing explains concepts Claude already knows.

4 / 5

Actionability

Fully executable guidance throughout: exact commands with placeholders ("git fetch {upstream} --prune --prune-tags --tags", "gh api repos/{owner}/{repo}/branches --paginate --jq ...", "git merge-base --is-ancestor v{previous} {target}", "dotnet clean -c Release; dotnet pack -c Release", "gh pr checks {pr-number} --watch", the collaborator permission check), specific file paths (src/Directory.Build.props, CompatibilitySuppressions.xml), and complete copy-paste PR-description and release-notes templates. This matches anchor 5's 'copy-paste ready commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

Thirteen explicitly sequenced steps with validation checkpoints and feedback loops everywhere they matter: sync-before-read with tag resolution (Step 0), ancestry verification with a stop-and-recover path (Step 2), build verification after the version bump (Step 6), ApiCompat error-interpretation rules including regenerate-and-recheck loops (Step 7), dedicated user review gates (Steps 1, 5, 10, 10b, 12), and CI monitoring with failure diagnosis and mandatory re-watch after each push (Step 13). This matches anchor 5's 'explicit validation steps; feedback loops for error recovery'; the destructive/batch cap does not apply because validation is abundant.

5 / 5

Progressive Disclosure

The body is a navigable overview that pushes bulk detail into four real, one-level-deep reference files (categorization.md, apicompat-apidiff.md, readme-content.md, readme-snippets.md), each clearly signaled at its point of use — and the deep-linked anchors referenced in the body (#updating-the-baseline-version, #baseline-transition-suppression-audit) resolve in apicompat-apidiff.md, while ../shared-resources/release-branches.md and ../bump-version/references/semver-assessment.md are explicitly attributed cross-skill references. Content is appropriately split with easy navigation, matching anchor 5.

5 / 5

Total

19

/

20

Passed

Description

92%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 is a strong example: it states concrete third-person capabilities comprehensively and closes with an explicit, natural-language 'Use when' clause covering command and question forms. The only improvement space is broader synonym coverage in the trigger clause (e.g., "cut a release").

DimensionReasoningScore

Specificity

The description enumerates seven concrete actions covering the entire workflow: "Assesses Semantic Versioning level (PATCH/MINOR/MAJOR), bumps the version, runs ApiCompat and ApiDiff, reviews documentation, updates changelogs, drafts release notes, and creates a pull request". This is comprehensive coverage with no gaps, matching the anchor-5 example rather than the 'minor gaps' of anchor 4, and it uses third-person voice throughout.

5 / 5

Completeness

It explicitly answers both questions: a clear, detailed 'what' (the full action list) and an explicit 'when' with concrete trigger phrases ("Use when asked to prepare a release..."). This matches the anchor-5 example structure exactly; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

The trigger clause offers four natural phrasings users would actually say — "prepare a release, start a release, create a release PR, or assess what the next release should be" — including a question form. A few natural synonyms are still missing (e.g., "cut a release", "ship a new version"), which fits anchor 4's 'good keyword coverage; a few natural terms missing' better than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — release preparation for the C# MCP SDK ending in a pull request with release artifacts — and its triggers ("prepare a release", "create a release PR") steer it away from the sibling publish-release skill that actually creates the GitHub release. Minimal conflict risk, matching anchor 5.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 7 suspicious

Warning

Total

15

/

16

Passed

Repository

modelcontextprotocol/csharp-sdk

Path

.github/skills/prepare-release/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.