blazor

Guidelines for Blazor development including component lifecycle, state management, and performance optimization

Quality

31%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./blazor/SKILL.md

Quality

Content

29%

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

This skill reads more like a Blazor cheat sheet or reference card than an actionable skill for Claude. It covers many topics at a shallow level with a mix of concrete code examples and vague bullet-point advice, but lacks workflow sequencing, validation steps, and progressive disclosure. The content would benefit significantly from being restructured into a concise overview with references to topic-specific files, and from replacing generic advice with specific, opinionated guidance.

Suggestions

Restructure into a concise SKILL.md overview (component architecture basics + key patterns) with references to separate files like STATE.md, AUTH.md, TESTING.md, PERFORMANCE.md for detailed guidance.

Remove explanations of concepts Claude already knows (Blazor Server vs WebAssembly comparison, what lifecycle methods are) and focus on project-specific conventions and non-obvious patterns.

Add workflow sequences for common multi-step tasks like 'creating a new component', 'adding authentication to a page', or 'optimizing a slow component' with explicit validation/verification steps.

Replace vague bullet points ('Use cascading parameters sparingly', 'Consider Fluxor') with specific guidance on when and how to apply these patterns, including concrete thresholds or decision criteria.

Dimension	Reasoning	Score
Conciseness	The skill covers a lot of ground but includes explanations Claude already knows (e.g., 'Blazor Server: State lives on server', 'Blazor WebAssembly: Runs entirely in browser', lifecycle method descriptions). The comparison table between Server and WebAssembly is general knowledge. Some bullet points are too generic ('Avoid long-running synchronous code'). However, the code examples are reasonably tight.	2 / 3
Actionability	Code examples are concrete and mostly executable (component structure, data binding, bUnit testing, error boundaries), but many sections are bullet-point lists of vague advice rather than specific instructions ('Use cascading parameters sparingly', 'Consider Fluxor for complex state management'). The guidance mixes actionable code with abstract recommendations that lack specifics.	2 / 3
Workflow Clarity	There are no multi-step workflows with sequencing or validation checkpoints. The content is organized as a reference catalog of features rather than guiding Claude through any process. There's no workflow for creating a component, setting up authentication, or debugging — just disconnected snippets and bullet points.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text covering 12+ topics inline with no references to external files or any layered structure. Topics like authentication, testing, state management, and API integration each deserve their own files. There's no navigation structure or signposting for deeper content.	1 / 3
	Total	6 / 12 Passed

Description

32%

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 identifies the technology domain (Blazor) and lists broad topic areas but lacks concrete actions, explicit trigger guidance, and uses no verbs to describe what the skill actually does. It reads more like a category label than a skill description that would help Claude reliably select it from a large pool of skills.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Blazor components, .razor files, Blazor Server/WebAssembly, or Blazor-specific patterns.'

Replace the abstract topic list with concrete actions using third-person verbs, e.g., 'Provides guidelines for structuring Blazor components, managing state with cascading parameters and dependency injection, optimizing render performance, and handling component lifecycle events.'

Include common user-facing trigger terms and file extensions such as '.razor', 'Blazor WASM', 'Blazor Server', 'SignalR', 'RenderFragment', and 'EditForm' to improve matching accuracy.

Dimension	Reasoning	Score
Specificity	Names the domain (Blazor development) and mentions some areas (component lifecycle, state management, performance optimization), but these are broad topic areas rather than concrete actions. No specific verbs describing what the skill does.	2 / 3
Completeness	Partially addresses 'what' (guidelines for Blazor development) but lacks any explicit 'when' clause or trigger guidance. The description reads more like a topic label than actionable selection criteria. Per rubric rules, missing 'Use when...' caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes 'Blazor' which is a strong trigger term, along with relevant terms like 'component lifecycle', 'state management', and 'performance optimization'. However, it misses common variations users might say such as '.razor files', 'Blazor Server', 'Blazor WebAssembly', 'WASM', 'SignalR', or 'render'.	2 / 3
Distinctiveness Conflict Risk	'Blazor' is a fairly specific technology which helps distinguish it, but the broad terms like 'state management' and 'performance optimization' could overlap with skills for other frameworks (React, Angular, etc.). The lack of explicit triggers increases conflict risk.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mindrally/skills
Path: blazor/SKILL.md
Commit: 05a7130

Reviewed: 1 day 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.