aspnetcore-project-starter
Scaffold a production-ready ASP.NET Core 9 API with C# 13, Controllers and Minimal APIs, EF Core 9, Identity authentication, middleware pipeline, dependency injection, and xUnit tests.
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./dotnet/aspnetcore-project-starter/SKILL.mdQuality
Discovery
67%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 description excels at specificity and distinctiveness by clearly listing the exact technologies and versions involved in scaffolding an ASP.NET Core API. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill, and could benefit from more natural user-facing keywords beyond technical jargon.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to create a new .NET API, scaffold a C# backend, or start an ASP.NET project'
Include common user-facing variations like 'REST API', 'web API', '.NET backend', or 'C# web service' that developers might naturally use when requesting this type of work
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'ASP.NET Core 9 API with C# 13, Controllers and Minimal APIs, EF Core 9, Identity authentication, middleware pipeline, dependency injection, and xUnit tests.' These are all concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (scaffold a production-ready ASP.NET Core 9 API with specific features), but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Contains good technical keywords like 'ASP.NET Core', 'EF Core', 'Identity authentication', 'xUnit' that developers would use, but missing common variations like '.NET API', 'web API', 'REST API', 'backend', or 'C# API' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (ASP.NET Core 9, C# 13, EF Core 9) and clear niche. Unlikely to conflict with other skills due to the precise version numbers and .NET-specific terminology. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
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 highly actionable ASP.NET Core starter skill with production-ready, executable code examples covering the full stack from scaffolding to testing. The workflow is clear and well-sequenced. However, the document is lengthy and could be more concise by trimming explanatory text Claude already knows and potentially splitting detailed patterns into referenced files.
Suggestions
Remove explanatory phrases like 'Dependency injection everywhere — register in DI, inject via constructor' and 'DTOs for request/response shapes, never expose entities directly' that explain concepts Claude already understands
Consider splitting the Essential Patterns section into a separate PATTERNS.md file, keeping only a quick-start example in the main skill
Trim the Integration Notes section to bullet points with links to external docs rather than inline explanations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., explaining what DTOs are for, noting 'middleware ordering matters' which Claude knows). The extensive code examples are valuable but could be trimmed in places where patterns repeat. | 2 / 3 |
Actionability | Excellent actionability with fully executable code throughout—complete Program.cs, controllers, services, tests, and CLI commands. Every code block is copy-paste ready with proper imports and realistic implementations. | 3 / 3 |
Workflow Clarity | Clear sequenced workflow in 'First Steps After Scaffold' with numbered steps including validation (verify Swagger UI). The scaffold commands are properly ordered, and the 'Common Commands' section provides clear reference for ongoing operations. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting detailed patterns into separate reference files. The Integration Notes section at the end hints at topics that could be expanded elsewhere. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (520 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.