bwfc-identity-migration

Migrate ASP.NET Web Forms Identity and Membership authentication to Blazor Server Identity. Covers OWIN to ASP.NET Core middleware, login page migration, BWFC login controls, role-based authorization, and cookie auth under Interactive Server mode. WHEN: "migrate identity", "login page migration", "OWIN to core", "cookie auth blazor", "LoginView migration".

1.15x

Quality

82%

Does it follow best practices?

Impact

96%

1.15x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

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 scenario with concrete actions, explicit trigger terms, and a well-defined niche. It covers both what the skill does and when to use it, with natural keywords that developers would use when seeking help with this particular migration path. The description is concise yet comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: migrating OWIN to ASP.NET Core middleware, login page migration, BWFC login controls, role-based authorization, and cookie auth under Interactive Server mode. These are all concrete, well-defined tasks.	3 / 3
Completeness	Clearly answers both 'what' (migrate ASP.NET Web Forms Identity/Membership to Blazor Server Identity, covering OWIN, login pages, controls, role-based auth, cookie auth) and 'when' (explicit WHEN clause with trigger phrases like 'migrate identity', 'OWIN to core', etc.).	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'migrate identity', 'login page migration', 'OWIN to core', 'cookie auth blazor', 'LoginView migration'. These cover specific migration scenarios a developer would naturally describe. Also includes domain terms like 'Blazor Server', 'ASP.NET Web Forms', 'Membership authentication'.	3 / 3
Distinctiveness Conflict Risk	Highly specific niche: ASP.NET Web Forms to Blazor Server identity migration. The combination of source technology (Web Forms), target technology (Blazor Server), and domain (authentication/identity) makes this very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

64%

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 thorough migration guide with excellent concrete code examples covering a complex topic (Web Forms auth to Blazor Identity). Its main weaknesses are redundancy (cookie auth pattern and logout endpoint appear multiple times), lack of explicit validation checkpoints in the workflow, and the monolithic structure that could benefit from splitting detailed sections into referenced files. The critical warning about HttpContext being null in WebSocket circuits is valuable and well-explained.

Suggestions

Add explicit validation/verification steps after key stages — e.g., 'Verify: run the app and confirm /Account/Login returns 200' after Step 2, and 'Verify: check that the AspNetUsers table exists' after Step 4's database migration.

Remove redundant code — the logout endpoint appears twice (in 'Ready-to-Use Endpoint Templates' and 'Common Identity Gotchas'), and the cookie auth explanation is repeated. Consolidate to a single location and cross-reference.

Extract the 'Ready-to-Use Endpoint Templates' section and the BWFC login controls mapping into separate referenced files to reduce the main skill's length and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~350+ lines) with some redundancy — the cookie auth under Interactive Server mode is explained in the critical warning section, then repeated in the 'Ready-to-Use Endpoint Templates' section with nearly identical code. The 'Common Identity Gotchas' section repeats the logout endpoint and cookie auth requirement already covered. Some explanatory text (e.g., 'Why this happens' paragraph) could be tightened, though it does add value for a tricky concept.	2 / 3
Actionability	Excellent actionability throughout — every step includes fully executable code (bash commands, C# code, Razor markup), specific package names, concrete migration examples with before/after comparisons, and ready-to-use endpoint templates. The code is copy-paste ready and covers login, register, and logout flows completely.	3 / 3
Workflow Clarity	Steps are numbered (1-7) with a clear sequence, but there are no explicit validation checkpoints. For a migration involving database schema changes, authentication configuration, and middleware ordering, there should be verification steps (e.g., 'verify the migration applied correctly', 'test that authentication works before proceeding'). The 'ORDER MATTERS' comment on middleware is good but insufficient for the overall workflow.	2 / 3
Progressive Disclosure	The skill references related skills at the top (/bwfc-migration, /bwfc-data-migration) which is good, but the content itself is monolithic — all 350+ lines are in a single file. The endpoint templates, OWIN middleware mapping table, and BWFC login controls reference could each be separate files. Internal anchor references (e.g., '#disableantiforgery-requirement') provide some navigation but the document is still very long for a single skill file.	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 (513 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

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.