CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-mstest-v1v2-to-v3

Use this skill before answering or editing whenever an MSTest v1/v2 project is being upgraded or repaired for v3. Triggers include QualityTools assembly references; MSTest.TestFramework/TestAdapter 1.x-2.x; "upgrade to MSTest v3"; comparing v1 and v2 migration paths; choosing MSTest or MSTest.Sdk; CS0411/CS1503 after a v3 package bump; DataRow type mismatch, MSTEST0014, or "Test data doesn't match method parameters"; .testsettings/LegacySettings to .runsettings; timeout changes; and net5.0 or other dropped v3 TFMs. Still use it when packages say 3.x but migration source errors or legacy settings remain. Preserve VSTest/MTP. Do not use for a clean v3 project, v3-to-v4, framework conversion, or runner-only migration.

Quality

82%

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

70%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 body delivers an outstanding migration workflow — sequenced steps, baseline/verify feedback loops, precise breaking-change details with version-scoped caveats, and explicit anti-overreach rules. Its weaknesses are redundancy (several rules restated three to four times across sections) and a monolithic single-file layout that inlines reference-style tables and pitfalls instead of splitting them into bundled reference files.

Suggestions

Consolidate the 16-argument DataRow rule into one canonical location (the breaking-changes table or Step 5) and reference it from the other sections instead of restating it four times.

Move the breaking-changes table, .testsettings-to-.runsettings mappings, and Common Pitfalls into one-level-deep files under references/ (e.g. references/breaking-changes.md, references/settings-migration.md) and link them from a leaner SKILL.md overview.

Isolate time-sensitive version numbers (MSTest 3.8.0, Microsoft.NET.Test.Sdk 17.13.0, the 3.0.1/3.0.2 argument cap) into a clearly labeled version-notes section or reference file so the durable workflow stays clean.

DimensionReasoningScore

Conciseness

Mostly efficient with no filler explaining concepts Claude already knows, but the 16-argument DataRow rule is restated in four places (breaking-changes table, Response Guidelines, Step 5, Common Pitfalls), the literal-path-opening guidance is repeated in three sections, and time-sensitive version pins (MSTest 3.8.0, Test.Sdk 17.13.0) sit in the main flow rather than a versioned/deprecated section.

3 / 5

Actionability

Mostly executable guidance: copy-paste XML for the metapackage and MSTest.Sdk swap, before/after C# for the AreEqual fix, literal-level DataRow corrections, and concrete .testsettings-to-.runsettings mappings. Minor gaps: no complete .runsettings example and a few fixes remain directional ("Verify timeout values; adjust if needed", "Re-baseline IDs").

4 / 5

Workflow Clarity

A clear 7-step sequence with an explicit pre-migration baseline ("Record discovered, passed, failed, and skipped counts"), a verification step that compares counts and mandates investigating every difference, a Validation checklist, and a Boundary Gate guarding against over-application — full feedback loops for a batch-editing operation.

5 / 5

Progressive Disclosure

Good in-file structure with clear section headers, but ~260 lines are entirely inline with no bundle files at all; the breaking-changes table, settings mappings, and Common Pitfalls are reference-shaped bulk that would be more navigable split into one-level-deep reference files. Structure is better than anchor 2 (headers and gates are well organized), but there are no references to signal, so anchor 4's 'references mostly clear' does not fit.

3 / 5

Total

15

/

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 description with excellent trigger coverage, explicit use/don't-use boundaries, and low conflict risk. Its only weakness is that the 'what' compresses the skill's actions into a single clause ("upgraded or repaired for v3") while the concrete capabilities (fix breaking changes, replace settings files, update TFMs) must be inferred from the trigger list.

DimensionReasoningScore

Specificity

Lists several concrete trigger conditions ("QualityTools assembly references", "CS0411/CS1503 after a v3 package bump", ".testsettings/LegacySettings to .runsettings", "choosing MSTest or MSTest.Sdk") but frames them as triggers rather than enumerating the skill's concrete actions, leaving minor gaps versus a comprehensive capability list.

4 / 5

Completeness

Explicitly answers both: what ("upgraded or repaired for v3") and when ("Use this skill before answering or editing whenever..." plus negative scope "Do not use for a clean v3 project, v3-to-v4..."). The 'when' is maximally concrete; the 'what' is clear but thinner than the anchor-5 pattern of enumerated concrete actions.

4 / 5

Trigger Term Quality

Comprehensive natural terms users would actually say: "upgrade to MSTest v3", error codes (CS0411, CS1503, MSTEST0014), runtime message ("Test data doesn't match method parameters"), package names (MSTest.TestFramework/TestAdapter 1.x-2.x), and file names (.testsettings, .runsettings), covering synonyms and extensions.

5 / 5

Distinctiveness Conflict Risk

MSTest-specific package names, error codes, and settings file names create a clear niche, and explicit exclusions (v3-to-v4, framework conversion, runner-only migration) route away from sibling skills with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dotnet/skills

Path

plugins/dotnet-test-migration/skills/migrate-mstest-v1v2-to-v3/SKILL.md

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.