release

Orchestrate an MSBuild release: create the tracking issue, branch, configure DARC channels and subscriptions, bump version in main, final-brand the release branch, insert into VS, and publish post-GA. Covers the full monthly release lifecycle aligned with VS shipping cadence.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/release/SKILL.md

Quality

Content

77%

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 a well-sequenced, validated workflow, but it is verbose for a skill and keeps a lot of operational detail inline instead of moving it into bundle reference files. Tightening prose and offloading detail to referenced files would improve both conciseness and progressive disclosure.

Suggestions

Move the PACKAGE_VALIDATION_BASELINE rationale and the DARC rotation deep-dive into a referenced reference file, keeping SKILL.md to the procedure and a one-line pointer.

Trim explanatory prose (e.g., the 'why it fails' columns) to the essential caveat; assume Claude can infer the rest.

Add a short 'Quick reference' summary up top so the dense phase tables can live further down.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and high-signal, but sections like the 'Two tempting wrong answers' table and extended prose on DARC rotation add explanation beyond what a lean skill needs, keeping it below the lean anchor.	2 / 3
Actionability	Concrete, copy-paste-ready commands appear throughout ('pwsh ./scripts/Get-PackageValidationBaseline.ps1', '--configuration-branch <name> --no-pr', '.\eng\common\darc-init.ps1'), matching the fully-executable anchor.	3 / 3
Workflow Clarity	A clear 6-phase sequence with explicit per-phase triggers, a Validation checklist, and an Error Recovery feedback loop (e.g., 'DARC configuration PR conflicts: Rebase… and force-push') meets the checkpoints anchor.	3 / 3
Progressive Disclosure	External repo files are linked one level deep and well-signaled in tables, but no bundle files exist and substantial operational detail is kept inline in SKILL.md rather than split out, so it sits between monolithic and cleanly-split.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and highly distinctive but is missing an explicit 'Use when…' trigger and leans on internal jargon rather than natural user phrasing. Adding a user-voice trigger clause would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when…' clause naming how a user would request this (e.g., 'Use when running the monthly MSBuild release, cutting a vs* branch, or preparing a VS insertion').

Soften jargon in the trigger terms — pair 'DARC channels'/'final-brand' with plainer phrasing a requestor might actually say.

Keep the concrete action list; it is the strongest part of the description.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete actions — 'create the tracking issue, branch, configure DARC channels and subscriptions, bump version in main, final-brand the release branch, insert into VS, and publish post-GA' — matching the multi-action anchor.	3 / 3
Completeness	It clearly states what the skill does but provides no 'Use when…' trigger clause, which the guidelines cap at 2 for completeness.	2 / 3
Trigger Term Quality	Domain terms (MSBuild, release, DARC, VS) are present but heavy on internal jargon and missing the natural user-voice variations a requestor would say, so it lands above the no-keywords anchor but below full coverage.	2 / 3
Distinctiveness Conflict Risk	The MSBuild/VS monthly-release niche with DARC/insertion specifics is highly specific and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 14 suspicious	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: dotnet/msbuild
Path: .github/skills/release/SKILL.md
Commit: c88db8e

Reviewed: 5 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.