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

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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 thorough, well-sequenced release-publishing workflow with strong validation gates and executable commands. The main improvement area is tightening the safety-rationale prose in the later steps.

Suggestions

Compress the extended justifications in Step 9 (SHA pinning) and Step 10 (polling) into a one-line rationale plus the command, keeping the safety rule explicit without the surrounding prose.

Inline the one or two most-used sub-procedure commands (e.g., the breaking-changes audit invocation) instead of only referencing the sibling skill, to reduce round-trips.

Verify each cross-skill reference path (../bump-version, ../prepare-release, ../shared-resources) resolves from this skill's location, or mark them as shared-resource dependencies explicitly.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence without explaining basics, but Step 9 and Step 10 carry extended prose justifications (the SHA-pinning and late-commit absorption rationales) that could be trimmed without losing the safety message.	4 / 5
Actionability	Provides concrete, executable commands (`git fetch ... --prune-tags`, `gh release create --draft {tag} --target {merge-commit-sha}`, `gh release edit`, `gh release view`) and a complete release-notes template, though several sub-procedures delegate to sibling skills rather than giving inline commands.	4 / 5
Workflow Clarity	A clearly sequenced Step 0–10 process with explicit validation checkpoints, user-confirmation gates, feedback loops (re-target the draft, re-validate snippets, re-review changed sections), and a dedicated Edge Cases section.	5 / 5
Progressive Disclosure	Well-sectioned overview that points one level deep to the real bundle file references/formatting.md plus clearly signaled cross-skill references; minor gaps come from relying on several sibling-skill reference paths whose existence is not verifiable from this bundle.	4 / 5
	Total	17 / 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.

A strong, third-person description that clearly states capabilities and trigger conditions for a narrowly scoped release-publishing skill. It is comprehensive on what and when, with only minor room to broaden trigger synonyms.

Dimension	Reasoning	Score
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" — with comprehensive coverage of the skill's behavior.	5 / 5
Completeness	Explicitly answers both what (publish/refresh/warn/create draft) and when, with a concrete "Use when..." clause anchored to the prepare-release PR merge state.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ("publish a release, finalize a release, create release notes, or complete a release"), but coverage stops just short of common synonyms a user might use such as "cut a release" or "ship a release".	4 / 5
Distinctiveness Conflict Risk	Scoped narrowly to the C# MCP SDK and the post-merge prepare-release workflow, giving it a clear niche and minimal conflict risk with unrelated release skills.	5 / 5
	Total	19 / 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
relative_links	Relative link issues: 7 suspicious	Warning

	Total	15 / 16 Passed

Repository: modelcontextprotocol/csharp-sdk
Path: .github/skills/publish-release/SKILL.md
Commit: 609499b

Reviewed: 4 days 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.