blazor-auth-migration
Guides correct AuthenticationStateProvider registration when migrating ASP.NET Web Forms Identity/OWIN authentication to Blazor Server using scoped providers and cookie-based auth. Covers DI lifetime pitfalls (singleton vs scoped vs transient), minimal API auth endpoints, and integration with BWFC LoginView. Use when migrating authentication, fixing session bleed across browser tabs, debugging shared auth state in Playwright tests, or setting up cookie-based login and registration endpoints in a Blazor Server migration.
88
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 is highly specific, includes a comprehensive 'Use when...' clause with natural trigger scenarios, and occupies a very distinct niche. It covers both the capabilities and the trigger conditions thoroughly, using concrete technical terms that developers would naturally use when encountering these issues.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: AuthenticationStateProvider registration, DI lifetime pitfalls (singleton vs scoped vs transient), minimal API auth endpoints, integration with BWFC LoginView. Very detailed and technical. | 3 / 3 |
Completeness | Clearly answers both 'what' (guides AuthenticationStateProvider registration, covers DI lifetime pitfalls, minimal API auth endpoints, BWFC LoginView integration) and 'when' with an explicit 'Use when...' clause listing four specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'migrating ASP.NET Web Forms', 'Blazor Server', 'cookie-based auth', 'session bleed across browser tabs', 'Playwright tests', 'login and registration endpoints', 'AuthenticationStateProvider', 'DI lifetime', 'OWIN authentication'. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely niche and specific to a particular migration path (ASP.NET Web Forms Identity/OWIN to Blazor Server). The combination of technologies and specific issues like session bleed and scoped providers makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that clearly communicates a critical DI registration pattern for Blazor Server auth migration. Its main strengths are executable code examples and well-structured anti-patterns with concrete symptoms. Weaknesses include some unnecessary explanation of DI concepts Claude already understands and the lack of an explicit verification step to confirm the fix works.
Suggestions
Remove the 'Why this works' bullets or reduce them to a single line — Claude understands DI lifetimes and factory registrations without explanation.
Add a brief verification step, e.g., 'Verify: open two browser tabs, log in on one, confirm the other remains unauthenticated' to provide a validation checkpoint for the migration workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary explanation. The 'Why this works' bullets explain DI concepts Claude already knows (what AddScoped does, what factory registration means). The context section about 'Run 7, Iteration 2' is project-specific noise that doesn't help Claude apply the skill. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for both the correct registration pattern and the minimal API auth endpoints. Anti-patterns include concrete code with specific symptoms, making it easy to diagnose and fix issues. | 3 / 3 |
Workflow Clarity | The skill clearly presents correct vs incorrect patterns, but there's no explicit workflow sequence for migrating auth. There are no validation checkpoints — e.g., how to verify the registration is scoped (checking DI container, running a test). For a migration task involving auth state, a verify step would be valuable. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines of content), the structure is well-organized with clear sections: Context, Core Rule, Patterns, Anti-Patterns, and Examples. No need for external file references given the scope, and the content is easy to scan with headers and emoji markers. | 3 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- FritzAndFriends/BlazorWebFormsComponents
- Commit
1bd9b17
- Reviewed
Table of Contents
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.