csharp-developer

Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures database access with Entity Framework Core, implements async patterns and cancellation, structures applications with CQRS via MediatR, and scaffolds Blazor components with state management. Invoke for C#, .NET, ASP.NET Core, Blazor, Entity Framework, EF Core, Minimal API, MAUI, SignalR.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

78%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.

A well-structured body with executable examples, an explicit EF migration validation checkpoint, and clean one-level-deep reference navigation whose targets all exist. Main weaknesses are minor padding (intro line, tool-name list) and an abstract Output Templates section.

Suggestions

Remove the 'Knowledge Reference' line listing tool names Claude already knows (MediatR, xUnit, Moq, etc.) and the 'Senior C# developer with mastery...' intro to recover tokens and lift conciseness to 5.

Replace the abstract 'Output Templates' list with a concrete copy-paste template (e.g. a DTO + endpoint pair) so actionability reaches the fully executable anchor.

Add an explicit verify-gate to the 'Test' workflow step (e.g. 'Run `dotnet test --collect:"XPlat Code Coverage"`; do not proceed below 80%') to pair with the EF checkpoint and reach workflow_clarity 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code, but the 'Senior C# developer with mastery...' intro and the 'Knowledge Reference' buzzword list (MediatR, xUnit, Moq, Benchmark.NET, Polly, Serilog, ...) pad tokens with tool names Claude already knows; trimming these would reach the lean score-5 anchor.	4 / 5
Actionability	Substantial executable code — a complete Minimal API Program.cs, a Result<T> record struct, correct/wrong async examples, and `dotnet ef` commands — but the 'Output Templates' section is an abstract list ('Domain models and DTOs', 'API endpoints') without concrete code, leaving a minor gap below the fully copy-paste-ready score-5 anchor.	4 / 5
Workflow Clarity	A clear five-step Core Workflow with an explicit EF Core checkpoint ('Run dotnet ef migrations add, review migration, roll back with dotnet ef migrations remove') providing a feedback loop for a destructive/database operation; falls short of 5 because only one checkpoint exists and the 'Test' step lacks an explicit verify-gate.	4 / 5
Progressive Disclosure	The body is an overview pointing to a well-signaled Reference Guide table with one-level-deep references and 'Load When' conditions; all five referenced files (aspnet-core, blazor, entity-framework, modern-csharp, performance) exist in the bundle, matching the clear-overview anchor exactly.	5 / 5
	Total	17 / 20 Passed

Description

100%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, third-person description that pairs concrete capabilities with an explicit 'Use when' clause and a comprehensive trigger keyword list. It is specific, complete, and distinct from neighboring skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'Builds REST APIs using minimal or controller-based routing', 'configures database access with Entity Framework Core', 'implements async patterns and cancellation', 'structures applications with CQRS via MediatR', 'scaffolds Blazor components with state management' — giving comprehensive coverage rather than the 1-2 actions of a score-4 anchor.	5 / 5
Completeness	Explicitly answers both: 'what' via the five concrete actions and 'when' via 'Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps' plus the 'Invoke for ...' trigger list, matching the anchor for concrete trigger phrases on both sides.	5 / 5
Trigger Term Quality	Comprehensive natural term coverage with synonyms — 'C#, .NET, ASP.NET Core, Blazor, Entity Framework, EF Core, Minimal API, MAUI, SignalR' — all phrases a user would naturally say; the only gap is absence of file-extension triggers, but C# has no meaningful extension-based trigger.	5 / 5
Distinctiveness Conflict Risk	Clear niche (C#/.NET 8+ backend + Blazor) with distinct triggers and minimal overlap risk; MAUI/SignalR appear in triggers but not the action list, a minor inconsistency that does not create conflict with other skills.	5 / 5
	Total	20 / 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: Jeffallan/claude-skills
Path: skills/csharp-developer/SKILL.md
Commit: 882ef55

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.