CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

publish-release

Publish a GitHub release for the C# MCP SDK after a prepare-release PR has been merged. Refreshes release notes to include any PRs merged since preparation, warns about version or breaking change impacts from late-arriving PRs, and creates a draft GitHub release. Use when asked to publish a release, finalize a release, create release notes, or complete a release after the prepare-release PR has been merged.

Quality

86%

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

73%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.

A well-engineered process skill: the workflow is unambiguously sequenced with confirmation gates, validation, and recovery loops, and the gh/git commands are concrete and copy-paste ready. The main costs are repetition (versioning-link rules, never-publish warnings, disclosure rules each stated multiple times) and rationale prose in Step 9 that could be condensed, plus one genuinely hard step (listing PRs in a commit range) left without a command.

Suggestions

State the versioning-link rule (v{MAJOR} slug, belongs under Breaking Changes) once — in the Release Notes Template section — and cross-reference it from Step 7 and the two Edge Cases entries instead of restating it in each place.

Condense the Step 9 GitHub draft/tag mechanics paragraphs to the operative rules ('always pass the full SHA, never a branch name'; 'repoint with gh release edit --target, then regenerate notes') and trim the surrounding rationale, which duplicates the top-level safety note and the checklist.

Add the concrete command or procedure for enumerating PRs merged in a commit range (the core of Step 3), e.g. the gh api invocation or a pointer to the reference that defines it, since 'get the full set of PRs merged between the previous release tag and the merge commit' is currently a direction with no mechanics.

DimensionReasoningScore

Conciseness

Mostly efficient operational prose, but there is a pattern of tightening opportunities: the versioning-link rule is stated three times (Step 7, two Edge Cases entries, and the template intro), 'never publish' appears in the safety note, Step 9, and the checklist, and the AI-disclosure rules in Step 9 are stated twice in adjacent text. Multi-paragraph explanations of GitHub draft/tag mechanics in Step 9 ('Pinning the SHA costs nothing…', 'That is also what makes a late-arriving commit easy to absorb…') go beyond the operative instruction. This fits the 3 anchor ('some unnecessary explanation or could be tightened') better than 4, where over-explanation would be only minor and isolated.

3 / 5

Actionability

Concrete copy-paste commands with clearly marked placeholders ('git fetch {upstream} --prune --prune-tags --tags', 'gh release create --draft {tag} --target {merge-commit-sha}', 'gh release view v{version} --json isDraft,publishedAt,tagName,isPrerelease'), specific file paths (src/Directory.Build.props, src/PACKAGE.md), a worked version-tag example, and a complete release notes template. It falls short of 5 because the hardest operation — 'Get the full set of PRs merged between the previous release tag and the merge commit' — is given as a direction with no command or mechanic, and a few steps ('assess and flag impacts', 'harvesting Co-authored-by trailers') defer mechanics without pointing to where they are defined.

4 / 5

Workflow Clarity

Eleven explicitly sequenced steps (0–10) with per-step user-confirmation gates ('The user must explicitly choose an option before proceeding'), explicit validation checkpoints (fetch verification in Step 0, version confirmation in Step 2, snippet build validation in Step 5, metadata review in Step 9), feedback loops for error recovery (fix → re-validate → re-target draft → regenerate notes; poll-until-published in Step 10), and a publishing checklist. This matches the 5 anchor exactly; no meaningful validation gaps remain for a 4.

5 / 5

Progressive Disclosure

Good structure: the bundle's references/formatting.md is real, referenced twice, one level deep, and well signaled ('Follow [references/formatting.md] when composing…'), and cross-skill references (../shared-resources/release-branches.md, ../prepare-release/references/categorization.md, ../bump-version/references/semver-assessment.md) each state what they provide and link with section anchors. It stops short of 5 because the body is a ~280-line procedure manual rather than a lean overview — the 35-line release notes template and the extensive Edge Cases list are inlined where comparable skills would split them into a reference file.

4 / 5

Total

16

/

20

Passed

Description

96%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.

A strong description: concrete third-person actions, an explicit 'Use when' clause with multiple natural trigger phrasings, and a clear post-merge precondition that disambiguates it from preparation-time skills. The only risk is that 'create release notes' could also fire for the sibling prepare-release skill, but the gating condition largely resolves it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Refreshes release notes to include any PRs merged since preparation', 'warns about version or breaking change impacts from late-arriving PRs', 'creates a draft GitHub release' — covering the skill's capabilities comprehensively in third person. This matches the 5 anchor ('multiple specific concrete actions; comprehensive coverage'); the 4 anchor would require minor gaps in coverage, which are not present.

5 / 5

Completeness

Explicitly answers both questions: what ('Refreshes release notes… warns about… impacts… creates a draft GitHub release') and when ('Use when asked to publish a release, finalize a release, create release notes, or complete a release…'). This is a direct match to the 5 anchor — both what and when with concrete trigger phrases — not merely the 4 anchor where the 'when' could be more specific.

5 / 5

Trigger Term Quality

The 'Use when' clause supplies four natural user phrasings — 'publish a release', 'finalize a release', 'create release notes', 'complete a release' — including deliberate synonyms of the same intent, plus the gating condition ('after the prepare-release PR has been merged'). Coverage is comprehensive for this domain; a 4 would require clearly missing natural terms, and no common variant of the request is absent.

5 / 5

Distinctiveness Conflict Risk

The repo-specific scope ('C# MCP SDK', 'after a prepare-release PR has been merged') carves out a clear niche, but the trigger 'create release notes' also describes the sibling prepare-release skill, creating minor overlap risk with a closely related skill. That matches the 4 anchor ('mostly distinct; minor overlap risk with closely related skills') rather than the 5 anchor's minimal conflict risk.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

modelcontextprotocol/csharp-sdk

Path

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