CtrlK
BlogDocsLog inGet started
Tessl Logo

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`.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An actionable, well-organized body with clear sequencing and a properly signaled one-level reference. The main improvement is trimming concept re-explanation in the Explain and Quick Reference sections that Claude already knows.

Suggestions

Tighten the 'Explain' section: drop the primer on what BCP 47 subtags and WCAG levels are, keeping only the normative requirement and any non-obvious detail.

Remove overlap between the intro paragraph and the Quick Reference bullets so each section earns its tokens.

DimensionReasoningScore

Conciseness

Structured and mostly tight, but the 'Explain' section re-states WCAG SC numbers and what BCP 47 subtags are and the Quick Reference repeats the intro — concepts Claude already knows that could be trimmed.

2 / 3

Actionability

Gives concrete check criteria (present / non-empty / valid BCP 47 matching content, with an explicit flag list) and copy-paste-ready fixes such as `<html lang='fr'>` and `zh-Hant`, providing fully actionable guidance.

3 / 3

Workflow Clarity

A simple single-purpose inspection skill with a clearly sequenced Check (1/2/3) and Fix step; no destructive or batch operation requires a validate-feedback loop, so the simple-skill allowance applies.

3 / 3

Progressive Disclosure

Well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signaled one-level-deep pointer to a real references/rule.md file.

3 / 3

Total

11

/

12

Passed

Description

85%

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 specific, well-scoped description with explicit what-and-when guidance and low conflict risk. Its main weakness is the awkward, jargon-leaning trigger phrasing and missing common user variations like 'language tag'.

Suggestions

Rewrite the trigger as natural user speech, e.g. 'Use when reviewing HTML accessibility or when the user mentions the lang attribute, language tag, or page language.'

Add common natural variations alongside 'BCP 47 language code' (e.g. 'language tag', 'language code', 'HTML lang') so the trigger matches how users actually phrase the request.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Check the `<html>` opening tag for a `lang` attribute with a non-empty, valid BCP 47 language code' and 'check for `lang` attribute changes on individual elements'), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (check html lang, check lang changes) and when via an explicit 'Use when...' trigger clause, so it clears the cap that applies only when trigger guidance is missing.

3 / 3

Trigger Term Quality

Includes the natural term 'lang attribute' and 'HTML documents', but leans on jargon ('BCP 47 language code') and the opening 'Use when applies to all HTML documents' is not natural user speech, missing common variations like 'language tag' or 'page language'.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (the HTML `lang` attribute / page language) with distinct, specific triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.