dotnet-backend

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

Quality

53%

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

Quality

Content

39%Scale 1-5

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

This skill provides decent executable code examples for common ASP.NET Core patterns but suffers from significant verbosity—listing technologies and concepts Claude already knows, persona framing, and redundant best-practices checklists. It lacks workflow sequencing and validation checkpoints for what are inherently multi-step processes (setting up auth, running migrations, configuring services). The monolithic structure with no progressive disclosure makes it token-inefficient.

Suggestions

Remove the 'Your Expertise' technology listing and 'Your Responsibilities' sections entirely—Claude already knows these concepts. Focus only on project-specific conventions or non-obvious patterns.

Add a clear multi-step workflow for bootstrapping a new API project: create project → configure DbContext → run initial migration → verify DB connection → add endpoints → test with curl/HTTP file → add auth → verify auth works.

Split the large code examples into separate bundle files (e.g., examples/minimal-api.cs, examples/jwt-auth.cs) and reference them from a concise SKILL.md overview.

Add validation checkpoints: verify migration succeeded, test endpoint returns expected response, confirm JWT token is valid before proceeding to authorization setup.

Dimension	Reasoning	Score
Conciseness	The skill is significantly verbose. The 'Your Expertise' section is a laundry list of technologies Claude already knows. The 'Your Responsibilities' section restates concepts any .NET developer would know (async/await, connection pooling, AsNoTracking). The 'Best Practices You Follow' checklist is largely common knowledge for Claude. The persona framing ('8+ years of experience') wastes tokens.	2 / 5
Actionability	The code examples are concrete, executable, and cover multiple common patterns (Minimal API, Controller-based API, JWT auth, BackgroundService). However, some examples have minor gaps—the UserResponse record constructor doesn't match the User object properties, and the Minimal API example references BCrypt without showing the package dependency. The examples are mostly copy-paste ready.	4 / 5
Workflow Clarity	There is no clear multi-step workflow for building a service end-to-end. The skill presents isolated code snippets without sequencing them into a coherent process. There are no validation checkpoints—no mention of running migrations, testing endpoints, verifying JWT configuration works, or validating database connectivity. For a skill involving database operations and auth setup, the lack of any verification steps is a significant gap.	2 / 5
Progressive Disclosure	The content is a monolithic wall of code examples and lists with no references to external files. The extensive code patterns (4 large code blocks) and the long best-practices checklist could be split into separate reference files. There are no bundle files, and the skill doesn't organize content into overview vs. detailed reference material.	2 / 5
	Total	10 / 20 Passed

Description

66%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 reasonably specific about the technology stack and capabilities, using natural terms that developers would search for. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The term 'production API patterns' could also be more concrete.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about building .NET APIs, Entity Framework database access, ASP.NET authentication/authorization, or hosted background services.'

Expand 'production API patterns' into specific examples like 'middleware, error handling, rate limiting, dependency injection' to improve specificity and trigger term coverage.

Include common synonyms and variations like 'Entity Framework', '.NET 8', 'REST API', 'Web API', 'authentication', 'authorization' to improve trigger term matching.

Dimension	Reasoning	Score
Specificity	Lists several specific capabilities: ASP.NET Core 8+ backend services, EF Core, auth, background jobs, and production API patterns. These are concrete technologies and patterns, though 'production API patterns' is somewhat vague and could be more specific (e.g., rate limiting, middleware, error handling).	4 / 5
Completeness	Has a clear 'what' (build ASP.NET Core 8+ backend services with specific technologies), but there is no explicit 'when' clause. The absence of a 'Use when...' clause caps this at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes strong natural keywords like 'ASP.NET Core', 'EF Core', 'auth', 'background jobs', and 'API'. A user asking about these technologies would likely use these terms. Missing some synonyms like 'Entity Framework', 'authentication', 'authorization', 'Web API', 'REST API', '.NET 8'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct due to the specific technology stack (ASP.NET Core 8+, EF Core). It clearly targets .NET backend development, which is a well-defined niche. Minor overlap risk with general backend/API skills or broader .NET skills, but the version specificity and technology combination help differentiate it.	4 / 5
	Total	15 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: 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.