CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/dotnet-unit-tests

Use for any question or task about .NET tests in C#, F# or VB.NET, including quick how-to questions and choosing between xUnit, NUnit and MSTest: Fact and Theory tables, fixtures and shared state between tests, parallel runs, mocking, async tests, output, and coverage with dotnet test. Has authoring conventions and anti-patterns for xUnit.net.

Quality

86%

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

Overview
Quality
Evals
Security
Files

Quality

Content

78%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, actionable skill body: sequenced steps, executable commands, an explicit run-verification loop, and appropriately deferred framework alternatives in real one-level-deep reference files. The main improvement areas are completing placeholder code bodies, trimming the version/date commentary, and adding validation to the later steps.

Suggestions

Complete the ellipsis code bodies ('{ ... }' in the MemberData and collection-fixture examples) so every snippet is copy-paste ready.

Move the time-sensitive version commentary ('v3 released 2024; v2 still widely used') into a dedicated versions/legacy note so it does not penalize the otherwise lean overview.

Add a quick verify step to the CI section (e.g., confirming the trx file and coverage output exist before uploading to codecov) to extend the Step 2 validation pattern.

DimensionReasoningScore

Conciseness

The body is efficient and code-heavy with high-value pattern notes ('DB-backed classes share one fixture via [Collection]... while pure-logic tests parallelize freely'), but the Overview framing ('xUnit.net is the current .NET test standard...') and the unpinned time-sensitive note 'v3 released 2024; v2 still widely used in production' are minor over-explanations that could be trimmed, matching anchor 4.

4 / 5

Actionability

Mostly executable guidance: copy-paste install commands ('dotnet new xunit -n MyProjectTests'), runnable test snippets, and troubleshooting ('if it discovers 0 tests, confirm the class is public, the method carries [Fact]...'). Minor gaps keep it below anchor 5: several snippets use '{ ... }' ellipsis bodies and undefined placeholders like 'OpenConnection()'.

4 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced with an explicit validation checkpoint and error-recovery loop in Step 2 ('Verify the run reports Passed! with the expected test count') plus a 7-item authoring checklist, but Steps 3-7 are additive feature documentation without checkpoints, matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references ('references/nunit.md', 'references/mstest.md', 'references/fluentassertions.md') linked contextually at the framework-decision points and reiterated in a References section; default-framework (xUnit) content is appropriately inline while alternatives are split out — a clean match for anchor 5.

5 / 5

Total

17

/

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 with an explicit 'Use for' trigger clause, comprehensive framework-synonym coverage, and a well-scoped niche. Its only weakness is that capabilities are stated as topic nouns rather than concrete actions, and a few natural trigger phrases (e.g., 'unit tests') are absent.

Suggestions

Include the literal phrase 'unit tests' (e.g., 'any question or task about .NET unit tests') since it is the most natural thing a user would say.

Rephrase a few topic nouns as concrete actions (e.g., 'write Fact/Theory parametrized tests', 'configure fixtures and parallel runs') to sharpen capability specificity.

DimensionReasoningScore

Specificity

Names the domain ('.NET tests in C#, F# or VB.NET') and enumerates many specific topics ('Fact and Theory tables, fixtures and shared state between tests, parallel runs, mocking, async tests, output, and coverage with dotnet test'), but these are topic nouns rather than concrete action verbs, so it falls just short of the comprehensive-actions anchor 5.

4 / 5

Completeness

Explicitly answers both: 'what' via the detailed topic inventory and authoring conventions, and 'when' via the concrete trigger clause 'Use for any question or task about .NET tests in C#, F# or VB.NET, including quick how-to questions' — a clear match for anchor 5.

5 / 5

Trigger Term Quality

Good natural keyword coverage including all three framework names ('xUnit, NUnit and MSTest'), the command 'dotnet test', 'mocking', 'fixtures', and 'parallel runs', but the literal phrase 'unit tests' and any file/extension triggers are missing, matching anchor 4 ('a few natural terms missing') rather than 5.

4 / 5

Distinctiveness Conflict Risk

Framework-anchored triggers ('xUnit, NUnit and MSTest', 'Fact and Theory', 'dotnet test') establish a clear niche with minimal conflict risk against generic testing or code-review skills, matching anchor 5.

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.

Reviewed

On this page