CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

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

86%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 skill body is a well-structured, token-efficient overview that offloads detail to a single clearly signaled reference file. Its main limitation is that executable markup examples live only in the reference, leaving the body's actionability slightly shy of copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — one orienting sentence plus tight bulleted guidance, with no padding explaining what buttons or screen readers fundamentally are.

5 / 5

Actionability

Gives concrete, specific directives with named attributes ('Use inner text, aria-label, or aria-labelledby', 'replace the button with a link'), but keeps executable markup examples in the reference file rather than inline.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear with implicit verification guidance, though there is no explicit validate→fix→retry feedback loop (not required here since the task is non-destructive).

4 / 5

Progressive Disclosure

The body is a clean overview with a single, clearly signaled one-level-deep reference to references/rule.md (verified to exist), with detailed examples and best practices appropriately split into that file.

5 / 5

Total

18

/

20

Passed

Description

67%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 what and when with several concrete actions, but its trigger terms lean technical and miss the natural phrasings a user would actually say. It is a solid, mostly distinct skill description with room for more natural keyword coverage.

Suggestions

Add natural user-facing trigger terms such as 'buttons', 'accessibility', 'a11y', 'button labels', and 'screen reader' so the skill matches how users actually phrase the need.

Tighten the 'when' clause to name the concrete trigger (e.g., 'Use when reviewing buttons that may lack visible or accessible labels') rather than the broad 'interactive components or design-system patterns'.

Narrow the domain scope from 'design-system patterns' to button-specific accessibility to reduce overlap with general accessibility skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), but coverage is not fully comprehensive enough for a 5.

4 / 5

Completeness

Has both an explicit 'Use when...' trigger and a clear 'what' (the list of checks to perform), though the when-clause could be more specific and concrete.

4 / 5

Trigger Term Quality

Includes relevant terms ('rendered HTML, interactive components, or design-system patterns') but misses common natural variations users would say such as 'buttons', 'accessibility', 'a11y', or 'labels'.

3 / 5

Distinctiveness Conflict Risk

The button-naming accessibility niche is mostly distinct, though broad phrasing like 'interactive components' and 'design-system patterns' creates minor overlap with related accessibility skills.

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.