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

Passed

No findings from the security scan

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.

The content is highly actionable with a clear, validated workflow and strong safety/restore guidance for a destructive operation. Its main weakness is conciseness — the single ~210-line file carries some explanatory prose and inline advanced sections that could be trimmed or moved to reference files.

Suggestions

Trim restating prose such as 'The path depends on your VS version and edition' and 'this is customizable, so use vswhere below to confirm the path' — the table and vswhere block already convey this.

Consider moving the Debugging, .NET SDK, and Cross-Machine sections into a separate reference file (e.g. references/advanced.md) and linking from a short 'Advanced' section to reduce the main SKILL.md length and improve progressive disclosure.

Tighten the 'What Gets Copied' list and Prerequisites into denser bullet form to cut tokens without losing the operational detail.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational detail, but at ~210 lines it includes restating prose ('The path depends on your VS version and edition', 'this is customizable, so use vswhere below to confirm the path') that could be tightened, matching anchor 3 rather than 4.	3 / 5
Actionability	Provides copy-paste-ready PowerShell, vswhere snippets, exact Deploy-MSBuild.ps1 invocations with a parameter table, env-var recipes with values, restore commands, and a problem/solution troubleshooting map — fully executable and covering common cases.	5 / 5
Workflow Clarity	A clear Step 1–4 sequence (Build→Locate→Deploy→Test) with an explicit verification step, destructive-op safety (auto Backup-*, CAUTION, restore path), and error-recovery troubleshooting plus a Quick Reference checklist.	5 / 5
Progressive Disclosure	Well-organized sections with the heavy deploy logic in the one-level-deep referenced .\scripts\Deploy-MSBuild.ps1 and external docs in 'See Also'; no bundle files exist to split further, so it is well-structured but not the clean multi-file split of anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

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

The description is clear, concrete, and explicitly covers both what the skill does and when to use it, with distinct trigger phrases that minimize conflict risk. Its only soft spot is specificity, where it states the core action without enumerating a broader set of concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('locally-built MSBuild binaries into a Visual Studio installation') and a couple of actions (deploy; testing/debugging), but does not enumerate several distinct concrete actions, so it sits at anchor 3 rather than 4.	3 / 5
Completeness	Explicitly answers both 'what' (deploy built MSBuild binaries into VS for testing/debugging) and 'when' ('Use when you need VS itself to use your local MSBuild changes, or when debugging MSBuild as invoked by VS') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say — 'MSBuild', 'Visual Studio'/'VS', 'debugging', 'testing' — giving good keyword coverage, though it lacks exhaustive synonyms or file extensions that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche — deploying locally-built MSBuild into a VS installation — with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 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: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: dotnet/msbuild
Path: .github/skills/deploy-msbuild-to-vs/SKILL.md
Commit: 22771ef

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