CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-tooltip-name

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

Quality

74%

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

Quality

Content

63%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, brief overview that uses progressive disclosure correctly: the body stays lean and points one level deep to a real references/rule.md holding the code examples and verification steps. Weaknesses are the near-verbatim duplication between Quick Reference and Check, and the Fix/Explain sections giving direction without any concrete inline example.

Suggestions

Merge the Quick Reference bullets into the Check section (or vice versa) — they currently restate the same three points almost verbatim and cost tokens twice.

Add a minimal inline fix example in the Fix section (e.g., `<button aria-describedby="tip-save">` paired with `<div id="tip-save" role="tooltip">`) or explicitly point to the Code Example in references/rule.md, so the fix path is concrete without leaving the body.

Either give the Explain section real substance (the mechanism by which aria-describedby is announced) or fold its purpose into the intro, since a single restating sentence adds no guidance.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the Quick Reference bullets ("Tooltips must have an accessible name or be referenced by `aria-describedby`", "Verify that tooltips are correctly associated with their trigger elements") duplicate the Check section almost verbatim, the intro sentence states tooltip basics Claude already knows, and the one-sentence Explain section adds no content. This "mostly efficient but could be tightened" pattern matches the 3 anchor better than the 4 anchor's "minor instances of over-explanation" — the duplication is a full redundant section.

3 / 5

Actionability

The Check section gives concrete criteria ("all elements with role=\"tooltip\" have an accessible name or are linked to a trigger element via aria-describedby"), but Fix ("Assign an accessible name to the tooltip or ensure it is correctly referenced") and Explain provide direction without any concrete markup or example — the executable code exists only in references/rule.md. As an instruction-only skill the guidance is actionable at the check level but incomplete on the fix path, matching the 3 anchor's "some concrete guidance but incomplete, missing key details".

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure presents a clear, unambiguous sequence for this simple review task, and verification is addressed ("note how to verify the fix with browser accessibility tooling or assistive tech"). It falls short of 5 because explicit verification steps (accessibility tree inspection, keyboard/screen-reader retest) are deferred entirely to references/rule.md rather than given even briefly in the body.

4 / 5

Progressive Disclosure

The body is a concise overview that appropriately pushes code examples, standards details, and verification procedures into references/rule.md via a single clearly signaled one-level-deep pointer ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"). The referenced file exists and delivers exactly what the pointer promises, matching the 5 anchor's clean overview-to-reference split.

5 / 5

Total

15

/

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 that explicitly answers both what the skill does and when to use it, with several concrete inspection actions and a clearly distinct accessibility niche. The main weakness is trigger phrasing: it leans on the rule title rather than natural synonyms users would say (ARIA, aria-describedby, tooltip labels).

Suggestions

Add natural trigger synonyms such as "ARIA", "aria-describedby", or "tooltip labels" to the 'when' clause so it matches what users actually say when they need this rule.

Replace the embedded rule title ("related to Provide accessible names for tooltips") with a fluent trigger phrase, e.g., "Use when reviewing tooltips, ARIA descriptions, or accessible names in rendered HTML".

DimensionReasoningScore

Specificity

The description lists several concrete inspection actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — with only minor gaps (no mention of fix or verification actions). It falls short of the 5 anchor because coverage is not comprehensive, but exceeds the 3 anchor's 1-2 concrete actions.

4 / 5

Completeness

Both parts are explicitly present: the 'when' via "Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for tooltips" and the 'what' via the concrete check/inspect actions. It is not a 5 because the 'when' clause embeds the rule title verbatim rather than natural trigger phrases (e.g., "when the user mentions tooltips, ARIA, or aria-describedby"), leaving the trigger guidance slightly less explicit than the anchor-5 example.

4 / 5

Trigger Term Quality

Good keyword coverage including "rendered HTML", "interactive components", "tooltips", "accessible names", "keyboard behavior", and "screen-reader output", which are natural phrases for this need. A few natural terms are missing — notably "ARIA", "aria-describedby", and "title attribute", which is what users working on this rule would most often say.

4 / 5

Distinctiveness Conflict Risk

The tooltip accessible-naming niche is clear and triggers are distinct for rendered HTML and interactive component review. There is minor overlap risk with closely related ARIA naming rules (e.g., button/label naming) and the broad "design-system patterns" phrase, which keeps it below a 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/aria-tooltip-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.