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

81%

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

77%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 highly actionable, well-structured skill with executable commands and good sequencing for a destructive workflow. Weaker on progressive disclosure because the repeatedly-referenced Deploy-MSBuild.ps1 script is not present in the bundle, and the destructive deploy step could use an explicit pre-overwrite validation checkpoint.

Suggestions

Add an explicit validation checkpoint before the destructive overwrite in Step 3 (e.g., confirm the destination path exists and a Backup-* folder was created before proceeding).

Include the referenced scripts/Deploy-MSBuild.ps1 in the bundle, or remove the script-reference framing and inline the deploy logic so references resolve.

Tighten the 'What Gets Copied' list and consolidate the two restore command blocks into one to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is largely lean, action-oriented prose with executable commands and tables; minor sections (e.g., the 'What Gets Copied' enumeration and repeated restore examples) could be tightened, but it generally assumes Claude's competence without padding concepts.	4 / 5
Actionability	Provides copy-paste-ready PowerShell/cmd commands for build, deploy, restore, and debugging, plus a parameter table and troubleshooting table covering the common cases with concrete fixes.	5 / 5
Workflow Clarity	Sequenced Step 1–4 with explicit checkpoints (close/reopen VS, verify via build output/binlog) and a restore path, but the destructive deploy step lacks an explicit validate-before-overwrite checkpoint and relies on the script's implicit backup rather than a documented verify step.	4 / 5
Progressive Disclosure	Structure is well-organized with clear sections and a See Also of external links, but the referenced bundle script (scripts/Deploy-MSBuild.ps1) does not exist in the bundle, and there are no in-skill reference files — the deploy detail lives entirely inline rather than being split into a referenced reference.	3 / 5
	Total	16 / 20 Passed

Description

86%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, well-targeted description that clearly states both the capability and explicit use-when triggers, with low conflict risk thanks to a redirect to the adjacent bootstrap skill. Minor headroom remains in trigger synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (deploy MSBuild into VS) and several concrete actions (deploy locally-built binaries, test, debug MSBuild as invoked by VS), but coverage stops short of fully enumerating the multiple sub-capabilities found in the body.	4 / 5
Completeness	Explicitly states both what it does ('Deploy locally-built MSBuild binaries into a Visual Studio installation for testing and debugging') and when to use it ('Use when you need VS itself to use your local MSBuild changes, or when debugging MSBuild as invoked by VS').	5 / 5
Trigger Term Quality	Includes natural user-facing phrases like 'need VS itself to use your local MSBuild changes' and 'debugging MSBuild as invoked by VS'; covers the main phrasings but omits synonyms like 'patch VS' which only appears in the argument-hint.	4 / 5
Distinctiveness Conflict Risk	The niche is narrow and clearly distinct (patching VS's bundled MSBuild with local builds); explicit redirect to the bootstrap skill for CLI-only testing minimizes overlap with adjacent skills.	5 / 5
	Total	18 / 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
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: b75ae9e

Reviewed: 1 day 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.