assessing-breaking-changes

Guides assessment of backward compatibility for MSBuild changes. Consult when modifying behavior, adding warnings or errors, changing defaults, altering target ordering, removing or deprecating features, deciding whether a change needs a ChangeWave, reviewing blast radius of behavioral changes, or when a PR introduces user-visible output differences.

Quality

100%

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

100%

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

A focused, well-structured assessment skill: concise, concrete, and supported by a clear decision framework and verification checklists. References are appropriately external and clearly signaled rather than nested.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows; the blast-radius table, decision tree, and numbered protocols each earn their tokens. Not the level below because nothing reads as unnecessary explanation.	3 / 3
Actionability	Concrete, copy-paste-ready guidance: executable XML snippets ('<TreatWarningsAsErrors>true</TreatWarningsAsErrors>', '<TargetFrameworks>net472;net8.0</TargetFrameworks>'), specific options ('MessageImportance.Low', 'MessageImportance.Normal'), and a precise decision framework rather than vague direction.	3 / 3
Workflow Clarity	Clear sequencing via the ASCII decision framework plus explicit checklists (Blast Radius Checklist, Compatibility Test Matrix); as an assessment skill it is not a destructive/batch operation, so the missing validate-retry loop does not cap the score.	3 / 3
Progressive Disclosure	Well-organized single-file skill with clearly signaled one-level references ('see the changewaves skill', 'For detailed ChangeWave mechanics, see...'); no bundle files exist to mis-organize, and sections are cleanly partitioned.	3 / 3
	Total	12 / 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.

A strong, well-scoped description that names concrete actions, gives an explicit 'Consult when' trigger, and occupies a distinct niche. It is neither vague nor padded and uses correct third-person voice.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('modifying behavior, adding warnings or errors, changing defaults, altering target ordering, removing or deprecating features, deciding whether a change needs a ChangeWave, reviewing blast radius') in third-person voice, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what ('Guides assessment of backward compatibility for MSBuild changes') and when ('Consult when modifying behavior...'), with an explicit trigger clause satisfying both halves.	3 / 3
Trigger Term Quality	Covers natural terms an MSBuild developer would say ('backward compatibility', 'ChangeWave', 'deprecating features', 'blast radius', 'user-visible output differences'), giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to MSBuild backward-compatibility / ChangeWave assessment, a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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: 3 suspicious	Warning

	Total	14 / 16 Passed

Repository: dotnet/msbuild
Path: .github/skills/assessing-breaking-changes/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.