CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

form-labels

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

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/form-labels/SKILL.md
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 skill body: concrete check/fix guidance, an appropriately split one-level-deep reference to a real file containing the code examples, and clear sectioning. The main improvement opportunities are consolidating the placeholder-only/fieldset guidance repeated across four sections and adding a minimal correct-label markup example inline.

Suggestions

Consolidate the placeholder-only-label and fieldset/legend guidance, which currently repeats in Quick Reference, Check, Fix, and Code Review, into one authoritative section to tighten conciseness.

Add a minimal inline example of a correctly associated label (e.g. a two-line <label for="..."> snippet) so the fix guidance is fully copy-paste ready without opening the reference.

Merge or clearly differentiate the 'Check' and 'Code Review' sections, which currently overlap in purpose, to sharpen the review workflow.

DimensionReasoningScore

Conciseness

The ~35-line body is lean overall, but the intro line explains a concept Claude already knows ('Properly associated labels ensure that screen readers can identify the purpose of form inputs...') and the placeholder-only-label and fieldset/legend guidance is repeated across Quick Reference, Check, Fix, and Code Review. This matches anchor 4 (minor instances that could be trimmed) rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Concrete, specific guidance throughout ('Add a <label> element with a 'for' attribute that matches the 'id' of the corresponding input field', 'wrap related checkboxes or radio buttons in a <fieldset> with a <legend>'), with full code examples correctly deferred to references/rule.md, which exists and contains them. It sits at anchor 4 rather than 5 because the body itself carries no example markup of a correct pattern, leaving a minor gap the reference file has to fill.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence with verification guidance present ('note how to verify the fix with browser accessibility tooling or assistive tech') fits anchor 4. Not 5: the 'Check' and 'Code Review' sections overlap in purpose, which slightly muddles which section governs the review pass, and validation details are deferred to the reference.

4 / 5

Progressive Disclosure

A short, well-sectioned overview body with a clearly signaled one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that points to a real file with the promised examples, plus the source rule URL. Content is appropriately split between overview and detail, matching anchor 5.

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 description with an explicit 'Use when...' trigger and a concrete list of review actions. Its main weakness is the template-substituted rule title 'related to Associate labels with form controls' embedded mid-sentence, which reads unnaturally and slightly obscures both the what and the when, alongside missing common trigger synonyms like 'accessibility' or 'a11y'.

Suggestions

Rewrite the embedded rule title into a natural clause, e.g. 'Use when reviewing rendered HTML or interactive components for form-label accessibility (labels not programmatically associated with their inputs).' to state the what and when more explicitly.

Add natural trigger terms users would say, such as 'accessibility', 'a11y', 'form inputs', or 'WCAG', to improve trigger_term_quality coverage.

DimensionReasoningScore

Specificity

Lists several concrete inspection actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the core capability is conveyed through the awkwardly capitalized embedded rule title 'related to Associate labels with form controls' rather than a crisply stated what.

4 / 5

Completeness

Both 'what' ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') and 'when' ('Use when reviewing rendered HTML, interactive components, or design-system patterns...') are present, satisfying anchor 4. Not anchor 5 because the trigger clause is qualified by the stilted 'related to Associate labels with form controls' phrasing, making the 'when' less explicit and natural than the model example.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('rendered HTML', 'form controls', 'labels', 'keyboard', 'screen-reader', 'focus'), but common variations users would actually say are missing — 'accessibility', 'a11y', 'form inputs', 'WCAG' — so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The form-label/screen-reader niche is mostly distinct, but the broad mentions of 'keyboard behavior, focus flow' and 'design-system patterns' create minor overlap risk with sibling accessibility-review skills (focus order, keyboard navigation), fitting anchor 4 rather than the minimal-conflict anchor 5.

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/form-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.