CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lang-attribute

Use when applies to all HTML documents. Check the `<html>` opening tag for a `lang` attribute with a non-empty, valid BCP 47 language code. Also check for `lang` attribute changes on individual elements when the document contains content in multiple languages (inline quotes, foreign terms, multilingual sections). The `lang` attribute is inherited — child elements inherit the language from their nearest ancestor with `lang`.

Quality

80%

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/lang-attribute/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.

The body is a well-structured, actionable checklist: concrete verification steps, explicit flag conditions, exact fix values, and a clean one-level reference to real code examples. Its weakness is redundancy — the rationale for the lang attribute is repeated across the intro, Quick Reference, and Explain sections, and the Code Review section is generic filler.

Suggestions

State the why-it-matters rationale once (in the intro or Quick Reference) and drop the duplication in Quick Reference bullet 4 and the Explain section, which restates the WCAG citations already given in bullets 1 and 3.

Replace the generic Code Review boilerplate with concrete guidance (e.g., grep-able patterns or where lang is typically set in common frameworks — a base template, _document/app.html, or a layout component).

Since references/rule.md already carries the WCAG explanation and code examples, keep the body's Explain section to only the rule-specific thresholds not covered elsewhere.

DimensionReasoningScore

Conciseness

The why-it-matters material is stated three times: the intro paragraph on screen readers/translation/hyphenation/spell checking, Quick Reference bullet 4 ('The `lang` attribute affects screen reader pronunciation, spell checking, hyphenation, and browser translation'), and the Explain section restating the WCAG SC 3.1.1/3.1.2 citations already given in Quick Reference bullets 1 and 3. Concepts like what `lang` does are ones Claude already knows, so the body could be tightened — matching anchor 3 (mostly efficient but includes unnecessary explanation) rather than anchor 4's 'minor instances'.

3 / 5

Actionability

The Check section is concretely executable (numbered verifications, explicit flag conditions like "lang='english' is invalid") and the Fix section gives copy-paste-ready values for common languages plus IANA registry validation, but the Code Review section is generic boilerplate ('Review templates, server-rendered HTML, and shared components that output markup related to Set the page lang attribute') with no concrete pointers — matching anchor 4 (mostly executable, minor gaps).

4 / 5

Workflow Clarity

This is a simple single-purpose skill where the action is unambiguous: numbered verification steps, explicit flag conditions, and an exact remedy, with code examples correctly deferred to references/rule.md. Per the rubric's simple-skill exception this scores 5; no destructive or batch operations exist to require a validation cap.

5 / 5

Progressive Disclosure

Well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) with 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 with the promised code examples — matching anchor 5 (clear overview, well-signaled one-level-deep references, easy navigation).

5 / 5

Total

17

/

20

Passed

Description

75%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 solid, specific description with two well-defined check actions and decent natural keywords. Its main weaknesses are the garbled and overly broad 'Use when applies to all HTML documents' trigger clause and the absence of the accessibility/WCAG vocabulary users would most naturally use.

Suggestions

Fix the broken trigger clause, e.g. 'Use when reviewing or writing HTML documents, checking accessibility (a11y) compliance, or auditing WCAG language requirements' — this both repairs the grammar and adds natural trigger terms.

Add the natural synonyms users actually say — 'accessibility', 'screen reader', 'WCAG', 'language code' — to improve trigger term coverage.

Mention the mismatch check (declared language vs actual content language) to round out the action coverage.

DimensionReasoningScore

Specificity

Two concrete, well-parameterized check actions are stated ('Check the `<html>` opening tag for a `lang` attribute with a non-empty, valid BCP 47 language code', 'check for `lang` attribute changes on individual elements when the document contains content in multiple languages'), matching anchor 4 with minor gaps: it omits declared-vs-actual content language mismatch flagging and any fix guidance that the body covers.

4 / 5

Completeness

Both what (the two check actions) and when are present via an explicit 'Use when' clause, but the trigger is grammatically broken ('Use when applies to all HTML documents' lacks a subject) and maximally broad, matching anchor 4 ('when' could be more explicit or specific) rather than the concrete-trigger anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('HTML documents', 'lang attribute', 'multiple languages', 'foreign terms', 'multilingual sections', 'inline quotes'), but common variations users would say — 'accessibility', 'screen reader', 'WCAG', 'i18n' — are absent, so it fits anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (lang attribute / BCP 47 validation) with specific terminology, but the 'applies to all HTML documents' scope means it co-triggers with every sibling HTML/accessibility rule, matching anchor 4 (mostly distinct, minor overlap risk with closely related skills).

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/lang-attribute/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.