dotnet-core-expert

Name: dotnet-core-expert
Rating: 70 (1 reviews)
Author: jeffallan

tessl install github:jeffallan/claude-skills --skill dotnet-core-expert

github.com/jeffallan/claude-skills

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.

Review Score

70%

Validation Score

12/16

Implementation Score

42%

Activation Score

100%

SKILL.md

Review

Evals

Generated

12 days ago

Warnings & errors only

Criteria	Score
metadata_version	'metadata' field is not a dictionary
license_field	'license' field is missing
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata
body_examples	No examples detected (no code fences and no 'Example' wording)

Overall Assessment

This skill has good organizational structure with clear progressive disclosure to reference files, but critically lacks actionable content. It reads more like a persona description than executable guidance - no code examples, no specific commands, and vague workflow steps. The constraints (MUST DO/MUST NOT DO) are useful but insufficient without concrete implementation examples.

Suggestions

Add executable code examples for at least one common task (e.g., minimal API endpoint with dependency injection, or EF Core DbContext setup)
Replace vague workflow steps with specific actions and validation checkpoints (e.g., 'Run dotnet build to verify compilation before proceeding')
Remove the role-playing framing ('Senior .NET engineer with 10+ years') - Claude doesn't need persona backstory to follow instructions
Include at least one complete, copy-paste ready example showing the preferred patterns (minimal API with record DTOs, proper DI, async pattern)

Dimension	Score	Reasoning
Conciseness	2/3	The skill contains some unnecessary framing ('Senior .NET engineer with 10+ years of experience') and verbose role definition that Claude doesn't need. The constraints and knowledge reference sections are reasonably efficient, but the overall structure could be tighter.
Actionability	1/3	The skill provides no executable code examples, only abstract guidance like 'Write high-performance code with modern C# features.' The reference table points to files but the skill itself contains no concrete, copy-paste ready implementations or specific commands.
Workflow Clarity	2/3	The 5-step core workflow is listed but lacks validation checkpoints and specific actions. Steps like 'Implement - Write high-performance code' are too vague. No feedback loops or error recovery guidance for complex operations like migrations or authentication setup.
Progressive Disclosure	3/3	Good structure with clear reference table pointing to specific topic files with 'Load When' guidance. One-level-deep references are well-signaled and organized by topic. The overview appropriately defers detailed content to reference files.

Overall Assessment

This is a strong skill description that clearly identifies its niche in .NET 8 development with specific architectural patterns and technologies. It uses third person voice appropriately and includes explicit 'Use when' and 'Invoke for' clauses that provide clear trigger guidance. The description is concise yet comprehensive, covering both the scope and activation conditions effectively.

Dimension	Score	Reasoning
Specificity	3/3	Lists multiple specific concrete actions and technologies: minimal APIs, clean architecture, cloud-native microservices, Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.
Completeness	3/3	Explicitly answers both what (building .NET 8 apps with specific patterns and technologies) and when ('Use when building...', 'Invoke for...') with clear trigger guidance.
Trigger Term Quality	3/3	Excellent coverage of natural terms developers would use: '.NET 8', 'minimal APIs', 'clean architecture', 'microservices', 'Entity Framework Core', 'CQRS', 'MediatR', 'JWT authentication', 'AOT compilation' - all are terms users would naturally mention.
Distinctiveness Conflict Risk	3/3	Highly distinctive with specific technology stack (.NET 8) and architectural patterns (CQRS, MediatR, clean architecture) that clearly differentiate it from generic coding or other language-specific skills.