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

81%

Does it follow best practices?

Impact

63%

1.23x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

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 workflow with concrete tools, explicit trigger terms, and well-defined boundaries. It uses proper third-person voice, avoids vague language, and even cross-references related skills to reduce ambiguity. The WHEN clause with natural user phrases and the FOR SINGLE OPERATIONS boundary guidance are particularly strong.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: migrate ASP.NET Web Forms to Blazor Server, orchestrate L1 automated transforms via CLI, guide L2 contextual transforms. Also references specific tools (webforms-to-blazor CLI, BlazorWebFormsComponents/BWFC) and cross-references related skills for auth and data migration.	3 / 3
Completeness	Clearly answers both 'what' (migrate ASP.NET Web Forms to Blazor Server using specific tools, orchestrate L1/L2 transforms) and 'when' (explicit WHEN clause with trigger phrases). Also includes boundary guidance via 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', 'web forms to blazor', 'run migration'. Also includes domain-specific terms like 'ASP.NET Web Forms', 'Blazor Server', 'BWFC' that would naturally appear in user requests.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a very specific niche: ASP.NET Web Forms to Blazor migration. The description explicitly delineates boundaries with related skills (/bwfc-identity-migration, /bwfc-data-migration), reducing conflict risk. The technology stack is specific enough to avoid overlap with generic migration or code conversion skills.	3 / 3
	Total	12 / 12 Passed

Implementation

62%

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

This skill is highly actionable with excellent workflow clarity, providing a comprehensive and well-structured migration guide with concrete CLI commands, code examples, and validation checkpoints. However, it suffers severely from verbosity — the same core message ('use the shims, don't fight them') is repeated in at least 6 different sections with overlapping examples, and substantial reference material is inlined rather than delegated to supporting files. The content would be significantly more effective at roughly 40% of its current length.

Suggestions

Extract the anti-patterns section, shim reference tables, WebFormsForm/ClientScript/PostBack details, and common patterns into separate reference files (e.g., ANTI-PATTERNS.md, SHIM-REFERENCE.md) and link from the main skill — this would cut the main file by ~50%.

Consolidate the repeated 'use the shims' messaging: the shim table, decision tree, anti-patterns, session-state TODO section, and 'Key Benefits' section all say the same thing — reduce to one authoritative section with a brief reminder elsewhere.

Remove the 8 anti-pattern examples and replace with a concise 'DO NOT' bullet list — Claude doesn't need 8 separate before/after code blocks to understand 'use shims instead of manual alternatives'.

The decision tree section is entirely redundant with the shim compatibility table above it — remove one or the other.

Dimension	Reasoning	Score
Conciseness	This skill is extremely verbose at ~800+ lines. It extensively repeats the same concepts (e.g., 'use the shims' is stated dozens of times with nearly identical examples), includes 8 anti-pattern examples that all convey the same message, and the decision tree restates what the shim tables already cover. Significant token waste through redundancy.	1 / 3
Actionability	The skill provides fully executable CLI commands with complete option tables, concrete code examples for every transform pattern, specific error-fix tables, and copy-paste ready code for both before/after migration scenarios. The migration checklist is immediately usable.	3 / 3
Workflow Clarity	The four-phase workflow (L1 CLI → L2 Copilot → Build/Verify → L3 Developer) is clearly sequenced with explicit validation steps (dotnet build, migration report review, per-page checklist). The TODO-driven L2 process with category-specific transforms provides clear feedback loops, and the troubleshooting tables address error recovery.	3 / 3
Progressive Disclosure	The skill references three child documents (CODE-TRANSFORMS.md, CONTROL-REFERENCE.md, AJAX-TOOLKIT.md) and recipe files appropriately, but the main SKILL.md contains enormous amounts of inline content that should be split out — the anti-patterns section, the full shim reference table, the WebFormsForm/ClientScript/PostBack detailed sections, and the common patterns tables could all be in separate reference files. No bundle files were provided to verify references exist.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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

	Total	10 / 11 Passed

Repository: FritzAndFriends/BlazorWebFormsComponents
Commit: 147d0c4

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