Name: dotnet-backend
Rating: 56.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

dotnet-backend

Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.

Quality

65%

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/SKILL.md

The canonical home for this skill is dotnet-backend in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

65%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 highly actionable thanks to complete, executable C# examples across the core backend scenarios, but it carries padding (persona, expertise/responsibilities catalogs Claude already knows) and is a monolithic inline file with no progressive disclosure or workflow validation checkpoints.

Suggestions

Cut the 'You are an expert...' persona line and collapse 'Your Expertise'/'Your Responsibilities' into the code-pattern sections to remove Claude-known padding.

Move the four code patterns into reference files (e.g. references/minimal-api.md, references/jwt-auth.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add a short validation/verification checkpoint to the background-service batch example (e.g. wrap SaveChangesAsync in try/catch and re-query unsent rows) to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	The four code patterns earn their tokens, but the persona line, the 'Your Expertise' catalog, and the 'Your Responsibilities' section restate framework knowledge Claude already has, so it is mostly efficient with several padded sections that could be trimmed.	3 / 5
Actionability	Four complete, copy-paste-ready C# examples (Minimal API, controller API, JWT token service, BackgroundService) plus a concrete best-practices tool list cover the common backend cases with executable code.	5 / 5
Workflow Clarity	This is a patterns/reference skill with clear topic sections but no sequenced multi-step workflow or validation checkpoints, and the batch background-service example lacks error-handling/verification feedback, so it sits at 'steps present but checkpoints missing' and is capped at 3.	3 / 5
Progressive Disclosure	The body is well-sectioned but a 256-line file inlines four large code blocks with no bundle files or one-level-deep references, so content that could be split into separate reference files is kept inline, matching the 'some structure, content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

66%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 is specific and distinguishable, naming a clear .NET backend niche with several concrete capability areas, but it omits any explicit 'Use when...' trigger guidance, which caps completeness at 3. Adding a trigger clause would raise both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building or refactoring ASP.NET Core APIs, EF Core data access, auth, or background services in C#.'

Add common synonyms/extensions users say ('.NET', 'C#', 'Web API', 'Minimal APIs') to broaden trigger-term coverage.

Tighten 'auth' and 'production API patterns' into more concrete actions (e.g. 'JWT authentication, policy-based authorization') for fuller specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('ASP.NET Core 8+ backend services') plus several concrete capability areas ('EF Core, auth, background jobs, and production API patterns'), matching the 'lists several specific actions' anchor with minor gaps in coverage.	4 / 5
Completeness	The 'what' is clear (build backend services with the listed capabilities) but there is no explicit 'Use when...' clause or trigger guidance, so per the rubric cap completeness stays at 3 rather than 4.	3 / 5
Trigger Term Quality	Includes natural developer terms ('ASP.NET Core', 'EF Core', 'backend services', 'auth', 'background jobs') that users would actually say, but omits common synonyms/extensions like '.NET', 'C#', or 'Web API', so it falls short of the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The 'ASP.NET Core 8+ backend' framing carves a clear niche with minimal conflict risk; minor overlap remains with general backend/auth skills, so it sits at 'mostly distinct' rather than the fully-distinct anchor 5.	4 / 5
	Total	15 / 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/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.