CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-compile-surface-hardening

Keep migrated Blazor output compiling when more Web Forms artifacts stay on the generated compile surface

59

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/cli-compile-surface-hardening/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

The body is concise and well-structured with concrete, code-level patterns and a clear pointer to example files. Its main gap is the absence of an explicit validation/verification step in the transform-and-stub workflow.

Suggestions

Add an explicit verification checkpoint after stub generation and transform registration, e.g. 'Verify the migrated project compiles and run BlazorWebFormsComponents.Cli.Tests before considering the change complete.'

Promote at least one pattern (e.g. the validator generic-argument mapping) into a short executable code snippet showing the before/after to lift actionability toward copy-paste ready.

Make the workflow order explicit with a numbered sequence (apply code-behind transforms -> run markup stub generation -> register transforms in DI + tests -> verify compile/tests) so the ordering and checkpoint are unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, never explaining what Blazor/Web Forms/Razor are; every line (Context, Patterns, Examples, Anti-Patterns) earns its place.

5 / 5

Actionability

Provides concrete code-level guidance (e.g. 'EnforceCodeStyleInBuild>false', 'RequiredFieldValidator -> Type="string"', '@MethodName() -> render-method stub returning object?'), but patterns are shorthand mappings rather than full copy-paste executable blocks, leaving minor gaps.

4 / 5

Workflow Clarity

A sequence is present ('Run markup-driven member stub generation after the main code-behind transforms', 'Register new transforms in both production DI and test helpers'), but there is no explicit validation/verify checkpoint; given the batch code-generation nature, the rubric cap of 3 applies.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no external bundle files and is well-organized into Context, Patterns, Examples, and Anti-Patterns sections, with the Examples section pointing to real codebase files rather than inlining them.

5 / 5

Total

17

/

20

Passed

Description

57%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.

The description is well-targeted to a distinct migration niche but reads as a domain statement rather than an explicit trigger. It lacks a 'Use when...' clause and natural synonyms that would raise trigger quality and completeness.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when the migration CLI emits more generated .razor.cs files or copies legacy source into the output project.'

Include natural user-facing synonyms like 'port', 'convert', or 'migrate Web Forms to Blazor' alongside the technical jargon to improve trigger term coverage.

Optionally enumerate one or two more concrete actions (e.g. 'fix validator generic arguments, generate markup-referenced member stubs') to move specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (Blazor/Web Forms migration) and one concrete goal ('Keep migrated Blazor output compiling'), but lists no comprehensive set of actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

Has a clear 'what' (keep output compiling), but the embedded 'when more Web Forms artifacts stay on the generated compile surface' describes a code state rather than explicit 'Use when...' invocation guidance, so completeness caps at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains relevant keywords ('Blazor', 'Web Forms', 'compiling') a user would say, but leans on jargon like 'compile surface' and omits natural synonyms like 'port' or 'convert', so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

Targets a narrow niche (Web Forms to Blazor compile-surface hardening) with distinct triggers, making overlap with other skills minimal.

5 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

FritzAndFriends/BlazorWebFormsComponents

Path

.squad/skills/cli-compile-surface-hardening/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.