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".

1.66x

Quality

76%

Does it follow best practices?

Impact

100%

1.66x

Average score across 1 eval scenario

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./migration-toolkit/skills/migration-standards/SKILL.md

Quality

Content

65%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 and concrete, with excellent code examples and a clear L1/L2 boundary, but it is a verbose monolith that repeats material across sections and lacks both validation feedback loops and file-based progressive disclosure.

Suggestions

De-duplicate the SessionShim/Response.Redirect material: describe each shim once in the shims table and reference it from the mandatory rules and Page Base Class sections instead of re-explaining.

Add an explicit validation checkpoint to the migration workflow (e.g., 'run dotnet build after Layer 1; only proceed to Layer 2 when it compiles') to satisfy the batch-operation feedback-loop expectation.

Split the large reference material (shims table, Page Lifecycle Mapping, anti-patterns) into separate files under references/ and link to them from SKILL.md so the overview stays lean.

Dimension	Reasoning	Score
Conciseness	The 645-line body is mostly relevant domain knowledge Claude lacks, but several points are repeated across sections (SessionShim/Response.Redirect appear in mandatory rules, Page Base Class, dedicated sections, and the shim table), so it could be tightened without loss.	3 / 5
Actionability	It provides copy-paste-ready Razor/C# snippets, exact commands ("dotnet new blazor --interactivity Server"), specific package versions (10.0.3), namespaces, and concrete before/after examples covering the common migration cases.	5 / 5
Workflow Clarity	The Layer 1→Layer 2 sequence and boundary rule are explicit, but this batch migration workflow lacks an explicit validate→fix→retry feedback loop (e.g., build/compile verification checkpoint), which caps workflow clarity at 3 per the batch-operation guideline.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but with no bundle files present the entire 645-line skill is a single monolithic document; the shim reference table, page lifecycle mapping, and anti-pattern gallery clearly belong in separate reference files.	3 / 5
	Total	14 / 20 Passed

Description

87%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, well-scoped description that clearly states both capability and explicit trigger phrases for a specialized migration niche. The only weakness is action-verb specificity in the leading clause.

Dimension	Reasoning	Score
Specificity	The description enumerates several concrete areas ("target architecture (.NET 10, Server Interactive), database provider detection, event handler preservation, SelectMethod patterns, and page lifecycle mapping"), but the leading verb "Enforce...standards" and "Covers..." are topic enumeration rather than crisp action verbs, leaving minor gaps versus the comprehensive-action anchor.	4 / 5
Completeness	It explicitly answers both what ("Enforce canonical migration standards for ASP.NET Web Forms to Blazor using BWFC" plus the covered areas) and when (an explicit WHEN: clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	The WHEN clause lists natural domain triggers ("migration standards", "target architecture", "render mode placement", "page base class", "Layer 1 vs Layer 2") a practitioner would actually say, but coverage lacks some synonyms/variants that would push it to the top anchor.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply scoped to ASP.NET Web Forms→Blazor migration via BWFC with distinct, specialized triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 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 (646 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

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