CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webforms-migration

Migrate ASP.NET Web Forms applications (.aspx/.ascx/.master) to Blazor Server using BlazorWebFormsComponents (BWFC). Use this skill when converting Web Forms markup, code-behind, Master Pages, User Controls, or data-binding patterns to Blazor equivalents.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A highly actionable, comprehensive migration reference with concrete commands and before/after tables, but it is held back by content redundancy, the absence of inline validation checkpoints in the migration recipe, and a monolithic single-file structure with no external references.

Suggestions

De-duplicate the removed-attributes list (Directive Conversion vs. 'Attributes Removed During Migration') and the blazor.web.js 404 guidance (Step 3b/3c vs. Common Gotchas) by keeping one canonical location and cross-referencing it.

Add explicit validation checkpoints to the migration recipe (e.g., 'run `dotnet build` and load the page in the browser after Step 6') so the destructive rewrite has a verify-fix-retry loop.

Move the large Control Translation Table and the Identity & Authentication sections into separate reference files under references/, leaving SKILL.md as an overview that links to them one level deep.

DimensionReasoningScore

Conciseness

Mostly efficient reference tables, but there is real redundancy: the 'Attributes Removed During Migration' section repeats the 'Drop these attributes entirely' list from Directive Conversion, and the blazor.web.js 404 fix is explained both in Step 3b/3c and again in Common Gotchas.

3 / 5

Actionability

Fully executable guidance throughout — concrete dotnet CLI commands, complete before/after code blocks for every control category, and copy-paste-ready translation tables covering the common cases.

5 / 5

Workflow Clarity

A clear 8-step sequence is present, but a migration is a destructive/batch rewrite and the recipe has no inline validation checkpoints between steps; the Common Gotchas section is troubleshooting, not step-level verification, so the rubric cap of 3 applies.

3 / 5

Progressive Disclosure

Good internal section structure, but no bundle/reference files exist and the SKILL.md is the full detailed material rather than an overview pointing to references; large reference blocks (Control Translation Table, Identity & Auth) that belong in separate files are inlined.

3 / 5

Total

14

/

20

Passed

Description

95%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, library, file extensions, and a broad set of conversion targets with an explicit 'Use when' trigger clause. The only minor weakness is that the action verbs are dominated by a single 'migrate/convert' notion applied to several artifacts.

DimensionReasoningScore

Specificity

Lists several concrete conversion targets (markup, code-behind, Master Pages, User Controls, data-binding) plus file extensions and the named BWFC library, but the actions cluster under one verb (migrate/convert) rather than distinct operations.

4 / 5

Completeness

Explicitly answers both what ('Migrate ASP.NET Web Forms applications ... to Blazor Server using BWFC') and when ('Use this skill when converting Web Forms markup, code-behind, Master Pages, User Controls, or data-binding patterns').

5 / 5

Trigger Term Quality

Comprehensive natural terms a migrating user would say — 'Web Forms', 'Blazor', 'code-behind', 'Master Pages', 'User Controls', 'data-binding' — including the .aspx/.ascx/.master file extensions.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Web Forms → Blazor Server via BWFC) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (754 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

FritzAndFriends/BlazorWebFormsComponents

Path

.github/skills/webforms-migration/SKILL.md

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.