component-development

Provides a step-by-step workflow for creating Blazor components that emulate ASP.NET Web Forms controls in the BlazorWebFormsComponents library. Covers base class selection (BaseWebFormsComponent, BaseStyledComponent, DataBoundComponent, BaseValidator), Web Forms property and event naming conventions, Playwright integration testing setup, and the complete checklist from component creation through documentation and navigation updates. Use when implementing a new BWFC component, choosing the correct base class for a control type, adding unit or integration tests, or extending an existing component with new Web Forms property support.

Quality

80%

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

Quality

Content

68%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.

A well-structured, actionable skill body with concrete paths and executable test examples, hindered mainly by a lack of validation/verification checkpoints in its multi-step creation workflow.

Suggestions

Add an explicit validation checkpoint to the creation checklist (e.g., 'Run dotnet build and the unit/integration tests before updating navigation') so the workflow has a verify-then-proceed loop.

Expand base class selection beyond the table with a one-line decision rule or example per branch so the choice is unambiguous from the body alone.

Confirm HTML_OUTPUT_MATCHING.md exists as a bundled reference (or mark the link as an external/placeholder guide) so the progressive-disclosure reference resolves.

Dimension	Reasoning	Score
Conciseness	Lean and well-organized with no padding about what Blazor or Web Forms are; a few declarative sentences like 'Every component must have integration tests' could be trimmed, keeping it just above the efficient-but-slightly-padded midpoint.	4 / 5
Actionability	Provides concrete file paths, copy-paste-ready Playwright test stubs, and a specific run command ('dotnet test samples/AfterBlazorServerSide.Tests'), with only minor gaps such as the absence of a decision rule for choosing among base classes beyond the table.	4 / 5
Workflow Clarity	The 9-step creation checklist is clearly sequenced, but there are no validation checkpoints (e.g., build/test before updating navigation); because the workflow produces multi-file changes without an explicit verify step, workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Content is well-structured with a 'Related Guides' section and a one-level-deep, clearly signaled reference to HTML_OUTPUT_MATCHING.md; the inlined test patterns are reasonable, with only minor organization gaps given there are no actual bundle files alongside the skill.	4 / 5
	Total	15 / 20 Passed

Description

92%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 what the skill does and when to use it, with concrete actions and natural trigger phrases. Minor room to soften internal jargon ('BWFC') for broader recognizability.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — base class selection, Web Forms property/event naming conventions, Playwright integration testing setup, and the full creation-to-documentation checklist — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (step-by-step workflow covering base classes, naming, testing, checklist) and 'when' (a 'Use when...' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'Use when implementing a new BWFC component, choosing the correct base class... adding unit or integration tests, or extending an existing component' read as things a user would say, though 'BWFC' is internal jargon and a few synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific library (BlazorWebFormsComponents) and a niche task (emulating Web Forms controls in Blazor), with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: FritzAndFriends/BlazorWebFormsComponents
Path: .github/skills/component-development/SKILL.md
Commit: 3154758

Reviewed: 14 days 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.