CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

form-field-multiple-labels

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use a single label for each form field. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

70%

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/form-field-multiple-labels/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 well-structured, appropriately split overview that correctly pushes implementation detail to references/rule.md, but the executable core is too thin in the body itself: the Check and Fix sections give direction rather than instruction, with no detection method or code example inline, and the templated Code Review section spends tokens without adding rule-specific guidance.

Suggestions

Name a concrete detection method in the Check section, e.g. the axe rule id `form-field-multiple-labels` or a DOM query for inputs whose id is referenced by more than one `label[for]`.

Inline a minimal good/bad HTML pair in the Fix section (two labels on one input vs. a single label or aria-labelledby) instead of deferring all code to references/rule.md.

Trim or merge the 'Code Review' section, which restates the description's generic boilerplate and adds no rule-specific instruction beyond Check/Fix/Explain.

DimensionReasoningScore

Conciseness

The body is lean overall (no concept over-explanation), but the 'Code Review' section ('Review the rendered markup and interactive states that affect Use a single label for each form field. Flag exact elements, roles, labels, focus behavior...') is templated boilerplate duplicating the description, and 'Explain how a 1:1 relationship...' adds little rule-specific value. This fits 'mostly efficient but could be tightened' rather than 4's 'minor instances of over-explanation', since two of six sections are generic filler.

3 / 5

Actionability

'Search for form inputs that are associated with more than one <label> element' and 'Consolidate multiple labels into a single <label> or use aria-labelledby' give concrete direction, but the body provides no detection method (no selector, no axe rule id — those live only in references/rule.md) and no code example. Fits 'some concrete guidance but incomplete'; not 4 because a reviewer working from the body alone cannot execute the search.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear, but validation is only hand-waved ('note how to verify the fix with browser accessibility tooling or assistive tech') with no explicit checkpoint in the body — the concrete Verification steps are deferred to the reference. Fits 'steps listed but checkpoints missing or implicit'; not 4 because the validation checkpoint is not 'mostly present'.

3 / 5

Progressive Disclosure

A concise overview body with a single clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and references/rule.md exists and delivers exactly those details (code examples, best practices, verification steps). Matches the 'clear overview with well-signaled one-level-deep references' anchor; no organization gaps to justify 4.

5 / 5

Total

14

/

20

Passed

Description

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

The description explicitly answers both when to use the skill and what it does, listing several concrete review actions. But it reads as templated: the rule name is injected mid-sentence ('related to Use a single label for each form field'), the process language is generic accessibility boilerplate shared with sibling rule skills, and the natural trigger term 'accessibility' is absent.

Suggestions

Add the natural trigger terms 'accessibility' / 'a11y' (and 'form control') so users describing accessibility problems land on this skill.

State the skill's core action in the description — e.g. 'Identify form inputs associated with more than one <label> element and consolidate them or replace with aria-labelledby' — so the 'what' covers the fix, not just inspection.

Rewrite 'related to Use a single label for each form field' into fluent prose (e.g. 'related to single-label form fields') to remove the template artifact that also blurs distinctiveness from sibling accessibility rules.

DimensionReasoningScore

Specificity

'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' lists several concrete actions, matching 'several specific actions; minor gaps in coverage' — but coverage is one-sided (review/inspection only; the fix side, consolidating labels or using aria-labelledby, is absent from the description). Not 3 (more than 1-2 actions named) and not 5 (not comprehensive).

4 / 5

Completeness

Both halves are explicit: when ('Use when reviewing rendered HTML, interactive components, or design-system patterns related to...') and what ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant'). Falls short of 5 because the 'what' hedges with 'where relevant' and never states the core deliverable — flagging/fixing inputs with multiple labels — leaving a gap versus 'clearly and explicitly answers both'.

4 / 5

Trigger Term Quality

Natural terms users would say are present: 'label', 'form field', 'rendered HTML', 'keyboard behavior', 'screen-reader output'. However, the most natural umbrella terms — 'accessibility', 'a11y', 'form control', 'WCAG' — are missing, so keyword coverage is good but not comprehensive, fitting anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The embedded rule name 'Use a single label for each form field' names a specific niche, but the process text ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') is generic accessibility-review boilerplate that would equally match any sibling a11y rule skill, and nothing distinguishes this rule from closely related form-labeling skills. Fits 'somewhat specific but could still overlap with similar skills' better than 4's 'mostly distinct; minor overlap risk'.

3 / 5

Total

15

/

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/form-field-multiple-labels/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.