CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-progressbar-name

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

Quality

80%

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

Quality

Content

77%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, simple skill body with excellent progressive disclosure (real, one-level-deep reference carrying the executable detail) and an unambiguous check-fix-verify flow. The drag is conciseness: the 'Explain' and templated 'Code Review' sections plus a known-concept intro sentence pad the body without adding guidance, and no code example appears inline.

Suggestions

Remove or merge the 'Explain' section and the templated 'Code Review' paragraph into 'Check'/'Fix' — they restate the Quick Reference without adding actionable guidance.

Cut the opening sentence explaining why screen reader users need accessible names; that is standard a11y knowledge, and the Quick Reference already carries the actionable rules.

Inline one minimal snippet (e.g., a div with role="progressbar" plus aria-label and aria-valuenow/min/max) so the body is self-sufficient for the common case, keeping the fuller examples in references/rule.md.

DimensionReasoningScore

Conciseness

Mostly efficient, but there is unnecessary material: the intro sentence explains why accessible names matter (a concept Claude already knows), and the 'Explain' section ('Explain why progress bars need accessible names...') plus the templated 'Code Review' paragraph add little beyond the Quick Reference and Check sections. Fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') better than 4's 'minor instances' — roughly four of seven sections carry redundancy or padding.

3 / 5

Actionability

Concrete, attribute-level guidance: 'Use `aria-label` or `aria-labelledby`', 'Provide `aria-valuenow`, `aria-valuemin`, and `aria-valuemax`', and a precise check ('all progress bar elements (role="progressbar") have an accessible name'). Not a 5 because the body itself contains no copy-paste-ready code — the executable HTML examples live only in references/rule.md, leaving a minor gap in the standalone body.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines, and the flow is unambiguous: Check (identify progressbars missing names) → Fix (add aria-label/aria-labelledby) → verify ('note how to verify the fix with browser accessibility tooling or assistive tech', with full verification steps in references/rule.md). Per the simple-skill scoring note, a clear, well-organized single-task body earns 5; there are no destructive or batch operations that would impose the validation cap.

5 / 5

Progressive Disclosure

The body is a lean overview and the implementation detail is cleanly delegated: 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — a well-signaled, one-level-deep reference that exists in the bundle and contains the code examples, standards, exceptions, and verification steps. No nested references, no monolithic inline detail.

5 / 5

Total

17

/

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 and a set of concrete inspection actions, well above the vague-template baseline. Its main weaknesses are the awkwardly embedded rule title and the omission of the fix-side actions (add aria-label/aria-labelledby) from the capability statement.

DimensionReasoningScore

Specificity

The description lists several concrete review actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — but stops short of comprehensive coverage (no mention of the fix actions like adding aria-label/aria-labelledby). Matches anchor 4 ('several specific actions; minor gaps in coverage'), not 3 (only 1-2 actions) and not 5 (no full coverage of check + fix).

4 / 5

Completeness

Both parts are explicit: 'Use when reviewing rendered HTML, interactive components, or design-system patterns related to...' (when) and 'Check native semantics first, then inspect keyboard behavior...' (what). Not a 5 because the rule title is inserted mid-sentence awkwardly ('related to Provide accessible names for progress bars') and the 'what' covers only inspection, leaving the fix/explain actions implied rather than stated.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'rendered HTML', 'interactive components', 'progress bars', 'accessible names', 'screen-reader output', 'keyboard'. A few natural terms a user would say are missing ('aria-label', 'aria', 'a11y', 'WCAG', 'accessibility audit'), matching anchor 4 rather than 5's comprehensive synonym/extension coverage, and clearly above anchor 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The niche (accessible names for progress bars) is distinct with clear triggers, but the boilerplate review language ('keyboard behavior, focus flow, accessible names, and screen-reader output') would read nearly identically across a family of sibling ARIA rule skills, creating minor overlap risk with closely related skills — anchor 4, not 5's 'minimal conflict risk'.

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-progressbar-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.