blazor-project-starter

Scaffold a production-ready Blazor .NET 9 application with Server, WebAssembly, and Auto render modes, component architecture, SignalR real-time, dependency injection, JS interop, authentication state, and CSS isolation.

Quality

57%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./dotnet/blazor-project-starter/SKILL.md

Quality

Discovery

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description excels at technical specificity, listing concrete Blazor features and capabilities that clearly define its niche. However, it critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill from a large pool. The technical jargon is appropriate for the target audience but could benefit from common term variations.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks to create a Blazor app, scaffold a .NET web application, or mentions C#/ASP.NET web development with real-time features.'

Include common term variations such as 'C#', 'ASP.NET Core', 'WASM', 'dotnet' to improve trigger term coverage.

Add simpler trigger terms like 'real-time web app', 'interactive web application', or '.NET frontend' for users who may not use precise Blazor terminology.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and technologies: 'Scaffold a production-ready Blazor .NET 9 application' with specific features including 'Server, WebAssembly, and Auto render modes, component architecture, SignalR real-time, dependency injection, JS interop, authentication state, and CSS isolation.'	3 / 3
Completeness	Describes WHAT it does (scaffold Blazor app with various features) but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill.	1 / 3
Trigger Term Quality	Contains good technical keywords like 'Blazor', '.NET 9', 'SignalR', 'WebAssembly' that developers would use, but missing common variations like 'WASM', 'dotnet', 'C#', 'ASP.NET', or simpler terms like 'real-time web app'.	2 / 3
Distinctiveness Conflict Risk	Highly specific to Blazor .NET 9 with particular render modes and features; unlikely to conflict with other skills due to the precise technology stack mentioned.	3 / 3
	Total	9 / 12 Passed

Implementation

64%

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 Blazor starter skill with excellent, production-ready code examples covering the full stack from scaffolding to testing. However, it's verbose for a skill file—some explanatory content could be trimmed, and the monolithic structure would benefit from progressive disclosure via linked reference files. The workflow lacks explicit validation checkpoints for the scaffold and migration commands.

Suggestions

Add validation checkpoints after scaffold commands (e.g., 'Verify: `dotnet build` should succeed with 0 errors before proceeding')

Split detailed patterns (JS interop, authentication, bUnit testing) into separate reference files and link from a concise overview section

Remove explanatory text that Claude already knows (e.g., 'SignalR: Server render mode uses SignalR under the hood') and keep only the actionable guidance

Add error recovery guidance for common scaffold failures (e.g., 'If package restore fails, check...')

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some explanatory content that Claude already knows (e.g., explaining what render modes do, what CSS isolation is). The Integration Notes section contains some redundant explanations, though the code examples themselves are lean.	2 / 3
Actionability	Excellent actionability with fully executable scaffold commands, complete code examples for every pattern (Program.cs, components, services, tests), and copy-paste ready implementations. All code is complete and runnable, not pseudocode.	3 / 3
Workflow Clarity	The scaffold command sequence is clear, but lacks explicit validation checkpoints. No verification steps after running dotnet new, no guidance on what to check if commands fail, and no feedback loops for the EF migrations workflow which involves database operations.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document with no references to external files for advanced topics. The 400+ lines could benefit from splitting detailed patterns (JS interop, authentication, testing) into separate reference files.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

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 (572 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: about 1 month ago

Table of Contents

Discovery Implementation Validation

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.