dotnet-backend-patterns

Master C#/.NET patterns for building production-grade APIs, MCP servers, and enterprise backends with modern best practices (2024/2025).

Quality

52%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/dotnet-backend-patterns/SKILL.md

The canonical home for this skill is dotnet-backend-patterns in rmyndharis/antigravity-skills

Quality

Content

43%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 concise and well-sectioned but its instructions are abstract rather than actionable, the steps are not a sequenced workflow with validation, and progressive disclosure is undermined by a broken reference path that ignores the actual bundle files.

Suggestions

Replace abstract directives with concrete, executable guidance — e.g. specific DI registration snippets, EF Core query patterns, or commands — or at minimum point to the bundled templates in `assets/` and patterns in `references/`.

Turn the Instructions list into a numbered workflow with explicit validation checkpoints (e.g. 'verify data-access performance' with a concrete check).

Fix the reference path: change `resources/implementation-playbook.md` to the real `references/dapper-patterns.md` and `references/ef-core-best-practices.md`, and add navigation entries for `assets/repository-template.cs.template` and `assets/service-template.cs.template`.

Dimension	Reasoning	Score
Conciseness	The body is lean with tight sectioned lists and no padding about basic .NET concepts; the only minor waste is the opening line repeating the description verbatim and a 'Do not use' section of borderline value.	4 / 5
Actionability	The Instructions are high-level hints ('Define architecture boundaries', 'Apply DI, async patterns, and resilience strategies') with no concrete code, commands, or specific steps to execute, matching the 'minimal concrete guidance; high-level hints' anchor.	2 / 5
Workflow Clarity	The bullets are parallel activities rather than a sequenced workflow — no numbering, no defined sequence, and no validation/verification checkpoints — fitting the 'rough sequence present but many gaps; validation absent' anchor.	2 / 5
Progressive Disclosure	Sections are clearly organized and a one-level-deep reference is signaled, but the body points to `resources/implementation-playbook.md` which does not exist while the real bundle files in `references/` and `assets/` go unreferenced, so navigation is partly broken.	3 / 5
	Total	11 / 20 Passed

Description

61%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 clearly scopes a .NET backend niche with good natural trigger terms, but it lacks an explicit 'Use when...' clause and relies on generic verbs ('Master', 'building') rather than concrete actions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building or reviewing .NET Web APIs, MCP servers, or enterprise backends in C#.'

Replace generic verbs ('Master', 'building') with concrete actions ('design service architectures', 'implement DI and caching', 'optimize EF Core/Dapper data access').

Add common synonyms like 'ASP.NET' and 'Web API' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('C#/.NET patterns') and several concrete application targets ('production-grade APIs, MCP servers, and enterprise backends'), but the verbs remain generic ('Master', 'building') rather than enumerating concrete actions, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Provides a clear 'what' (master C#/.NET patterns for APIs, MCP servers, enterprise backends) but no explicit 'when'/Use-when clause, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would actually say — 'C#/.NET', 'APIs', 'MCP servers', 'enterprise backends' — giving good keyword coverage, though common synonyms like 'ASP.NET' or 'Web API' are missing.	4 / 5
Distinctiveness Conflict Risk	The .NET-backend niche with C#/.NET and MCP-server triggers is mostly distinct with only minor overlap risk against generic C# skills, though the absence of explicit trigger phrases keeps it just below the clear-niche anchor.	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/dotnet-backend-patterns/SKILL.md
Commit: 57c135b

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.