deploy-msbuild-to-vs

Deploy locally-built MSBuild binaries into a Visual Studio installation for testing and debugging. Use when you need VS itself to use your local MSBuild changes, or when debugging MSBuild as invoked by VS.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, highly actionable, and has a well-sequenced workflow with validation and restore steps for a risky operation. Its weak point is progressive disclosure: the skill references a Deploy-MSBuild.ps1 bundle script that is not present in the bundle.

Suggestions

Ship the referenced .\scripts\Deploy-MSBuild.ps1 file in a scripts/ bundle directory so the invoked commands actually resolve, or remove the script invocations and inline the deploy steps.

Move the lengthy path-resolution examples and the .NET SDK / cross-machine variants into a separate reference file referenced one level deep from the main workflow, keeping SKILL.md as a tighter overview.

Add a single explicit pre-deploy validation checkpoint (e.g. 'verify the destination Bin path exists and is writable before running the script') to make the existing validation step unmistakable.

Dimension	Reasoning	Score
Conciseness	The body is lean and actionable: commands, parameter tables, and exact paths with minimal conceptual padding. Explanatory prose (e.g. VS filtering MSBuild events) is justified domain detail rather than concepts Claude already knows, matching the lean top anchor rather than the level-2 'could be tightened' case.	3 / 3
Actionability	Provides fully executable PowerShell/cmd commands, concrete example paths, a parameter table, and copy-paste-ready deploy/restore snippets. Guidance is specific and complete rather than abstract or pseudocode, matching the top anchor.	3 / 3
Workflow Clarity	Steps 1-4 are clearly sequenced with validation checkpoints ('Confirm the path exists before deploying', verify build output) and an explicit restore/backup feedback loop for the destructive operation. This matches the top anchor; it is above level 2, which requires missing checkpoints.	3 / 3
Progressive Disclosure	The body repeatedly references a bundled script ('.\scripts\Deploy-MSBuild.ps1') but no scripts/ bundle directory exists, so a referenced path is broken. Content is otherwise a single monolithic file with no progressive splitting, fitting the level-2 anchor (some structure but references not cleanly backed by actual files); it is not a level-1 nested-reference wall.	2 / 3
	Total	11 / 12 Passed

Description

100%

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, uses natural trigger terms, and explicitly answers both what the skill does and when to use it in third person. It is concise and clearly scoped to a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Deploy locally-built MSBuild binaries into a Visual Studio installation for testing and debugging'), covering deployment plus testing and debugging. It lists multiple specific actions rather than vague language, matching the top anchor; it is not a level-2 'names domain and some actions but not comprehensive' case.	3 / 3
Completeness	Explicitly states what it does (deploy built MSBuild binaries into VS for testing/debugging) and when to use it via a clear 'Use when...' clause. Both halves are present and explicit, matching the top anchor; level 2 would omit or only imply the trigger.	3 / 3
Trigger Term Quality	Includes natural terms a user would say: 'MSBuild binaries', 'Visual Studio installation', 'testing and debugging', 'VS itself', 'local MSBuild changes', 'MSBuild as invoked by VS'. Good coverage of common variations, matching the top anchor rather than the partial-coverage level 2.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (deploying locally-built MSBuild into a VS install) with distinct triggers unlikely to fire for unrelated skills. It is well distinguished from generic build/debug skills, matching the top anchor.	3 / 3
	Total	12 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: dotnet/msbuild
Path: .github/skills/deploy-msbuild-to-vs/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.