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.

Quality

69%

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 ./skills/dotnet-backend-patterns/SKILL.md

Quality

Content

46%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 well-sectioned and concise but offers only abstract directives with no executable guidance, and its progressive disclosure is broken: the lone reference path is wrong and the real bundle files are not mentioned. Fixing the reference path and naming the actual reference/asset files would most improve this skill.

Suggestions

Correct the reference path and surface the real bundle: point to 'references/dapper-patterns.md' and 'references/ef-core-best-practices.md' (and note 'assets/repository-template.cs', 'assets/service-template.cs') instead of the non-existent 'resources/implementation-playbook.md'.

Replace abstract directives with concrete, actionable guidance — e.g., a minimal DI registration snippet, an EF Core query example, or a concrete resilience (Polly) pattern — or explicitly defer each to its named reference file.

Sequence the instructions as an ordered workflow with validation checkpoints (e.g., validate EF migrations after data-access changes) and remove the redundant intro line and the time-sensitive '(2024/2025)' tag.

Dimension	Reasoning	Score
Conciseness	The body is lean and terse with no concept over-explanation, but the intro line near-verbatim repeats the description and the time-sensitive '(2024/2025)' tag is not isolated in a deprecated section, which the rubric penalizes.	4 / 5
Actionability	Instructions are high-level directives ('Define architecture boundaries', 'Apply DI, async patterns, and resilience strategies') with no concrete code, commands, or specific steps — only minimal concrete guidance for an instruction-oriented skill.	2 / 5
Workflow Clarity	A rough logical progression exists (boundaries → patterns → validate performance → tests), but it is an unordered bullet list with no explicit sequencing and no validation checkpoints for risky operations.	3 / 5
Progressive Disclosure	The body points to 'resources/implementation-playbook.md', a path that does not exist in the bundle, while the actual reference files (references/dapper-patterns.md, references/ef-core-best-practices.md) and assets (repository-template.cs, service-template.cs) are never surfaced — navigation is broken and bundled material is undiscoverable.	2 / 5
	Total	11 / 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, specific description that clearly states both capabilities and explicit use-when triggers tied to a well-defined .NET/C# backend niche. Minor improvement possible by adding a few more natural synonym triggers.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities and technologies — 'building robust APIs, MCP servers, and enterprise applications' plus 'async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit' — giving comprehensive, specific coverage rather than vague claims.	5 / 5
Completeness	Explicitly answers both what ('Master C#/.NET backend development patterns... Covers async/await, dependency injection...') and when ('Use when developing .NET backends, reviewing C# code, or designing API architectures') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases like 'developing .NET backends, reviewing C# code, or designing API architectures' plus 'C#/.NET', 'MCP servers', and 'APIs', but misses some common synonyms and file/extension variants a user might say.	4 / 5
Distinctiveness Conflict Risk	The C#/.NET backend niche with triggers like '.NET backends', 'C# code', and 'MCP servers' is clearly distinct from other skills and unlikely to fire for the wrong skill.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/dotnet-backend-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.