dotnet-core-expert
Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.
94
92%
Does it follow best practices?
Impact
94%
1.32xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its domain (.NET 8), lists specific technologies and patterns, and provides explicit trigger guidance with 'Use when' and 'Invoke for' clauses. The description is concise yet comprehensive, using third-person voice and natural developer terminology. The only minor weakness is that it doesn't describe the 'what it does' in terms of actions (e.g., 'scaffolds', 'configures', 'generates') — it focuses more on the technology stack context than on concrete outputs.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: minimal APIs, clean architecture, cloud-native microservices, Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation. | 3 / 3 |
Completeness | Explicitly answers both 'what' (building .NET 8 apps with specific patterns and technologies) and 'when' ('Use when building .NET 8 applications...', 'Invoke for Entity Framework Core, CQRS...'). The 'Use when' and 'Invoke for' clauses serve as clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: '.NET 8', 'minimal APIs', 'clean architecture', 'microservices', 'Entity Framework Core', 'CQRS', 'MediatR', 'JWT authentication', 'AOT compilation'. These are terms developers naturally use when seeking help in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: .NET 8 specifically, combined with particular architectural patterns (CQRS, MediatR, clean architecture) and technologies (EF Core, JWT, AOT). Unlikely to conflict with generic coding skills or other language-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured .NET skill with strong actionability through executable code examples and good progressive disclosure via the reference table. The workflow includes proper validation checkpoints with feedback loops. The main weakness is moderate verbosity in the constraints section, where some items are obvious best practices Claude already knows, and a few MUST DO/MUST NOT items are vague rather than actionable.
Suggestions
Trim the MUST DO/MUST NOT lists to only non-obvious, project-specific constraints — remove items like 'Implement proper dependency injection' and 'Skip input validation' that Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary guidance Claude already knows (e.g., 'Implement proper dependency injection', 'Follow clean architecture principles' are vague platitudes). The MUST NOT list contains items that are obvious anti-patterns Claude would avoid. The code examples are well-chosen but the overall content could be tightened. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready C# code examples covering minimal APIs, MediatR handlers, EF Core DbContext, and DTOs. Specific commands like `dotnet build` and `dotnet test` are included. The code is complete and uses modern C# 12/.NET 8 patterns correctly. | 3 / 3 |
Workflow Clarity | The core workflow has clear sequencing with explicit validation checkpoints — build verification with error recovery loops ('if build fails, review errors, fix issues, and rebuild before proceeding') and test verification with similar feedback loops. This covers the validate-fix-retry pattern well for a development workflow. | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table pointing to five separate topic-specific files with clear 'Load When' guidance. The SKILL.md serves as a concise overview with actionable examples while deferring detailed guidance to one-level-deep references. Navigation is intuitive. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- Reviewed
Table of Contents
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.