CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-text

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid focusable descendants in role='text' elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

82%

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

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 overview for a simple single-purpose rule: concrete check and fix guidance, a clear section sequence, and exemplary one-level-deep progressive disclosure to a real references/rule.md file. Its weaknesses are mild redundancy between the Quick Reference and opening paragraph and verification guidance that is mentioned rather than spelled out as explicit steps.

Suggestions

Drop or merge the 'Quick Reference' bullets that repeat the opening paragraph, since the rule is already stated once.

Add one explicit verification step, e.g. 'Re-check with the browser accessibility tree or an axe scan after fixing', instead of only mentioning tooling generically.

Inline one short markup example of the violation so the check is recognizable without opening the reference file.

DimensionReasoningScore

Conciseness

The body is efficient and free of concept over-explanation, but the 'Quick Reference' bullets ("Prevent accessibility 'black holes' where interactive items are hidden from screen readers") largely duplicate the opening paragraph, and the Fix and Explain sections overlap — minor padding that could be trimmed, keeping it below the lean anchor.

4 / 5

Actionability

Concrete, specific guidance is given — "Remove role='text' from containers that have interactive children or move the interactive elements outside" names the exact fix, and the Check section names the exact elements to look for. It falls below fully executable because no inline markup example of the violation is provided (examples are delegated to the reference file).

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear, unambiguous sequence for this simple skill, and the Code Review section directs noting "how to verify the fix with browser accessibility tooling or assistive tech". It falls short of the top anchor because verification is mentioned rather than given as explicit re-check steps.

4 / 5

Progressive Disclosure

The ~30-line body is a clean overview with well-organized sections and a single clearly signaled, one-level-deep pointer — "see references/rule.md" — to a real file that contains the code examples and verification detail without nesting further references, matching the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

78%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 strong description with an explicit 'Use when' trigger, multiple concrete inspection actions, and a highly distinctive niche around role='text' elements. Its main weaknesses are the missing natural synonyms (accessibility, ARIA, a11y) and a 'what' that describes process rather than stating the skill's deliverable, with the embedded capitalized rule title reading awkwardly.

Suggestions

State the skill's outcome explicitly, e.g. 'Flags and guides fixes for focusable descendants inside role="text" elements' before the inspection steps.

Add natural trigger synonyms users would say: 'accessibility review', 'ARIA', 'screen reader testing', 'a11y'.

Rewrite the embedded rule title as a natural phrase instead of the capitalized 'Avoid focusable descendants in role='text' elements' string.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — but never states what the skill produces (flagging/fixing role='text' violations), leaving a minor coverage gap that keeps it below the comprehensive anchor.

4 / 5

Completeness

Both what and when are present: "Check native semantics first, then inspect..." answers what, and "Use when reviewing rendered HTML, interactive components, or design-system patterns" answers when. It falls between anchors because the 'what' describes inspection steps rather than explicitly stating the skill's outcome (identifying and fixing role='text' violations).

4 / 5

Trigger Term Quality

Natural trigger phrases like "rendered HTML", "interactive components", "keyboard behavior", and "screen-reader output" are present, but common synonyms users would actually say — "accessibility", "ARIA", "a11y" — are missing, matching the 'good coverage with a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

"Avoid focusable descendants in role='text' elements" carves out a clear niche with distinct triggers; the specific ARIA role makes it unlikely to fire for the wrong skill, matching the 'clear niche with minimal conflict risk' anchor.

5 / 5

Total

17

/

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