Tessl • The package manager for agent skills

Blog Docs Log inGet started

SkillPublic

semantic-pattern-guardrails

Guardrails for implementing Web Forms semantic page-pattern rewrites in the migration CLI

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/semantic-pattern-guardrails/SKILL.md

Quality

Content

82%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 a lean, high-signal set of guardrails: exact slot mappings, per-pattern safe-match/stop criteria, a concrete output contract, and an explicit anti-pattern list, with essentially no token waste. It falls just short of top marks on actionability and workflow clarity because the razor examples are skeletons and there is no validation or TODO-emission feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is imperative bullet lists with zero filler; every line encodes migration-specific contracts (slot mappings, safe-match criteria, middleware constraints) Claude could not know. Even the "Why:" section earns its tokens — it explains non-obvious OWIN/Identity HTTP semantics. Matches anchor 5; there is no over-explanation to push it to 4.	5 / 5
Actionability	Concrete guidance throughout — exact mappings ("master shell markup → ChildContent", "migrated <Content> blocks → ChildComponents"), explicit safe-match and stop conditions, and a minimum output contract with razor templates. Falls short of 5 because the razor examples are placeholder skeletons rather than complete code and no TODO/manual-review emission format is shown.	4 / 5
Workflow Clarity	The sequence is explicit ("Let the markup transforms do the local tag conversion first", then normalize) with decision checkpoints ("Stop and emit TODO/manual review if..."). Not 5 because there is no validate→fix→retry feedback loop or final verification step for the normalized contract.	4 / 5
Progressive Disclosure	Sections are well-organized (Context, Patterns, output contract, Anti-Patterns) with no content that clearly belongs in a separate reference file, and no bundle files exist to offload to. The body exceeds 50 lines, so the simple-skill exception to reach 5 does not cleanly apply — good structure with minor room to split, matching anchor 4.	4 / 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 carves out a highly distinct, well-scoped niche but reads as a domain label rather than a capability statement: it says what area it covers without listing concrete actions or any "use when" trigger guidance. It is specific but incomplete.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding semantic catalog entries for Web Forms page-pattern rewrites in the migration CLI, or when normalizing master/content page contracts after mechanical transforms."

Name the concrete page-pattern families it governs (master/content normalization, query/detail, action, account pages) so users and Claude can match on those phrases.

Include natural synonyms users would say — master pages, ContentPlaceHolder, Blazor migration — to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Guardrails for implementing Web Forms semantic page-pattern rewrites" names a precise domain plus one concrete action, but stops there — no list of capabilities. Fits anchor 3 (domain + 1-2 concrete actions, not comprehensive); not 4 since it doesn't list several actions, and not 2 since the action named is specific rather than generic.	3 / 5
Completeness	The "what" is clear (guardrails for semantic page-pattern rewrites), but there is no "Use when..." or equivalent trigger clause — the rubric guideline caps completeness at 3 for a missing explicit trigger. Not 4 because "when" is entirely absent rather than just weak.	3 / 5
Trigger Term Quality	Terms like "Web Forms", "semantic", "page-pattern", and "migration CLI" are relevant, but natural variations a user would say — master pages, ContentPlaceHolder, Blazor, .aspx — are missing. Matches anchor 3 (some relevant keywords, missing common variations).	3 / 5
Distinctiveness Conflict Risk	The niche is extremely specific (Web Forms semantic rewrites within a migration CLI), so it is clearly distinguishable from other skills with minimal wrong-trigger risk. Matches anchor 5; not 4 because no realistic overlap with neighboring skills exists.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/semantic-pattern-guardrails/SKILL.md
Revision: 3154758

Reviewed: 20 days ago

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.

semantic-pattern-guardrails

Table of Contents

Is this your skill?