CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-xml-lang-mismatch

Use when applies to XHTML documents and polyglot HTML documents that must parse correctly as both HTML5 and XML. For modern HTML5-only documents, only `lang` is needed and `xml:lang` is not required. Check when auditing documents served as application/xhtml+xml or documents that include both attributes.

Quality

79%

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/html-xml-lang-mismatch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, appropriately split rule skill with an unambiguous check/fix workflow and a correctly used one-level reference. The main weakness is redundancy — the identical-values rule and the HTML5-only-`lang` point are restated across four sections, and the Explain section teaches concepts Claude already knows.

Suggestions

Consolidate the repeated rule statements: state 'values must be identical, including subtags' once in Quick Reference and let Check/Fix reference it instead of restating it.

Trim the Explain section to the non-obvious part (why polyglot documents need both attributes) and drop the restatement of what `lang` and `xml:lang` do for HTML vs XML parsers.

Move the generic Code Review paragraph into references/rule.md (where verification tooling like axe/Lighthouse is already listed) or name the specific tools inline to remove the vague 'browser accessibility tooling' phrasing.

DimensionReasoningScore

Conciseness

The body is short and organized, but the core rule is repeated across the intro paragraph, Quick Reference, Check, Fix, and Explain sections (e.g., 'their values must be identical' appears in three places, and the HTML5-only-needs-`lang` point appears four times), and the Explain section restates well-known concepts ('The `lang` attribute on `<html>` serves this purpose for HTML parsers'). This fits anchor 3, 'mostly efficient but includes some unnecessary explanation or could be tightened' — above 2 because there is no padded tutorial-style filler, below 4 because the repetition and the known-concept explanation are more than minor.

3 / 5

Actionability

The Check and Fix sections give concrete, executable instruction: 'Inspect the `<html>` element for both `lang` and `xml:lang` attributes', 'including subtags — `en` vs `en-US` is a mismatch', and document-type-specific fixes ('remove `xml:lang`' for text/html, 'keep both and ensure they are identical' for XHTML/polyglot). It falls short of 5 because there are no inline code/markup examples (correct/incorrect `<html>` tags live only in references/rule.md) and the Code Review section is vague ('browser accessibility tooling or assistive tech' with no named tool); it is above 3 because the guidance is specific and covers the common cases.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines whose single action is unambiguous: the Check → Fix → Explain → Code Review sections cleanly sequence detect, correct, justify, and review, with the decision branches (HTML5 vs XHTML vs polyglot) each handled explicitly. Per the rubric's simple-skill exception the single action scores 5; no destructive/batch validation cap applies since this is an audit plus a one-attribute fix.

5 / 5

Progressive Disclosure

The body is a lean overview with clear section headers and a single, clearly signaled one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and that file exists in the bundle, holding exactly the deeper material (code examples, per-document-type table, standards links, verification steps). This matches anchor 5: clear overview, well-signaled reference, content appropriately split.

5 / 5

Total

17

/

20

Passed

Description

73%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 highly targeted, trigger-rich description with explicit 'when' guidance and strong distinctiveness, weakened by an only implied 'what' and a single concrete action. Adding one explicit statement of what the skill does (e.g., 'Verify `lang` and `xml:lang` values match and fix mismatches') would lift specificity and completeness.

Suggestions

State the core action explicitly, e.g. prepend 'Verify that `lang` and `xml:lang` on the `<html>` element have identical, valid BCP 47 values and fix mismatches' so the 'what' is as explicit as the 'when'.

Add one or two natural trigger phrases users would say, such as 'language mismatch' or 'language declaration', to round out keyword coverage.

Fix the awkward opening phrasing 'Use when applies to' — rewrite as 'Use when checking documents that must parse as both HTML and XML'.

DimensionReasoningScore

Specificity

The description names a very concrete domain ("XHTML documents and polyglot HTML documents that must parse correctly as both HTML5 and XML", "documents served as application/xhtml+xml") but lists only one action ("Check when auditing documents"), so it matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It does not reach 4 because it lists conditions and contexts rather than several specific actions (e.g., verify, fix, or remove the attributes), and it is above 2 because the domain and the single action are concrete, not generic.

3 / 5

Completeness

The 'when' is explicit and specific ("Use when applies to XHTML documents and polyglot HTML documents...", "Check when auditing documents served as application/xhtml+xml or documents that include both attributes"), and the 'what' is present but only inferred — the description states the lang/xml:lang requirement context ("only `lang` is needed and `xml:lang` is not required") without ever saying the skill verifies or fixes attribute mismatches. This matches anchor 4 ('when' explicit, 'what' present but could be more explicit); it is not 5 because the core action is never explicitly stated, and not 3 because both elements are more than weakly implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "XHTML documents", "polyglot HTML documents", "HTML5", "XML", "application/xhtml+xml", "lang" and "xml:lang" are the terms a developer or auditor would naturally use for this rule. It falls short of 5 because common phrasings like "language mismatch", "language declaration", or "screen reader language" are absent, and it exceeds 3 because the included terms are specific and varied rather than generic.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche with distinct triggers — XHTML/polyglot documents, the application/xhtml+xml MIME type, and dual lang/xml:lang attribute usage — making false triggers for unrelated skills (general accessibility, generic HTML linting) very unlikely. It clearly matches the anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 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/html-xml-lang-mismatch/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.