CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a solid, actionable skill with executable code examples and a well-structured workflow including validation checkpoints and feedback loops. Its main weaknesses are moderate verbosity in the constraints/output sections and the inability to verify that referenced files actually exist. The progressive disclosure structure is well-designed in concept but the SKILL.md itself carries substantial inline content that could be offloaded to references.

Suggestions

Trim the MUST NOT list to items that are genuinely non-obvious (e.g., remove 'skip input validation') and tighten the MUST DO list by removing items Claude already knows as best practices.

Replace the vague 'Output Templates' section with a concrete example of expected project structure output, or remove it entirely to save tokens.

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary padding — the 'Output Templates' section is vague filler, the MUST NOT list partially restates things Claude already knows (e.g., 'skip input validation'), and the constraints section could be tighter. The code examples earn their place but the surrounding prose could be leaner.

2 / 3

Actionability

Provides fully executable, copy-paste-ready C# code examples covering minimal APIs, MediatR handlers, EF Core DbContext, and DTOs. Concrete commands like `dotnet build` and `dotnet test` are specified. The constraints include specific syntax examples (e.g., nullable enable directive, record type syntax).

3 / 3

Workflow Clarity

The core workflow has a clear sequence with explicit validation checkpoints — build verification with error recovery loop, test execution with failure diagnosis loop, and endpoint verification. The feedback loops ('if build fails, review errors, fix issues, and rebuild before proceeding') are well-articulated.

3 / 3

Progressive Disclosure

The reference table with 'Load When' guidance is a well-structured progressive disclosure pattern pointing to five reference files. However, no bundle files were provided, so we cannot verify these references exist. The inline code examples are substantial (~60 lines) and could arguably be moved to reference files, keeping SKILL.md as a leaner overview.

2 / 3

Total

10

/

12

Passed

Description

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 via 'Use when' and 'Invoke for' clauses. The description is concise, uses third-person voice appropriately, and contains highly relevant trigger terms that developers would naturally use. A minor improvement could be adding a brief 'what it does' statement (e.g., 'Guides development of...') rather than jumping straight into 'Use when', but the current form is effective.

DimensionReasoningScore

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

Clearly answers both 'what' (building .NET 8 apps with specific patterns and technologies) and 'when' (explicit 'Use when' and 'Invoke for' clauses with concrete trigger scenarios).

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

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
Jeffallan/claude-skills
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.