CtrlK
BlogDocsLog inGet started
Tessl Logo

running-tests

Instructions for running unit tests, integration tests, and individual tests in the WinForms repository. Use this when asked how to run tests, filter them, use Visual Studio workflows, or troubleshoot test failures.

70

Quality

85%

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

82%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 high-quality, highly actionable test-running reference with copy-paste-ready commands, clear sequencing, and useful error-recovery guidance. The main improvement room is token efficiency (the cheat sheet duplicates section 4) and light progressive-disclosure structure.

Suggestions

Trim the Quick-Reference Command Cheat Sheet to non-duplicative entries, or replace it with a one-line pointer to section 4, since it repeats the executable/filter commands already shown in full above.

Consider moving the verbose PowerShell TRX-parsing script and the full filter-options table into a references/ file (e.g. references/parsing-results.md) and linking to it from section 8, reducing inline bulk while keeping the overview lean.

De-duplicate the 'dotnet test --filter does not work' guidance, which appears in the intro callout, section 4b's note, and the troubleshooting list — consolidate to a single authoritative statement.

DimensionReasoningScore

Conciseness

Dense and purposeful with no concept padding, but the Quick-Reference Cheat Sheet substantially duplicates section 4's executable commands and the troubleshooting list repeats the filter guidance, costing tokens.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — build.cmd invocations, dotnet test usage, executable paths with real --filter-method/--filter-class/--filter-trait flags, and a working PowerShell TRX-parsing script covering the common cases.

5 / 5

Workflow Clarity

Clear numbered sections (1–8) with stated prerequisites (e.g. 'After a full build', DOTNET_ROOT setup) and explicit error-recovery feedback loops in troubleshooting; running tests is itself self-validating so no destructive-validation cap applies.

4 / 5

Progressive Disclosure

Well-organized into numbered sections with a cheat sheet and clearly signaled one-level-deep references (docs\testing-in-vs.md, download-sdk skill, xUnit query-filter URL), but it is a monolithic single file with detailed reference material (full options table, TRX parsing script) inlined rather than split out.

4 / 5

Total

17

/

20

Passed

Description

88%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 that clearly states both the skill's purpose and explicit trigger conditions with concrete, natural language. Minor room to add synonyms and file extensions to the trigger terms and to scope the 'when' clause more tightly to WinForms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the test-running domain — 'running unit tests, integration tests, and individual tests', 'filter them, use Visual Studio workflows, or troubleshoot test failures' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('Instructions for running unit tests, integration tests, and individual tests in the WinForms repository') and when ('Use this when asked how to run tests, filter them, use Visual Studio workflows, or troubleshoot test failures') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keywords a user would say ('run tests', 'filter them', 'Visual Studio', 'troubleshoot test failures'), but missing common synonyms/extensions like '.trx', 'xUnit', or 'debug tests'.

4 / 5

Distinctiveness Conflict Risk

The WinForms-scoped 'what' carves a clear niche, but the 'when' triggers ('how to run tests, filter them') are somewhat generic and could overlap with general .NET test-running skills.

4 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/winforms
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.