bwfc-identity-migration

**WORKFLOW SKILL** — Migrate ASP.NET Web Forms Identity and Membership authentication to Blazor Server Identity. Covers OWIN→Core middleware, login/register/logout minimal API endpoints, BWFC login controls, cookie auth under Interactive Server, and role-based authorization. WHEN: "migrate identity", "login page migration", "OWIN to core", "cookie auth blazor", "LoginView migration". INVOKES: dotnet CLI for identity scaffolding. FOR SINGLE OPERATIONS: use bwfc-migration for markup, bwfc-data-migration for EF.

1.43x

Quality

82%

Does it follow best practices?

Impact

96%

1.43x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

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

Highly actionable content with excellent copy-paste code, held back by repeated warnings that bloat the token budget and by a missing referenced companion file. The destructive database-migration step also lacks the validation feedback loop the rubric requires.

Suggestions

Add a validation checkpoint to the database migration step (e.g., run `dotnet ef migrations script --idempotent` to review, back up the DB, then verify row counts/identity tables after `database update`) so destructive operations get a validate-fix-retry loop.

Consolidate the LoginView-vs-AuthorizeView and DisableAntiforgery warnings, each currently stated three times, into a single authoritative section that other steps link back to.

Either create the referenced IDENTITY-PATTERNS.md companion file or remove the reference and the duplicated 'Companion Documents' material that already appears inline, so navigation is not broken.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable code and tables rather than padded conceptual explanation, but several warnings are repeated (LoginView-vs-AuthorizeView stated three times, DisableAntiforgery explained three times, the login endpoint shown twice), which is trimmable redundancy.	4 / 5
Actionability	Concrete, copy-paste-ready C#/razor/bash snippets cover the common cases — endpoint templates for login/register/logout, DbContext setup, schema-migration commands, and control-mapping tables — fully executable guidance.	5 / 5
Workflow Clarity	The L2 playbook is clearly sequenced (Steps 1–7), but Step 4 runs a destructive database operation (`dotnet ef database update`) with no validation checkpoint or validate-fix-retry feedback loop, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Sections are well organized and one companion doc (IDENTITY-PATTERNS.md) is signaled one level deep, but that referenced file is absent from the bundle, and material the companion claims to hold (endpoint templates, OWIN mapping, gotchas) is inlined here, leaving structure partially broken.	3 / 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, concrete description that names the domain, lists specific actions, and provides explicit WHEN triggers plus sibling-skill disambiguation. Trigger term coverage is the only mild gap, missing synonyms and extension variants.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Migrate ASP.NET Web Forms Identity and Membership authentication to Blazor Server Identity' plus 'OWIN→Core middleware, login/register/logout minimal API endpoints, BWFC login controls, cookie auth...role-based authorization' — giving comprehensive coverage of the migration surface.	5 / 5
Completeness	It explicitly answers both 'what' (migrate Identity/Membership auth, covering the listed subsystems) and 'when' (a concrete WHEN: trigger clause), satisfying the top anchor.	5 / 5
Trigger Term Quality	The WHEN clause supplies natural phrases users would say ('migrate identity', 'login page migration', 'OWIN to core', 'cookie auth blazor', 'LoginView migration'), but it lacks synonyms and file/extension variants, so it is a notch below comprehensive.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear niche (Web Forms Identity → Blazor) with distinct triggers and explicit disambiguation ('FOR SINGLE OPERATIONS: use bwfc-migration... bwfc-data-migration...'), minimizing overlap risk.	5 / 5
	Total	19 / 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 (504 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

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