bwfc-migration

Migrate ASP.NET Web Forms applications to Blazor Server using the webforms-to-blazor CLI tool and BlazorWebFormsComponents (BWFC). Orchestrates L1 automated transforms via CLI, then guides L2 contextual transforms. WHEN: "migrate aspx", "convert web forms", "web forms to blazor", "run migration". INVOKES: webforms-to-blazor CLI tool. FOR SINGLE OPERATIONS: use /bwfc-identity-migration for auth, /bwfc-data-migration for EF/architecture.

1.23x

Quality

82%

Does it follow best practices?

Impact

63%

1.23x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

77%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 highly actionable, well-sequenced migration skill with strong workflow validation and concrete examples, weakened mainly by verbosity/repetition and by one-level-deep references that point to bundle files which are not actually present.

Suggestions

Provide the referenced bundle files (CODE-TRANSFORMS.md, CONTROL-REFERENCE.md, AJAX-TOOLKIT.md, and the recipes/*.md files) in a references/ directory, or remove the dangling links and inline only what is needed.

De-duplicate the Response.Redirect guidance: cover it once (e.g. in Phase 2) and reference that section from the anti-patterns and decision tree instead of re-explaining it three times.

Move the large shim/control reference tables into CONTROL-REFERENCE.md / CODE-TRANSFORMS.md and keep SKILL.md as a lean overview, which would simultaneously improve conciseness and progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is ~47KB with notable redundancy: the Response.Redirect revert is explained in the anti-patterns, the decision tree, and again as a dedicated Phase 2 step, and the shim tables are re-explained in the anti-patterns section. Content is mostly domain-specific rather than generic filler, but the repetition keeps it at 'mostly efficient, could be tightened.'	3 / 5
Actionability	It provides copy-paste-ready CLI commands, before/after code blocks for every TODO category, a build-error→fix table, and concrete transform listings, fully covering the common migration cases.	5 / 5
Workflow Clarity	The L1→L2→Build & Verify→L3 phases are clearly sequenced with an explicit validation gate (Phase 3 `dotnet build`), an error→fix feedback loop, and a per-page migration checklist; validation is present so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	Structure and sectioning are good and one-level-deep references (CODE-TRANSFORMS.md, CONTROL-REFERENCE.md, AJAX-TOOLKIT.md, recipes/*.md) are clearly signaled, but those referenced files do not exist in the bundle and substantial reference material is inlined in SKILL.md, placing it between anchors 3 and 4 and pulling down to 3 due to the broken references.	3 / 5
	Total	16 / 20 Passed

Description

87%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, third-person description that clearly states what the skill does and when to use it, with concrete trigger phrases and explicit routing to sibling skills for single operations. The only weakness is slightly less granular action verbs and a few missing trigger synonyms/extensions.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions tied to specific tools ("Migrate ASP.NET Web Forms applications to Blazor Server using the webforms-to-blazor CLI tool", "Orchestrates L1 automated transforms via CLI, then guides L2 contextual transforms"), with only minor abstraction in the verb choices; not a full 5 because "orchestrates"/"guides" are less granular than enumerating the underlying actions.	4 / 5
Completeness	It explicitly answers both what (migrate Web Forms to Blazor, orchestrate L1, guide L2) and when (a WHEN clause with concrete trigger phrases), plus routing guidance for single operations, matching the anchor that requires concrete trigger phrases for both.	5 / 5
Trigger Term Quality	The WHEN clause supplies natural phrases users would say ("migrate aspx", "convert web forms", "web forms to blazor", "run migration") with good coverage, but it omits common synonyms/extensions like ".aspx", "ASP.NET", or "WebForms" that would push it to a 5.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear niche (Web Forms to Blazor Server migration) with distinct triggers and explicit de-confliction by routing auth/EF work to sibling skills, minimizing overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1158 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: FritzAndFriends/BlazorWebFormsComponents
Path: migration-toolkit/skills/bwfc-migration/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.