**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.
80
71%
Does it follow best practices?
Impact
96%
1.43xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./migration-toolkit/skills/bwfc-identity-migration/SKILL.mdQuality
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 actions, natural trigger terms, explicit 'when' guidance, and boundary delineation from related skills. It uses proper third-person voice throughout and avoids vague language. The inclusion of cross-references to related skills for single operations further strengthens its distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: migrate OWIN→Core middleware, login/register/logout minimal API endpoints, BWFC login controls, cookie auth under Interactive Server, and role-based authorization. These are highly specific technical capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate ASP.NET Web Forms Identity to Blazor Server Identity, covering middleware, endpoints, controls, auth, authorization) and 'when' (explicit WHEN clause with trigger phrases). Also includes boundary guidance via 'FOR SINGLE OPERATIONS' directing to other skills. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'migrate identity', 'login page migration', 'OWIN to core', 'cookie auth blazor', 'LoginView migration'. These cover common variations of how a user would phrase this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting ASP.NET Web Forms Identity to Blazor Server migration specifically. Explicitly differentiates from related skills (bwfc-migration for markup, bwfc-data-migration for EF), reducing conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with comprehensive, executable code examples covering the full identity migration workflow. However, it is severely undermined by extreme verbosity and redundancy — key concepts like DisableAntiforgery and LoginView warnings are repeated 3-4 times each, and the content that should live in the companion IDENTITY-PATTERNS.md is duplicated inline. Adding validation checkpoints between migration steps would improve workflow reliability.
Suggestions
Eliminate redundant explanations: DisableAntiforgery is explained in 4 separate places, LoginView warnings in 3+ places, and the BWFC controls table appears twice. Consolidate each concept to a single authoritative location.
Move detailed endpoint templates, OWIN mapping table, and gotchas into IDENTITY-PATTERNS.md (and actually provide it as a bundle file), keeping only the quick reference pattern in SKILL.md.
Add explicit validation checkpoints: after Step 2 (verify services registered), after Step 4 (verify migration applied and tables exist), and after Step 5 (verify login flow works end-to-end).
Reduce the SKILL.md to ~100-150 lines by keeping only the overview, critical rules, quick reference, step sequence with validation, and pointers to companion docs for full examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It repeats the same concepts multiple times (e.g., DisableAntiforgery is explained in Critical Rules, the endpoint pattern, the endpoint templates section, AND a dedicated section; LoginView warning appears in Critical Rules, the migration table, the example, AND a bold warning block). The BWFC login controls table appears twice. Much content could be consolidated or moved to the referenced IDENTITY-PATTERNS.md companion document. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code throughout — complete C# endpoint implementations, Razor component markup, bash commands for package installation and migrations, and concrete before/after migration examples. Every step has specific, runnable code. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced and covers the full migration path, but there are no explicit validation checkpoints or feedback loops. After database migration (Step 4), there's no verification step. After configuring identity (Step 2), there's no way to confirm it works before proceeding. For a destructive migration workflow, this lack of validation caps the score at 2. | 2 / 3 |
Progressive Disclosure | Despite referencing a companion document (IDENTITY-PATTERNS.md), the SKILL.md itself is a monolithic wall of content that duplicates much of what should be in that companion. The overview table for IDENTITY-PATTERNS.md says it covers 'Cookie auth details, identity config steps, BWFC login controls, authorization patterns, endpoint templates, OWIN mapping, gotchas' — yet all of these topics are covered in extensive detail in the SKILL.md itself. No bundle files are provided, so the companion document doesn't exist to offload content to. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%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 (504 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
147d0c4
Table of Contents
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.