dotnet-test

Generates C# backend unit and integration tests for EF Core DbContext repositories, domain services, and vertical slice handlers using xUnit / NUnit. Use when the user asks to "write unit tests for C#", "test ef core context", "write integration tests for dotnet", or mentions xUnit backend tests.

Quality

89%

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

86%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 concise, actionable, well-structured skill body that respects Claude's competence and includes a validation checkpoint for its database operations. The main gap is the absence of a complete copy-paste code example and an explicit test-failure recovery loop.

Suggestions

Add a minimal complete C# test example (seed -> act -> assert with separate DbContexts and UseSqlite) as a copy-paste-ready code block so the arrange/act/assert pattern is fully executable at a glance.

Make the test-failure feedback loop explicit: after `dotnet test`, add a step to read failures, fix the test or implementation, and re-run until green.

Consider noting when to prefer Testcontainers over SQLite in-memory (e.g. raw SQL / provider-specific behavior) so the framework choice is decisive rather than left open.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding; it never explains concepts Claude already knows (no "what is EF Core" or "xUnit is a framework") and every line earns its place.	5 / 5
Actionability	Provides concrete, executable guidance (UseSqlite("DataSource=:memory:"), the three separate-DbContext arrange/act/assert pattern, dotnet test) but lacks a full copy-paste-ready code block tying the pieces together.	4 / 5
Workflow Clarity	Clear numbered 5-step sequence with an explicit validation checkpoint (dotnet test) and update-vs-create branching, though the error-recovery loop on test failure is implicit rather than spelled out.	4 / 5
Progressive Disclosure	A short (~40 line) single-purpose skill with no bundle files and clear section headers (Goal, If Tests Already Exist, Workflow); per the simple-skill guidance, well-organized sections earn a 5 with no external references needed.	5 / 5
	Total	18 / 20 Passed

Description

92%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, specific description that clearly states what it does and when to use it, with natural trigger phrases and a well-bounded niche that avoids conflict with adjacent skills. Minor trigger-synonym coverage is the only weakness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across named targets (DbContext repositories, domain services, vertical slice handlers) using specific frameworks (xUnit/NUnit), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (generates C# backend unit/integration tests for EF Core DbContext, domain services, handlers via xUnit/NUnit) and when (a concrete "Use when..." clause with several trigger phrases).	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ("write unit tests for C#", "test ef core context", "write integration tests for dotnet") plus technical terms, but a few natural synonyms/variations (e.g. generic "test C# code", NUnit as a trigger) are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (C# backend EF Core testing with xUnit/NUnit) with distinct triggers and minimal overlap risk, even handing off E2E work to a separate /playwright-test skill.	5 / 5
	Total	19 / 20 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.

Repository: AI-Unified-Process/marketplace
Path: aiup-blazor-dotnet/skills/dotnet-test/SKILL.md
Commit: c3a5da3

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.