CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

button-name

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

Quality

77%

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

Quality

Content

71%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 well-structured, short skill body that defers code examples to a real, one-level-deep reference file with clear signposting. The main weaknesses are mild redundancy across the Quick Reference, Fix, and Code Review sections and a rationale sentence that re-explains basic accessibility knowledge.

Suggestions

Remove the opening rationale sentence ('Buttons without accessible names are announced as button by screen readers...') — Claude already knows this; the Quick Reference bullets already imply the rule.

Deduplicate the label guidance: state 'inner text, aria-label, or aria-labelledby' once in Fix and drop the overlapping Quick Reference bullet, and merge the buttons-vs-links advice into a single place.

Make verification concrete in the Code Review section by naming an actual check (e.g. inspect the accessible name in devtools accessibility tree or a screen reader) instead of the generic 'browser accessibility tooling or assistive tech'.

DimensionReasoningScore

Conciseness

The body is short and sectioned, but includes unnecessary explanation Claude already knows ('Buttons without accessible names are announced as button by screen readers...') and duplicated guidance across Quick Reference, Fix, and Code Review (e.g. 'inner text, aria-label, or aria-labelledby' appears twice, and 'Use buttons for actions... not page navigation' repeats the Fix advice). It could be tightened into a leaner check/fix/verify structure, so it sits below the 'minor trim' bar of a 4 and above the 'noticeably padded' level of a 2.

3 / 5

Actionability

The Fix section gives concrete, executable instruction ('using text content, an aria-label, or an aria-labelledby reference. If the element navigates to another URL, replace the button with a link') and executable good/bad markup examples live in references/rule.md, which is appropriately signposted. It is not a 5 because verification is described generically ('browser accessibility tooling or assistive tech') without naming a concrete check, and no inline snippet covers the common cases.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent review sequence for a simple single-purpose skill, with a clear 'how to verify the fix' cue in the Code Review section. It is not a 5 because the sequence is implicit in section ordering rather than explicit steps, and the Code Review section partially restates earlier guidance without adding a distinct checkpoint; it is above a 3 since the single action is unambiguous and no destructive/batch cap applies.

4 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — the file exists, contains the code examples and guidance promised, and does not chain to further files. Content is appropriately split with easy navigation, matching the top anchor.

5 / 5

Total

16

/

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, concrete review actions, and distinctive accessibility vocabulary. Its main weaknesses are the awkward embedded rule title in the trigger clause and missing common synonyms like 'aria-label' or 'a11y' that users would naturally say.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — which map to a clear review procedure. It falls short of a 5 because the opening clause 'reviewing rendered HTML, interactive components, or design-system patterns related to...' is broad and leaves minor gaps in coverage of what the skill actually does, and it is above a 3 since more than 1-2 specific actions are named.

4 / 5

Completeness

Both parts are explicitly present: an explicit trigger ('Use when reviewing rendered HTML, interactive components, or design-system patterns...') and a clear what ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'). It is not a 5 because the trigger clause awkwardly embeds the rule title ('related to Provide accessible names for buttons') and could be stated more naturally and specifically; it is above a 3 because both what and when are explicit.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms a user would say: 'rendered HTML', 'interactive components', 'buttons', 'accessible names', 'keyboard behavior', 'screen-reader'. A few natural variations are missing (e.g. 'aria-label', 'button label', 'a11y'), so it is not a 5, but it clearly exceeds the 'some relevant keywords' level of a 3.

4 / 5

Distinctiveness Conflict Risk

The button-accessible-name niche is well carved out with domain-specific triggers ('accessible names', 'native semantics', 'screen-reader output'). Minor overlap risk remains with sibling frontendchecklist accessibility rules (e.g. link names, form labels) and general accessibility-review skills, so it is mostly distinct rather than a clear niche with minimal conflict.

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