webforms-html-audit
Patterns for comparing Web Forms control HTML output against Blazor component output using Playwright
55
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.squad/skills/webforms-html-audit/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description targets a very specific technical niche (Web Forms vs Blazor HTML comparison with Playwright), which gives it strong distinctiveness. However, it lacks explicit trigger guidance ('Use when...'), uses vague framing ('Patterns for comparing'), and doesn't enumerate concrete actions the skill performs. Adding explicit triggers and more specific action verbs would significantly improve its utility for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when migrating from ASP.NET Web Forms to Blazor and needing to compare rendered HTML output between the two frameworks.'
Replace 'Patterns for comparing' with specific concrete actions, e.g., 'Captures and diffs HTML output from Web Forms controls and Blazor components using Playwright, identifies rendering discrepancies, and validates migration parity.'
Include additional natural trigger terms like 'ASP.NET migration', 'rendering comparison', 'DOM diff', 'UI parity testing' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a specific domain (comparing Web Forms HTML output against Blazor component output) and mentions a specific tool (Playwright), but it says 'Patterns for comparing' which is vague about what concrete actions are performed—it doesn't list specific actions like 'capture snapshots', 'diff HTML output', or 'generate comparison reports'. | 2 / 3 |
Completeness | The description addresses 'what' at a high level (comparing Web Forms vs Blazor HTML output using Playwright) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also somewhat vague ('Patterns for comparing'), this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'Web Forms', 'Blazor', 'Playwright', 'HTML output', and 'component output' that a developer in this niche would use. However, it misses common variations or related terms like 'migration', 'ASP.NET', 'rendering comparison', 'DOM comparison', or 'UI testing'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Web Forms, Blazor, HTML output comparison, and Playwright is highly specific and occupies a very narrow niche. It is unlikely to conflict with other skills given this unique intersection of technologies and purpose. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides valuable domain-specific knowledge about Web Forms to Blazor HTML comparison that Claude wouldn't inherently know, particularly the normalization rules and control classification. However, it lacks executable code examples for the core operations (Playwright extraction script, normalization pipeline) and doesn't present a clear end-to-end workflow with validation steps. The content reads more as a reference guide than an actionable skill.
Suggestions
Add a complete, executable Playwright script example that extracts and compares HTML between Web Forms and Blazor pages, including the normalization pipeline as actual code rather than prose descriptions.
Add an explicit end-to-end workflow section with numbered steps, validation checkpoints (e.g., 'verify normalization removed all framework artifacts before comparing'), and error recovery guidance.
Provide a concrete example of the Intentional Divergence Registry format (e.g., a JSON/YAML schema or markdown table with a sample entry) rather than just listing what fields it should contain.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and domain-specific, but the Context section explains why HTML fidelity matters which Claude can infer. Some normalization rules could be more terse. The control classification section adds useful but slightly verbose descriptions. | 2 / 3 |
Actionability | Provides one concrete HTML example for marker isolation and specific Playwright locator syntax, but the normalization rules are described in prose rather than executable code. No complete Playwright script or normalization function is provided — these are described rather than demonstrated. | 2 / 3 |
Workflow Clarity | The checklist at the end implies a sequence, and the normalization rules are numbered, but there's no explicit end-to-end workflow with validation checkpoints or feedback loops. For a batch HTML comparison operation, the lack of a validate-fix-retry loop caps this at 2. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Patterns, Anti-patterns, Checklist), but all content is inline in a single file. The Intentional Divergence Registry concept is mentioned but not linked to a separate file or template, and the content is long enough that some sections (e.g., normalization rules, classification details) could benefit from being split out. | 2 / 3 |
Total | 8 / 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
9bf8669
- 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.