migration-standards
Enforce canonical migration standards for ASP.NET Web Forms to Blazor using BWFC. Covers target architecture (.NET 10, Server Interactive), database provider detection, event handler preservation, SelectMethod patterns, and page lifecycle mapping. WHEN: "migration standards", "target architecture", "render mode placement", "page base class", "Layer 1 vs Layer 2".
78
71%
Does it follow best practices?
Impact
94%
2.84xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./migration-toolkit/skills/migration-standards/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 a strong skill description that clearly defines a narrow, specific domain (ASP.NET Web Forms to Blazor migration) with concrete capabilities and explicit trigger terms. It uses proper third-person voice, lists multiple specific actions, and includes a well-structured WHEN clause with natural keywords that users in this domain would use. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: enforce migration standards, covers target architecture (.NET 10, Server Interactive), database provider detection, event handler preservation, SelectMethod patterns, and page lifecycle mapping. These are detailed, domain-specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (enforce canonical migration standards for ASP.NET Web Forms to Blazor, covering specific technical areas) and 'when' (explicit WHEN clause with trigger terms like 'migration standards', 'target architecture', 'render mode placement', etc.). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that users in this domain would actually say: 'migration standards', 'target architecture', 'render mode placement', 'page base class', 'Layer 1 vs Layer 2', plus domain terms like 'ASP.NET Web Forms', 'Blazor', 'BWFC', 'SelectMethod', 'page lifecycle'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: ASP.NET Web Forms to Blazor migration using BWFC. The combination of framework-specific terms and migration-specific triggers makes it very unlikely to conflict with other skills. | 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 before/after code examples covering every migration pattern. However, it is severely bloated — the same concepts (use shims, don't inject raw services, don't replace BWFC components) are restated 3-4 times across different sections, and the entire document could be cut by 40-50% without losing information. The lack of content splitting into referenced files makes this a monolithic reference that consumes excessive context window budget.
Suggestions
Extract the anti-patterns section, compile-compatibility shims table, and page lifecycle mapping into separate referenced files (e.g., ANTI-PATTERNS.md, SHIMS-REFERENCE.md, LIFECYCLE.md) to reduce the main skill to an overview with navigation links.
Deduplicate the repeated guidance: the mandatory rules, patterns sections, and anti-patterns all say 'use shims not raw services' and 'use BWFC components not raw HTML' — consolidate into a single authoritative statement in the mandatory rules and remove redundant restatements.
Add an explicit numbered migration workflow with validation checkpoints (e.g., 'After L1: verify build compiles → After L2 EF Core: verify database connection → After L2 identity: verify auth flow') to improve workflow clarity.
Remove explanatory prose that Claude can infer from examples alone — e.g., the paragraph explaining what SessionShim does is redundant given the before/after code example and the shims table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~500+ lines. There is massive redundancy: Session/shim patterns are explained multiple times (mandatory rules, patterns section, session state section, compile-compatibility shims, page lifecycle mapping, anti-patterns). The anti-patterns section alone has 7 examples that largely restate the mandatory rules. Many tables repeat information Claude could infer from a single clear statement. | 1 / 3 |
Actionability | The skill provides fully executable code examples throughout — complete Razor markup, C# code-behind, PowerShell commands, JSON configuration, and Playwright test patterns. Every pattern has concrete before/after examples that are copy-paste ready. | 3 / 3 |
Workflow Clarity | The Layer 1 vs Layer 2 boundary is clearly defined with a critical warning about sequencing, and the page lifecycle mapping table provides clear phase annotations. However, there are no explicit validation checkpoints in the overall migration workflow — no 'verify the build compiles after L1 before running L2' step, no checklist for verifying database provider detection, and the overall migration sequence is implicit rather than explicitly numbered with validation gates. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no external file references for detailed content. The shim reference table, all anti-patterns, the full event handler strategy, database migration details, identity migration, Playwright patterns, and static asset relocation are all inline. References to 'bwfc-migration skill CODE-TRANSFORMS.md' and 'bwfc-migration skill' exist but no bundle files support them, and the content that could be split (shim reference, anti-patterns catalog, lifecycle mapping) remains entirely inline. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (644 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- FritzAndFriends/BlazorWebFormsComponents
- Commit
147d0c4
- 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.