CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

w3c-compliant

Use when reviewing templates, rendered HTML, or shared components related to Validate HTML against W3C standards. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

73%

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/w3c-compliant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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, well-sectioned overview that correctly delegates bulk code examples to references/rule.md, giving excellent progressive disclosure. However, the main body itself lacks executable commands, presents only an implicit workflow without a re-validate feedback loop, and carries some verbatim duplication between the Quick Reference and Fix sections.

Suggestions

Add an explicit step sequence with a feedback loop, e.g., '1. Validate at validator.w3.org 2. Fix errors first 3. Re-validate after each fix until no errors remain, then address warnings' — this would lift workflow_clarity.

Include at least one executable command directly in the body (e.g., `npx html-validate src/` or a CI snippet using html-validate) instead of only naming the tools, to make the guidance copy-paste ready.

Remove the verbatim duplication of the common-issues list ('unclosed tags, invalid nesting, missing attributes' appears in both Quick Reference and Fix) and trim the intro sentence explaining why invalid HTML is bad, which Claude already knows.

DimensionReasoningScore

Conciseness

Mostly efficient, but the common-issues list ("unclosed tags, invalid nesting, missing attributes") is duplicated verbatim in Quick Reference and Fix, and the intro sentence and "Explain" section restate concepts Claude already knows — matching level 3's "some unnecessary explanation or could be tightened" rather than level 4's "minor instances".

3 / 5

Actionability

Concrete tool names appear ("validator.w3.org", "html-validate") and "Fix errors first, then warnings" plus "Flag exact elements, attributes, and routes" are specific, but the body contains no executable command or code example — fitting level 3's "some concrete guidance but incomplete" rather than level 4's "concrete code or commands".

3 / 5

Workflow Clarity

A rough validate-then-fix sequence exists but is implicit across bullets and section headers, with no re-validation feedback loop (e.g., "re-run the validator after each fix"), matching level 3's "sequence present but checkpoints missing or implicit" rather than level 4's "most checkpoints present".

3 / 5

Progressive Disclosure

A clear, well-organized short overview with a well-signaled one-level-deep reference ("see `references/rule.md`"), and the bundle confirms references/rule.md exists with the full code examples, matching the level-5 anchor exactly.

5 / 5

Total

14

/

20

Passed

Description

78%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 description: it explicitly states both what the skill does and when to use it, with concrete trigger phrases like 'templates', 'rendered HTML', and 'shared components'. Its main limitation is that it describes one core validation action rather than multiple distinct capabilities, and a few natural synonyms (e.g., 'HTML validator', '.html') are absent.

DimensionReasoningScore

Specificity

Names the domain ("W3C standards", "HTML") and 1-2 concrete actions ("Validate the final browser-facing markup", "reviewing templates, rendered HTML, or shared components"), but this is essentially one core action with scoping clarifications rather than the several specific actions of the level-4 anchor.

3 / 5

Completeness

Explicitly answers both what ("Validate the final browser-facing markup, not just the source framework abstraction") and when ("Use when reviewing templates, rendered HTML, or shared components") with concrete trigger phrases, matching the level-5 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("templates", "rendered HTML", "shared components", "W3C", "validate", "markup") but a few common user phrases are missing ("HTML validator", "lint", ".html"), so it falls short of the comprehensive level-5 anchor while clearly exceeding level 3.

4 / 5

Distinctiveness Conflict Risk

The W3C HTML validation niche is mostly distinct with clear triggers, but there is minor overlap risk with closely related frontend-quality skills (linting, accessibility checks), keeping it below the level-5 'minimal conflict risk' anchor.

4 / 5

Total

16

/

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/w3c-compliant/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.