CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

label-content-name-mismatch

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Align visible labels with accessible names. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

84%

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

78%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 tight, well-structured body for a simple single-purpose rule: it gives concrete check and fix instructions, a sensible section sequence, and a clean one-level pointer to references/rule.md for examples. The main improvements are removing the redundant Quick Reference rationale bullets, widening the Check section beyond buttons/links, and adding one concrete verification step (e.g., inspect the browser accessibility tree).

Suggestions

Trim the redundant Quick Reference bullets that restate the intro's voice-control rationale (e.g., 'Ensure speech-to-text users can trigger controls by their visible name') to reduce token cost without losing information.

Widen the Check section beyond 'buttons and links' to cover all interactive controls (e.g., form inputs, custom widgets), and note that an aria-labelledby mismatch is fixed by editing the referenced element's text rather than the attribute itself.

Add one concrete verification step to the Fix section — e.g., inspect the element's accessible name in the browser accessibility tree or run axe — so the workflow has an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) and assumes Claude's competence, but the intro sentence and the Quick Reference bullet 'Ensure speech-to-text users can trigger controls by their visible name' restate the same voice-control rationale, and 'Maintain consistency between what is seen and what is read by tech' is padded phrasing — minor over-explanation that could be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

'Check' and 'Fix' give concrete, executable guidance ('Compare the visible text of buttons and links with their aria-label or aria-labelledby attributes', 'Update the ARIA attribute to include the exact string of the visible label text at the beginning'). Minor gaps remain: 'Check' covers only buttons and links (not form inputs), and the fix is imprecise for aria-labelledby (the fix targets the referenced element, not the attribute itself), so it does not reach fully-copy-paste-ready anchor 5. No code is inlined, but per the rubric's scoring note this instruction-only skill is not penalized for that since the guidance is actionable and examples live in references/rule.md.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear, coherent sequence, and the Code Review section signals verification ('note how to verify the fix with browser accessibility tooling or assistive tech'). It falls short of anchor 5 because verification is only gestured at with no concrete checkpoint (e.g., inspect the accessibility tree or run axe), and the Code Review section partially duplicates the Check section. This is not a destructive or batch operation, so no cap applies.

4 / 5

Progressive Disclosure

The short body is well-organized into clear sections and correctly delegates implementation details, code examples, and framework guidance to references/rule.md — a real bundle file, one level deep, clearly signaled ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'). This matches the anchor-5 pattern of a clear overview with a well-signaled one-level-deep reference.

5 / 5

Total

17

/

20

Passed

Description

83%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 uses third person, opens with an explicit 'Use when...' trigger clause naming concrete surfaces (rendered HTML, interactive components, design-system patterns), and enumerates concrete inspection actions. Weaknesses are minor — a few natural trigger synonyms are absent and the action list is generic across accessibility rules, creating slight overlap risk with sibling a11y skills.

DimensionReasoningScore

Specificity

The description lists several concrete review actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — which is more than 1-2 actions but the actions are generic accessibility-review steps rather than a comprehensive set specific to this rule (e.g., no mention of aria-label comparison or visible-label matching), matching anchor 4 rather than 5.

4 / 5

Completeness

It explicitly answers both: 'what' is concrete ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant') and 'when' is explicit with concrete trigger phrases ('Use when reviewing rendered HTML, interactive components, or design-system patterns related to...'). The 'when' clause is explicit and specific, so it does not fit anchor 4's caveat that 'when' could be more explicit.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'rendered HTML, interactive components, design-system patterns', 'accessible names', 'keyboard behavior', 'focus flow', 'screen-reader output'. A few natural terms a user might say are missing (e.g., 'aria-label', 'voice control', 'label in name'), so it fits anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The rule name 'Align visible labels with accessible names' carves a clear niche, but the check actions (keyboard behavior, focus flow, screen-reader output) overlap with sibling accessibility-rule skills that share the same generic review steps — minor overlap risk with closely related skills, matching anchor 4 rather than the minimal-conflict profile of anchor 5.

4 / 5

Total

17

/

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/label-content-name-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.