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.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 well-structured and highly actionable, with executable code, explicit validation feedback loops, and clean one-level-deep references that all resolve to real bundle files. Only minor conciseness trimming is warranted.

DimensionReasoningScore

Conciseness

The body is lean: a numbered workflow, a reference table, terse MUST/MUST NOT bullets, and code examples, with no explaining of concepts Claude already knows; the 'Output Templates' section adds minor redundancy with the reference table.

4 / 5

Actionability

It provides copy-paste-ready, executable C# for a Minimal API endpoint, MediatR query handler, EF Core DbContext with async query, and DTO records, plus concrete commands (dotnet build, dotnet test, curl) and config snippets covering the common cases.

5 / 5

Workflow Clarity

The 5-step Core Workflow sequences analyze→design→implement→secure→test with explicit validate→fix→retry feedback loops in steps 3 and 4 (dotnet build on failure, dotnet test on failure, curl verification).

5 / 5

Progressive Disclosure

A reference table maps each topic to a one-level-deep references/*.md file with explicit 'Load When' guidance, and all five referenced files (minimal-apis, clean-architecture, entity-framework, authentication, cloud-native) exist in the bundle.

5 / 5

Total

19

/

20

Passed

Description

75%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, specific description that clearly states when to use the skill and what it covers, with natural trigger terms for a .NET backend audience. Minor gaps in synonym coverage and explicit concrete actions keep it just below the top anchor.

Suggestions

Fold a couple of high-frequency synonyms from metadata.triggers (e.g., 'C# 12', 'ASP.NET Core') into the description so users who say those terms match naturally.

Lead with one or two concrete actions (e.g., 'Scaffold minimal API endpoints and CQRS handlers') before the domain list to strengthen the 'what' clause.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities (minimal APIs, clean architecture, cloud-native microservices, EF Core, CQRS with MediatR, JWT authentication, AOT compilation), but 'building applications' stays slightly broad versus a fully concrete multi-action list.

4 / 5

Completeness

It explicitly answers both 'what' (Invoke for EF Core, CQRS/MediatR, JWT, AOT) and 'when' (Use when building .NET 8 applications with...), with concrete trigger phrasing, but the 'what' reads as a domain list rather than fully explicit concrete actions.

4 / 5

Trigger Term Quality

It surfaces natural, stack-specific terms a .NET developer would actually say (.NET 8, minimal APIs, CQRS with MediatR, JWT authentication, AOT compilation), though it omits common synonyms such as C# or ASP.NET that appear only in metadata.triggers.

4 / 5

Distinctiveness Conflict Risk

The .NET 8 niche with named stacks is clearly distinct from non-.NET skills, but metadata.related-skills (microservices-architect, cloud-architect) signals minor overlap risk with closely related skills.

4 / 5

Total

16

/

20

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.

Validation16 / 16 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.