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

—

Does it follow best practices?

Impact

85%

1.32x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable, real-world C# code, but it is a long monolithic wall that largely ignores the provided bundle files. Splitting advanced patterns into the existing references and adding validation checkpoints for risky operations would lift the weaker dimensions.

Suggestions

Reference and link the existing bundle files (e.g., 'For advanced Dapper patterns see references/dapper-patterns.md') and move the deep Dapper/EF Core detail out of the inline body to improve progressive disclosure and conciseness.

Add an explicit validation feedback loop (validate -> fix -> re-validate) for destructive or batch operations such as cache invalidation and database migrations to raise workflow clarity.

Trim explanatory comments and the 'When to Use' list that duplicate the description, keeping only guidance Claude would not already know.

Dimension	Reasoning	Score
Conciseness	The ~810-line body is mostly useful executable patterns, but includes restated context Claude already knows (e.g., '// Scoped: One instance per HTTP request', a 'When to Use' list that duplicates the description) and could be tightened or offloaded to references.	2 / 3
Actionability	Quotes fully executable, copy-paste-ready C# using real APIs (EF Core's 'FirstOrDefaultAsync', Dapper's 'QueryAsync' with 'CommandDefinition', xUnit '[Fact]'/'[Theory]') with concrete examples throughout.	3 / 3
Workflow Clarity	This is a multi-topic patterns skill, yet there is no sequenced multi-step workflow with validation checkpoints; risky operations like cache invalidation and DB changes lack an explicit validate->fix->retry feedback loop, capping the score at 2.	2 / 3
Progressive Disclosure	Real bundle files exist (references/dapper-patterns.md, references/ef-core-best-practices.md, assets/repository-template.cs, assets/service-template.cs) that overlap the inline content, but the body never signals or links them; content that belongs in separate files is inlined, so structure is present but navigation is not.	2 / 3
	Total	9 / 12 Passed

Description

85%

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 that clearly states concrete capabilities and an explicit 'Use when' trigger, giving it high completeness and distinctiveness. Trigger-term coverage is good but omits common single-word variations like '.NET' and 'C#', keeping it from a perfect score.

Suggestions

Add common short trigger terms a user would naturally say (e.g., '.NET', 'C#', 'Entity Framework', 'EF Core') to the 'Use when' clause to broaden trigger coverage.

Consider tightening 'Master C#/.NET backend development patterns for building robust APIs...' which risks reading as marketing; lead with the concrete actions.

Dimension	Reasoning	Score
Specificity	Quotes 'Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit' — multiple concrete, specific capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Master C#/.NET backend development patterns... Covers...') and when ('Use when developing .NET backends, reviewing C# code, or designing API architectures') with an explicit trigger clause.	3 / 3
Trigger Term Quality	Quotes 'Use when developing .NET backends, reviewing C# code, or designing API architectures' — relevant natural terms, but lacks common variations a user would say such as '.NET', 'C#', 'Entity Framework', or 'EF Core'.	2 / 3
Distinctiveness Conflict Risk	Clear .NET-backend niche with distinct triggers ('MCP servers', 'EF Core', 'Dapper', 'xUnit') making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: 5cc2549

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