CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-toggle-field-name

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

Quality

73%

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/aria-toggle-field-name/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 compact, well-structured overview with excellent progressive disclosure to an existing references/rule.md. Its weaknesses are instructional concreteness — no markup examples or named verification tooling — and a vaguely specified verification step, plus one redundant rationale sentence and overlap between the Check and Code Review sections.

Suggestions

Add a minimal good/bad HTML pair (e.g., unlabeled `<input type="checkbox">` vs. one wrapped in `<label>` or using `aria-label`) so the guidance is executable rather than descriptive.

Name concrete verification tooling in the Fix/Code Review sections, e.g. "verify with axe-core or the browser DevTools accessibility pane showing the accessible name".

Trim the opening rationale sentence and merge the overlapping "Check" and "Code Review" sections to remove redundancy.

DimensionReasoningScore

Conciseness

The body is short, well-sectioned, and lean, with one instance of over-explanation: the opening rationale "Toggle fields like checkboxes and switches are unusable for screen reader users if they don't have a label" restates a concept Claude already knows. Everything else earns its place.

4 / 5

Actionability

"Use `aria-label`, `aria-labelledby`, or `<label>` for checkboxes and radios" is concrete technique guidance, but the body contains no HTML examples of good vs. bad markup and no specific verification commands (e.g., axe, DevTools accessibility pane) — guidance names the right tools but not the executable details.

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review provides a rough sequence for this simple skill, but validation is only implicit: "note how to verify the fix with browser accessibility tooling" gestures at verification without naming a tool or concrete checkpoint. There is some redundancy between the "Check" and "Code Review" sections.

3 / 5

Progressive Disclosure

The ~30-line body is well-organized into clear sections and points to a single, clearly signaled, one-level-deep reference ("see `references/rule.md`", which exists on disk) for implementation details and examples — matching the simple-skill pattern exactly.

5 / 5

Total

15

/

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.

A solid description with an explicit "Use when" clause and multiple concrete inspection actions, held back by an awkward embedded rule title and missing natural synonyms for the toggle field types (checkbox, radio, switch, ARIA). Trigger phrasing overlaps with sibling accessibility skills sharing the same boilerplate.

Suggestions

Rewrite the trigger clause to read naturally, e.g. "Use when reviewing rendered HTML or design-system components containing checkboxes, radio buttons, or switches that may lack accessible names."

Add the concrete toggle-type synonyms (checkbox, radio button, switch, ARIA, screen reader) to the description so users' natural phrasing matches the trigger.

Replace the capitalized rule-title fragment "related to Provide accessible names for toggle fields" with plain descriptive language.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — giving specific inspection steps. It falls short of comprehensive because the awkward "related to Provide accessible names for toggle fields" phrasing muddies the capability statement, but it is well above naming only 1-2 actions.

4 / 5

Completeness

Both parts are explicit: 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..."). The when-clause could be clearer — the embedded capitalized rule title reads unnaturally and weakens the trigger phrasing.

4 / 5

Trigger Term Quality

Natural trigger terms are present: "rendered HTML", "interactive components", "accessible names", "screen-reader output", "keyboard behavior". Common synonyms a user would actually say — "checkbox", "radio button", "switch", "ARIA", "a11y" — are absent, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The rule topic (accessible names for toggle fields) is distinct, but the trigger boilerplate "reviewing rendered HTML, interactive components, or design-system patterns" is generic and would be shared by sibling frontend-checklist accessibility skills, creating real overlap risk at trigger time.

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/aria-toggle-field-name/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.