CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

running-unit-tests

Guide for running MSBuild unit tests efficiently. Use when running, scoping, filtering, or speeding up unit tests in this repository, or when finalizing a change with a heavier validation pass. Covers xUnit v3 + Microsoft.Testing.Platform (MTP) specifics and which `dotnet test` flags do and don't apply.

Quality

89%

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

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

An exemplary repo-specific skill: nearly all content is non-inferable configuration knowledge, commands are fully executable with real paths, and both the dev loop and final validation workflows carry explicit checkpoints and failure-mode warnings. The only weaknesses are minor: some command repetition between the detailed sections and the Quick reference, a small "--" typo in the speedup bullets, and an unverifiable external skill reference.

Suggestions

Trim the Quick reference table to only scenarios not already shown verbatim above it (e.g., keep only the TRX-report and single-test rows) to cut duplicated tokens.

Fix the "-- **Single TFM**" bullet on line 64 to use a single dash so it renders as a list item like its siblings.

Add a one-line note on where the `run-tests` / `dotnet-test` plugin skill comes from (or inline the top MTP-vs-VSTest flag table), since the reference cannot be resolved inside this bundle.

DimensionReasoningScore

Conciseness

Almost every line is repo-specific knowledge Claude cannot infer (single-threaded runner config, auto trait filters, unconditional coverage args, DOTNET_HOST_PATH), with no filler explaining known concepts. The Quick reference table repeats commands already shown and one bullet opens with a stray "--" (line 64), leaving minor trim opportunities that keep it at level 4 rather than the every-token-earns-its-place level 5.

4 / 5

Actionability

Commands are copy-paste ready with real project paths ("src\Tasks.UnitTests\Microsoft.Build.Tasks.UnitTests.csproj"), TFM-specific exe paths, correct MTP flags (--filter-method, --report-trx), and explicit pitfalls ("Switching TFM without rebuilding silently runs stale binaries"). The dev-loop, per-project, and full-suite cases are all covered with executable examples.

5 / 5

Workflow Clarity

Two clearly sequenced workflows (fast scoped dev loop; final validation pass) with explicit checkpoints and failure-mode guidance: "Always check the `skipped` count" for hidden regressions, "revert before final validation" for parallel overrides, "Restore parallelism settings" as step 1, and a warning not to cancel the ~9-minute full run. This matches the anchor with explicit validation steps, not merely "most checkpoints present".

5 / 5

Progressive Disclosure

The body is well organized into purposeful sections and appropriately defers the exhaustive MTP-vs-VSTest flag reference to an external skill ("see the `run-tests` skill from the `dotnet-test` plugin") while keeping only the essential pitfalls inline. No bundle files exist to verify that pointer, and the 130-line single file slightly exceeds a lean overview, so this is good structure with minor organization gaps rather than the level-5 ideal.

4 / 5

Total

18

/

20

Passed

Description

87%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: it states concrete capabilities, includes an explicit multi-trigger "Use when" clause, and is tightly scoped to MSBuild's xUnit v3/MTP setup so it is unlikely to fire for the wrong skill. Only minor gains available in verb specificity and synonym coverage.

DimensionReasoningScore

Specificity

The description names several concrete actions ("running, scoping, filtering, or speeding up unit tests") and a concrete deliverable ("which `dotnet test` flags do and don't apply"). The leading verb phrase "running MSBuild unit tests efficiently" is slightly generic, so it sits below the level-5 comprehensive anchor.

4 / 5

Completeness

It explicitly answers "what" ("Guide for running MSBuild unit tests efficiently... Covers xUnit v3 + Microsoft.Testing.Platform (MTP) specifics") and "when" via an explicit "Use when..." clause with multiple concrete triggers. Both are present and specific, matching the level-5 anchor rather than the level-4 anchor where the "when" could be more explicit.

5 / 5

Trigger Term Quality

Natural user phrases like "running unit tests", "speeding up", "dotnet test", and "finalizing a change" are present, plus domain terms (xUnit v3, MTP). A few natural variations are missing (e.g., "run tests faster", "test suite"), matching level 4 rather than the comprehensive synonym coverage of level 5.

4 / 5

Distinctiveness Conflict Risk

"MSBuild unit tests... in this repository" plus xUnit v3/MTP runner specifics carves out a clear niche with distinct triggers and minimal conflict risk against generic test-running skills. The repo-scoping removes the residual overlap that would place it at level 4.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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/running-unit-tests/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.