CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-release

Verify a published release of the C# MCP SDK. Monitors the Release and Publish Docs workflows triggered by publishing a GitHub release, confirms the packages are listed on NuGet.org, and confirms the versioned documentation site reflects the release. Use when asked to verify a release, check whether a release published correctly, monitor the release or docs workflow, confirm packages on NuGet, or check whether the docs site updated.

Quality

88%

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

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 strong, safety-conscious verification workflow with explicit sequencing, validation checkpoints, and mostly executable gh commands throughout. The main weaknesses are redundancy — key warnings (tag/SHA pinning, cancellation semantics, versioning links) are repeated across Steps 2–6 and Edge Cases — and missing concrete verification mechanisms for the NuGet and docs-site checks that are the skill's end goal.

Suggestions

State each warning once and cross-reference it: the tag/SHA pinning rules (Steps 2, 4, 6, Edge Cases), cancellation-not-success rule (Step 4 and Edge Cases), and versioning.html unslugged warning (Step 6 and Edge Cases) are each repeated nearly verbatim — keep the full explanation in Edge Cases and link to it from the steps.

Add concrete verification commands to Steps 5 and 6, e.g. `dotnet package search {package} --exact-match --take 1` (or the NuGet.org package URL) for Step 5 and `curl -sI https://csharp.sdk.modelcontextprotocol.io/v{MAJOR}/versioning.html` for Step 6, so the output-confirmation steps are as executable as the workflow-monitoring steps.

Move the docs-workflow internals in Step 4 (version discovery modes, release-tags vs latest-branches selection, orchestration/main checkout and picker-asset details) into a reference file such as references/docs-workflow.md, keeping Step 4 focused on what to verify and which run to trust.

DimensionReasoningScore

Conciseness

The body is operational rather than educational — it never explains concepts Claude already knows — but it could be tightened: tag/SHA pinning guidance appears in Step 2 (three dense paragraphs), again in Step 4, Step 6, and Edge Cases, and the versioning.html/unslugged warning and cancellation-not-success rules are each stated twice nearly verbatim. The Step 4 bullets ("Cancellation alone is not success...", "Orchestration stays current with `main`...") run 80–100 words each and repeat Edge Cases content. This is 'mostly efficient but could be tightened' rather than anchor 4's 'minor instances', because the duplication spans multiple sections rather than a few trimmable lines.

3 / 5

Actionability

Most steps give exact, copy-paste-ready commands with precise flags and JSON fields (e.g., `gh run list --workflow release.yml --event release --branch v{version} --limit 5 --json databaseId,status,conclusion,headBranch,headSha,createdAt`, `gh workflow run docs.yml --ref main --field docs_source=release-tags`), plus explicit decision rules. It falls short of anchor 5 because Steps 5 and 6 — the actual output verification the skill exists for — provide no concrete command or URL-check method for NuGet.org listing or the docs site, leaving the verification mechanism implicit.

4 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced with explicit validation checkpoints (draft check, headBranch == v{version} on every run, SHA cross-check, re-run/later-attempt handling), feedback loops (re-run failed workflow, re-check after NuGet indexing lag and Pages caching), and an edge-case checklist plus a final report table. The destructive/batch cap does not apply since the skill is read-only by default and remediations require explicit user confirmation. This matches anchor 5: sequence, validation, error recovery, and checklist are all present.

5 / 5

Progressive Disclosure

Good structure: well-labeled sections (Process, Remediation, Edge Cases), a workflow summary table, and a clearly signaled one-level-deep reference ("Use the shared [release branch reference](../shared-resources/release-branches.md)"). It is not anchor 5 because the Step 4 bullets inline ~60 lines of docs-workflow internals (version discovery modes, orchestration/main checkout details, picker asset sourcing) that belong in a reference file — the verification decisions in Step 4 and the workflow's internal mechanics are interleaved. It is above anchor 3 because the references that do exist are clearly signaled and navigation is easy.

4 / 5

Total

16

/

20

Passed

Description

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

An exemplary description: concrete third-person actions, explicit and varied 'Use when' triggers, and a clearly bounded niche. It tells the model both exactly what it does and when to invoke it without padding or buzzwords.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Monitors the Release and Publish Docs workflows", "confirms the packages are listed on NuGet.org", "confirms the versioned documentation site reflects the release" — covering the full verification scope (workflows, packages, docs) with no gaps, matching the comprehensive-coverage anchor. It exceeds anchor 4 because nothing in the skill's scope is missing from the action list.

5 / 5

Completeness

It explicitly answers both questions: 'what' via three concrete action sentences, and 'when' via "Use when asked to verify a release, check whether a release published correctly, monitor the release or docs workflow, confirm packages on NuGet, or check whether the docs site updated". This mirrors the anchor-5 example structure exactly; a missing or weak 'when' clause would cap it at 3, but the trigger list is explicit and concrete.

5 / 5

Trigger Term Quality

Trigger phrases are natural user utterances with synonym coverage: "verify a release", "check whether a release published correctly", "monitor the release or docs workflow", "confirm packages on NuGet", "check whether the docs site updated". Domain terms a user would actually say (NuGet, docs site, workflow) are all present, matching the comprehensive-coverage anchor; no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — verifying releases of the C# MCP SDK specifically — and the triggers (NuGet packages, docs site, Release/Publish Docs workflows) are distinct to this domain, so overlap risk with other skills is minimal. Only a hypothetical release-verification skill for the same SDK could conflict.

5 / 5

Total

20

/

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: 4 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

modelcontextprotocol/csharp-sdk

Path

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