CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

broken-html

Use when auditing metadata, crawlability, structured data, or indexability related to Fix malformed HTML structure. Verify the rendered HTML and HTTP response rather than relying only on source files.

Quality

71%

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 ./skills/broken-html/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-organized, token-efficient overview with excellent progressive disclosure to a real, one-level reference file. Its main weakness is actionability: the Check/Fix sections name the error types but never give an executable validation command or a concrete way to inspect rendered output, leaving the how-to entirely to the reference.

Suggestions

Name a concrete validation tool in the Check section (e.g., W3C validator, `npx html-validate .`, or `tidy -errors index.html`) so the check is executable without opening the reference.

Add a one-line re-validation step after Fix (re-run the validator against the rendered output) to close the feedback loop within the body.

Merge the overlapping Quick Reference, Check, and Fix sections into a single streamlined section to remove the triplicated guidance.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (no explanation of what HTML is), and every section is brief. Not 5 because of minor redundancy: the "Quick Reference" bullets largely restate "Check" and "Fix", and the thin "Explain" section adds little. Not 3 because there is no unnecessary explanation or padding beyond that overlap.

4 / 5

Actionability

Concrete error types are named ("unclosed tags, incorrect nesting, or structural errors", "stray tags or unescaped characters") but no executable tool or command is given — no validator (W3C validator, html-validate, tidy) and no concrete step for inspecting rendered output (e.g., curl or devtools); code examples live only in the reference file. Not 4 because the body lacks a specific executable step; not 2 because the guidance specifies what to look for rather than offering only high-level hints.

3 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence is present, and the referenced rule.md adds a Verification section (automated and manual checks, re-crawl after deployment). Not 5 because the body itself has no explicit re-validate-after-fix checkpoint; the validation loop only appears in the reference. Not 3 because the sequence and checkpoints are mostly explicit and this is not a destructive/batch operation.

4 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview (under 50 lines) that delegates implementation details to a single one-level-deep reference, `references/rule.md` (verified to exist, no further nesting), clearly signaled with what it contains ("full implementation details, code examples, and framework-specific guidance"). Matches the top anchor: clear overview, well-signaled one-level reference, easy navigation.

5 / 5

Total

16

/

20

Passed

Description

58%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 has an explicit 'Use when' trigger and one concrete verification action, but it reads as template-generated: the skill title is jammed into the trigger clause as a noun phrase, and the broad SEO-audit boilerplate creates overlap risk with sibling rules. Rewriting it as a clean what+when pair with natural trigger phrases would lift it substantially.

Suggestions

Rewrite as a clean what+when pair, e.g.: "Audits pages for malformed HTML (unclosed or misnested tags) and fixes the markup. Use when the user mentions broken or invalid HTML, failed HTML validation, or crawlability/indexing problems caused by markup errors."

Replace the embedded title phrase 'related to Fix malformed HTML structure' with natural user trigger phrases such as 'broken HTML', 'unclosed tags', or 'HTML validation'.

Narrow the trigger clause to this rule specifically so it does not collide with sibling SEO skills that share the same 'auditing metadata, crawlability, structured data, or indexability' boilerplate.

DimensionReasoningScore

Specificity

One concrete action is stated ("Verify the rendered HTML and HTTP response rather than relying only on source files") and the domain areas are named ("auditing metadata, crawlability, structured data, or indexability"), but the capability statement is garbled by the embedded title phrase "related to Fix malformed HTML structure". Not 4 because it does not list several distinct specific actions; not 2 because it goes beyond minimal/generic naming.

3 / 5

Completeness

An explicit trigger clause is present ("Use when auditing metadata, crawlability, structured data, or indexability related to...") and the 'what' is stated via "Verify the rendered HTML and HTTP response" plus the fix-malformed-HTML intent. Not 5 because the 'what' is awkwardly constructed and not cleanly stated as a capability; better than 3 because the 'when' is explicit rather than missing or weakly implied.

4 / 5

Trigger Term Quality

"metadata", "crawlability", "structured data", "indexability", and "rendered HTML" are natural SEO-audit terms, but common variations for the core problem are missing ("broken HTML", "unclosed tags", "invalid HTML", "HTML validation"), and "related to Fix malformed HTML structure" is an embedded imperative title rather than a phrase a user would naturally say. Not 4 because keyword coverage has visible gaps; not 2 because several relevant natural keywords are present.

3 / 5

Distinctiveness Conflict Risk

"related to Fix malformed HTML structure" gives the skill a specific focus, but the broad shared trigger clause "auditing metadata, crawlability, structured data, or indexability" would fire for many sibling SEO-audit skills using the same boilerplate. Not 4 because the overlap risk within the SEO category is real; not 2 because the malformed-HTML anchor keeps it from being entirely broad.

3 / 5

Total

13

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/broken-html/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.