Name: testland/xunit-tests
Rating: 75.2 (1 reviews)
Author: testland

testland/xunit-tests

Configures and runs xUnit.net (xUnit v2 + v3) - current de facto .NET test framework with `[Fact]` for single tests + `[Theory]` + `[InlineData]`/`[ClassData]`/`[MemberData]` for parametrized; collection fixtures (`[Collection]`) + class fixtures (`IClassFixture`) for shared setup; output via `ITestOutputHelper`; parallel test config via assembly attribute. Use when working with .NET (C# / F# / VB.NET) on the modern test stack.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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 with a clear step sequence, a genuine verify→fix→re-run checkpoint, and proper offloading of detail to a single reference file. The only weakness is time-sensitive version/license information embedded inline rather than isolated in a deprecated/old-patterns section.

Suggestions

Move version-sensitive facts (e.g. 'v3 released 2024; v2 still widely used', the FluentAssertions 2024 license change and 'v6 is the last fully-free version') into a dedicated 'Versions / deprecations' or 'Old patterns' section so the main steps stay evergreen.

Add a brief validation checkpoint after Step 1 (install) mirroring Step 2's verify step — e.g. confirm `dotnet test` discovers 0 tests due to missing packages before writing the first test.

Consider tightening the Overview paragraph ('xUnit.net is the current .NET test standard …') since Claude already knows xUnit's role; keep only the v2/v3 coexistence fact that affects action.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and code-heavy, but time-sensitive version/license statements ('v3 released 2024; v2 still widely used' and 'FluentAssertions changed license in 2024 … v6 is the last fully-free version') appear inline rather than in a deprecated/old-patterns section, which the rubric penalizes.	2 / 3
Actionability	Every step ships executable, copy-paste-ready code and concrete commands (`dotnet new xunit`, `dotnet add package …`, `dotnet test --filter …`), matching the fully-executable anchor.	3 / 3
Workflow Clarity	Steps 1–7 are clearly sequenced, and Step 2 includes an explicit validation checkpoint with a feedback loop ('Verify … if it exits non-zero or discovers 0 tests, confirm the class is public … then re-run'), plus a Worked example tying the steps together.	3 / 3
Progressive Disclosure	The body is an overview that offloads fixtures and parallelism to a real one-level-deep `references/fixtures-and-parallelism.md`, clearly signaled and referenced multiple times, with content appropriately split.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 high-quality description: third-person voice, dense with concrete xUnit constructs, and pairing a clear capability list with an explicit 'Use when' trigger. It is distinctive and unlikely to conflict with sibling test skills.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete actions and constructs (`[Fact]`, `[Theory]` with `[InlineData]`/`[ClassData]`/`[MemberData]`, `[Collection]`/`IClassFixture` fixtures, `ITestOutputHelper`, assembly parallel config), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly states what it does (configures and runs xUnit v2/v3 with the listed features) and gives an explicit 'Use when working with .NET (C# / F# / VB.NET) on the modern test stack' trigger, satisfying both what and when.	3 / 3
Trigger Term Quality	Uses natural terms a user would say — 'xUnit', 'xUnit.net', '.NET', 'C# / F# / VB.NET', '[Fact]', '[Theory]', 'parametrized' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to xUnit.net on the .NET stack with xUnit-specific attribute triggers, making it unlikely to fire for nunit/mstest or non-.NET skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

3 days ago

Table of Contents

Discovery Implementation Validation