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.32x

Quality

76%

Does it follow best practices?

Impact

85%

1.32x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/dotnet-contribution/skills/dotnet-backend-patterns/SKILL.md

Quality

Content

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

Highly actionable with extensive executable code, but the body is an oversized monolith that ignores its own bundle files, inlining reference material (EF Core, Dapper) that already lives in references/. Progressive disclosure is the core weakness.

Suggestions

Replace the inline EF Core and Dapper sections with concise summaries that link to references/ef-core-best-practices.md and references/dapper-patterns.md, keeping only a quick-start example in SKILL.md.

Reference assets/repository-template.cs and assets/service-template.cs from the Project Structure and service sections instead of reproducing full implementations inline.

Trim the explanatory DO/DON'T and Common Pitfalls lists to the non-obvious items, and remove the time-sensitive "(2024/2025)" qualifier from the intro to avoid stale date sensitivity.

Dimension	Reasoning	Score
Conciseness	The 810-line body is mostly code (efficient) but inlines extensive reference material that duplicates the existing bundle files, and the "(2024/2025)" framing adds time-sensitive padding; it could be tightened by offloading detail to the separate files.	3 / 5
Actionability	Concrete, executable C# code blocks throughout (DI registration, async patterns, EF/Dapper repositories, caching, xUnit tests) are copy-paste ready and cover the common backend cases comprehensively.	5 / 5
Workflow Clarity	Content is organized into clear topical sections but there is no sequenced multi-step workflow with validation checkpoints; as a broad patterns reference rather than a single destructive/batch task, this lands at the midpoint.	3 / 5
Progressive Disclosure	Bundle files exist (references/dapper-patterns.md, references/ef-core-best-practices.md, assets/repository-template.cs, assets/service-template.cs) but the body never references or links to them, inlining ~810 lines of content that clearly belongs in those separate files.	2 / 5
	Total	13 / 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 description: third person, explicit what-and-when structure, concrete capability list, and a clear "Use when" trigger clause. Minor keyword synonym/extension gaps prevent a perfect trigger-term score.

Dimension	Reasoning	Score
Specificity	"Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit" lists multiple specific concrete capabilities with comprehensive coverage of the .NET backend domain.	5 / 5
Completeness	It explicitly answers what ("Master C#/.NET backend development patterns... Covers...") and when ("Use when developing .NET backends, reviewing C# code, or designing API architectures") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"Use when developing .NET backends, reviewing C# code, or designing API architectures" plus the tech names (EF Core, Dapper, xUnit, MCP) gives good natural keyword coverage, but a few common synonyms/extensions (ASP.NET Core, Web API, .cs) are missing.	4 / 5
Distinctiveness Conflict Risk	The .NET/C# backend niche with distinct triggers (EF Core, Dapper, MCP servers, xUnit) is clearly distinguishable from other skills with minimal overlap risk.	5 / 5
	Total	19 / 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 (811 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/dotnet-contribution/skills/dotnet-backend-patterns/SKILL.md
Commit: d6837ae

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