csharp-testing

C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices. Use when writing or reviewing xUnit tests, mocks, or integration tests in a C# / .NET project.

Quality

85%

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

The canonical home for this skill is tdg-personal/csharp-testing

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 well-structured, highly actionable testing patterns catalog with executable examples throughout and no extraneous concept explanations. The main opportunity is splitting some detailed integration-test setups into reference files to slim the top-level SKILL.md.

Suggestions

Move the WebApplicationFactory and Testcontainers integration-test setup details into a references/ file (e.g. INTEGRATION_TESTING.md), keeping only a brief pointer and one compact example inline to reduce SKILL.md length.

Trim the opening line 'Comprehensive testing patterns for .NET applications using xUnit, FluentAssertions, and modern testing practices.' since the description and section headers already convey this.

Consider extracting the test-data-builder and anti-patterns material into a reference file if the skill grows further, preserving the body as a concise overview.

Dimension	Reasoning	Score
Conciseness	Largely lean and code-driven with every example earning its place; only minor instances of mild padding like 'Comprehensive testing patterns for .NET applications...' that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready code covering unit tests, parameterized tests, mocking, WebApplicationFactory integration tests, Testcontainers, data builders, and concrete dotnet test commands across the common cases.	5 / 5
Workflow Clarity	Clear 'When to Activate' guidance, well-sequenced topical sections, and concrete run commands; no destructive/batch operations require validation checkpoints, and the patterns-catalog nature means a strict multi-step workflow is not expected.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references; all content is inline with no bundle files, which is appropriate for this patterns catalog though a few detailed setups could optionally be split out.	4 / 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, specific description that clearly states capabilities and trigger conditions with natural keywords. Minor synonym coverage and slight abstraction in 'patterns/best practices' keep specificity and trigger quality just below perfect.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions and tools ('xUnit, FluentAssertions, mocking, integration tests, and test organization'), though 'testing patterns' and 'best practices' are slightly abstract, leaving minor coverage gaps versus the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what it does ('C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests...') and when to use it ('Use when writing or reviewing xUnit tests, mocks, or integration tests'), matching the concrete-trigger anchor 5.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('writing or reviewing xUnit tests, mocks, or integration tests in a C# / .NET project') with good coverage, but misses common synonyms like 'unit tests', 'TDD', or 'test coverage'.	4 / 5
Distinctiveness Conflict Risk	The C#/.NET + xUnit/FluentAssertions niche is clearly distinct with specific triggers, creating minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/csharp-testing/SKILL.md
Commit: 06c5e11

Reviewed: 3 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.