dotnet-backend-patterns

Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.

1.19x

Quality

80%

Does it follow best practices?

Impact

85%

1.19x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/dotnet-contribution/skills/dotnet-backend-patterns/SKILL.md

The canonical home for this skill is dotnet-backend-patterns in wshobson/agents

Quality

Content

68%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.

The body is highly actionable with executable, copy-paste-ready C# patterns and well-signaled bundle references. Its weaknesses are verbosity (heavy inlined code and explanation of known concepts) and the absence of a sequenced workflow, since it is a reference catalog rather than a procedural skill.

Suggestions

Move full test classes and the complete caching implementations into a references file (e.g., references/testing-patterns.md, references/caching-patterns.md) and keep only compact representative snippets inline, reducing body length and token cost.

Trim explanations of well-known concepts (e.g., what async/await or the Options pattern is) and lead each section with the executable pattern directly, assuming Claude's competence.

Add a short 'How to apply these patterns' workflow at the top (e.g., identify layer → pick data access → add caching → write tests) so the catalog has a light sequenced entry point.

Dimension	Reasoning	Score
Conciseness	The ~800-line body inlines large blocks (full xUnit/integration test classes, complete caching implementations) that duplicate material in the bundle files, and explains patterns Claude largely already knows; mostly competent but could be tightened and offloaded to references.	3 / 5
Actionability	Dense copy-paste-ready C# throughout — DI registration, async/await do/don'ts, EF Core configuration, Dapper repositories, multi-level caching, and full unit/integration tests — fully executable and covering common cases.	5 / 5
Workflow Clarity	This is a categorical patterns catalog rather than a multi-step process, so there is no sequenced workflow with validation checkpoints; guidance is organized via DO/DON'T and Common Pitfalls but lacks an explicit ordered flow.	3 / 5
Progressive Disclosure	All four referenced bundle files (assets/service-template.cs, assets/repository-template.cs, references/ef-core-best-practices.md, references/dapper-patterns.md) exist and are clearly signaled one level deep in a Resources section, though sizable inlined content could be split out for tighter organization.	4 / 5
	Total	15 / 20 Passed

Description

91%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.

The description is strong: it covers a clear domain niche, lists concrete capabilities, and provides explicit 'Use when...' trigger guidance. Trigger term coverage is comprehensive and natural.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit") with minor coverage gaps, fitting the 'lists several specific actions; minor gaps' anchor.	4 / 5
Completeness	Explicitly states what it does ("Master C#/.NET backend development patterns...") and when to use it ("Use when developing .NET backends, reviewing C# code, or designing API architectures"), hitting both what and when with concrete triggers.	5 / 5
Trigger Term Quality	Comprehensive natural terms a developer would actually say ("developing .NET backends", "reviewing C# code", "API architectures", "MCP servers", plus framework names EF Core/Dapper/xUnit), matching the 'comprehensive coverage including synonyms' anchor.	5 / 5
Distinctiveness Conflict Risk	The "C#/.NET backend" niche is clearly distinct with minimal conflict risk, though "reviewing C# code" could mildly overlap with general code-review skills, placing it just below the top anchor.	4 / 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
skill_md_line_count	SKILL.md is long (818 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/dotnet-contribution/skills/dotnet-backend-patterns/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours 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.