bwfc-migration

Migrate ASP.NET Web Forms .aspx/.ascx/.master markup to Blazor Server using BlazorWebFormsComponents (BWFC). Covers control translation, expression conversion, data binding, code-behind lifecycle, and Master Page to Layout conversion. WHEN: "migrate aspx", "convert web forms markup", "master page to layout", "asp prefix removal", "data binding expressions". FOR SINGLE OPERATIONS: use /bwfc-identity-migration for auth, /bwfc-data-migration for EF/architecture.

Quality

85%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Discovery

100%

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 is an excellent skill description that clearly defines a specific migration domain (ASP.NET Web Forms markup to Blazor), lists concrete actions, provides explicit trigger terms in a WHEN clause, and actively reduces conflict risk by referencing related skills for adjacent concerns. The description is concise yet comprehensive, using proper third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: control translation, expression conversion, data binding, code-behind lifecycle, and Master Page to Layout conversion. These are clearly defined, domain-specific tasks.	3 / 3
Completeness	Clearly answers both 'what' (migrate ASP.NET Web Forms markup to Blazor Server covering control translation, expression conversion, etc.) and 'when' (explicit WHEN clause with trigger phrases). Also includes boundary guidance with FOR SINGLE OPERATIONS directing to related skills.	3 / 3
Trigger Term Quality	Includes highly natural trigger terms that users would actually say: 'migrate aspx', 'convert web forms markup', 'master page to layout', 'asp prefix removal', 'data binding expressions'. Also includes file extensions (.aspx/.ascx/.master) and technology names (Blazor, BWFC).	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche (ASP.NET Web Forms markup to Blazor migration). Explicitly delineates boundaries by pointing auth and data/architecture tasks to sibling skills, reducing overlap risk.	3 / 3
	Total	12 / 12 Passed

Implementation

70%

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 and well-structured migration skill with excellent workflow clarity and progressive disclosure. Its main weakness is significant verbosity — the content could be cut by 30-40% without losing any actionable information. Redundant warnings (SelectMethod appears 3+ times), unnecessary explanations of what BWFC is, repeated pipeline summaries, and marketing-style descriptions inflate the token cost substantially.

Suggestions

Remove the 'What Is BWFC?' section entirely — Claude doesn't need a product overview, and the installation steps already convey what's needed.

Consolidate the three separate pipeline/workflow tables (Pipeline table, Pipeline Rules list, and Migration Workflow table) into a single concise representation to eliminate redundancy.

State the SelectMethod warning once prominently rather than repeating it in three separate locations (Layer 2 intro, Layer 2 bullet list, and Common Gotchas).

Remove explanatory notes that Claude already knows (e.g., 'Blazor always HTML-encodes', what NuGet packages are, what GitHub repositories are) to reduce token usage.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines. It explains what BWFC is (Claude can look this up), includes redundant summaries (the migration workflow table repeats the pipeline table), explains the same concepts multiple times (SelectMethod warnings appear 3+ times), and includes unnecessary context like NuGet/GitHub links and marketing-style bullet points ('58 components across 6 categories'). The 'What Is BWFC?' section is entirely unnecessary explanation.	1 / 3
Actionability	The skill provides highly concrete, executable guidance throughout: specific CLI commands, complete code snippets for installation/configuration, detailed before/after translation tables for every expression type, exact PowerShell commands for the migration script, and specific attribute mappings. The transformation rules are copy-paste ready.	3 / 3
Workflow Clarity	The two-layer pipeline is clearly sequenced with explicit ordering rules, critical warnings about not making manual fixes between layers, and a comprehensive per-page migration checklist with verification steps. The pipeline rules section explicitly states the sequence and the checklist includes build verification and rendering checks.	3 / 3
Progressive Disclosure	The skill clearly references three child documents (CONTROL-REFERENCE.md, CODE-TRANSFORMS.md, AJAX-TOOLKIT.md) with well-signaled descriptions of what each contains. Related skills are linked at the top. The main document serves as an overview with transformation tables while detailed patterns are appropriately delegated to child documents.	3 / 3
	Total	10 / 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: FritzAndFriends/BlazorWebFormsComponents
Commit: 9bf8669

Reviewed: 4 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.