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.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill dotnet-backend-patterns82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
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.
This is a strong skill description that effectively communicates specific capabilities (APIs, MCP servers, enterprise apps) with concrete technologies (Entity Framework, Dapper, xUnit). It includes an explicit 'Use when...' clause with clear trigger scenarios and uses appropriate third-person voice throughout. The description is well-differentiated from other potential skills through its C#/.NET focus.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'building robust APIs, MCP servers, and enterprise applications' plus specific patterns like 'async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit'. | 3 / 3 |
Completeness | Clearly answers both what ('building robust APIs, MCP servers, enterprise applications' with specific patterns) AND when ('Use when developing .NET backends, reviewing C# code, or designing API architectures') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'C#', '.NET', 'backend', 'APIs', 'MCP servers', 'async/await', 'dependency injection', 'Entity Framework', 'Dapper', 'xUnit', 'API architectures'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on C#/.NET backend specifically, with distinct triggers like 'Entity Framework Core', 'Dapper', 'xUnit' that wouldn't conflict with other language-specific skills or frontend skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive .NET backend development reference with excellent, executable code examples covering DI, async patterns, data access, caching, and testing. However, it's overly long for a SKILL.md file, lacks clear workflow sequences with validation steps, and includes some explanatory content that Claude already knows. The content would benefit from being split into a concise overview with references to detailed pattern files.
Suggestions
Split detailed sections (Data Access Patterns, Caching Patterns, Testing Patterns) into separate reference files and keep SKILL.md as a concise overview with links
Add explicit workflow sequences with validation checkpoints, e.g., 'After registering services: 1. Build project 2. Run `dotnet run` 3. Verify no DI exceptions at startup'
Remove explanatory comments like '// Scoped: One instance per HTTP request' that explain concepts Claude already knows
Add a decision tree or quick reference for choosing between EF Core vs Dapper, IOptions vs IOptionsSnapshot, etc.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory content Claude already knows (e.g., explaining what Clean Architecture is, basic DI lifetime descriptions). The DO/DON'T lists and Common Pitfalls sections add value but could be more condensed. | 2 / 3 |
Actionability | Excellent executable code examples throughout - complete C# implementations for DI registration, async patterns, EF Core repositories, Dapper queries, caching, and testing. All code is copy-paste ready with proper using statements and realistic patterns. | 3 / 3 |
Workflow Clarity | While individual patterns are well-documented, there's no clear workflow for when to apply which pattern or validation checkpoints. For example, no guidance on verifying DI registration works, or steps to validate cache invalidation is functioning correctly. | 2 / 3 |
Progressive Disclosure | References to external files (assets/service-template.cs, references/ef-core-best-practices.md) are mentioned at the end, but the main content is a monolithic document with 500+ lines. The 'When to Use This Skill' section is helpful, but detailed sections like Testing Patterns could be split into separate files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 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 | 10 / 11 Passed | |
Table of Contents
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.