CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-structured, concise assessment skill that avoids explaining concepts Claude already knows and gives concrete, actionable compatibility rules. Its main gap is the absence of an explicit validation feedback loop and the lack of an in-bundle reference structure.

Suggestions

Add an explicit validate→fix→retry loop to the compatibility-test workflow (e.g., 'run the test matrix, if WarnAsError build fails, gate the warning behind a ChangeWave and re-test') to lift workflow_clarity to 5.

Add a short 'Verify before merge' checkpoint that ties the Blast Radius Checklist to a concrete reviewer sign-off, making the validation step explicit rather than implied.

Consider moving the detailed Blast Radius Checklist and Compatibility Test Matrix into a bundled reference file (references/) and summarizing them in SKILL.md to better model overview→detail progressive disclosure.

DimensionReasoningScore

Conciseness

Lean and efficient; it does not explain what MSBuild or backward compatibility is, and every section (philosophy, checklist, decision tree) earns its place. Assumes Claude's competence throughout.

5 / 5

Actionability

Provides concrete, specific guidance — real XML snippets (<TreatWarningsAsErrors>, <TargetFrameworks>), named importance levels, and the MSBxxxx warning format. Falls just short of fully copy-paste-executable code, which is inherent to an assessment/decision skill rather than a coding skill.

4 / 5

Workflow Clarity

The Decision Framework tree, Blast Radius Checklist, and numbered Deprecation Protocol give a clear sequence with verification cues ('test opt-out path', the Compatibility Test Matrix). It lacks an explicit validate→fix→retry loop, which keeps it below 5.

4 / 5

Progressive Disclosure

Well-organized into clearly signaled sections, with one-level-deep pointers to the sibling changewaves skill and external ChangeWaves docs. No bundle files exist to split, so it is not a true overview→detail file split, keeping it below 5.

4 / 5

Total

17

/

20

Passed

Description

100%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, third-person description that clearly states the skill's purpose and provides an exhaustive list of concrete consultation triggers. It answers what and when with natural terminology and is highly distinctive.

DimensionReasoningScore

Specificity

Names the domain ('backward compatibility for MSBuild changes') and lists multiple concrete assessment actions — modifying behavior, adding warnings/errors, changing defaults, altering target ordering, removing/deprecating features — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' ('Guides assessment of backward compatibility for MSBuild changes') and 'when' ('Consult when...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user-sayable phrases ('adding warnings or errors', 'changing defaults', 'removing or deprecating features', 'blast radius of behavioral changes', 'user-visible output differences') with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Clear MSBuild-specific niche with distinct compatibility-assessment triggers and minimal overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.