CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-meter-name

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

Quality

81%

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

85%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, lean single-purpose skill: the Check/Fix/Explain/Code Review sections give an unambiguous workflow with a verification pointer, and details are properly offloaded to a real, one-level-deep reference containing complete HTML examples. The only notable weakness is the Quick Reference section, whose bullets largely restate the Check and Fix sections and could be trimmed or merged.

DimensionReasoningScore

Conciseness

The body is lean and imperative: "Check for `<meter>` elements or elements with `role="meter"` that lack an accessible name" and "Add an `aria-label` or `aria-labelledby` to the meter element" with no teaching of concepts Claude already knows. Minor trimmable padding keeps it at 4 rather than 5: the three Quick Reference bullets largely duplicate the Check and Fix sections ("The `<meter>` element or `role="meter"` must have an accessible label" / "Use `aria-label` or `aria-labelledby` to provide context"), and "Helps users understand what measurement is being displayed" is fluffy.

4 / 5

Actionability

The guidance is concrete and specific for an instruction-only skill: exact elements (`<meter>`, `role="meter"`), exact fix attributes (`aria-label`, `aria-labelledby`), and verification direction ("verify the fix with browser accessibility tooling or assistive tech"), with full copy-paste HTML examples delegated to references/rule.md. It stops short of 5 because no inline example or specific tool/command (e.g., axe, browser accessibility tree) is given in SKILL.md itself, leaving minor gaps in executable detail.

4 / 5

Workflow Clarity

As a simple single-purpose skill, the sequence is unambiguous: Quick Reference (rule statement) → Check (find unlabeled meters) → Fix (add aria-label/aria-labelledby) → Explain → Code Review, with verification explicitly addressed ("note how to verify the fix with browser accessibility tooling or assistive tech"). No destructive or batch operations exist that would require validation checkpoints, so the simple-skill exception applies cleanly and the single workflow is fully unambiguous.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview (Check/Fix/Explain/Code Review) that appropriately defers "full implementation details, code examples, and framework-specific guidance" to `references/rule.md`, which exists, is one level deep, clearly signaled, and contains the code examples and verification steps it promises. Content is correctly split between the overview and the reference with easy navigation.

5 / 5

Total

18

/

20

Passed

Description

71%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 explicit "Use when" guidance, third-person voice, and several concrete inspection actions. Its main weaknesses are the awkward mid-sentence embedded rule title ("related to Provide accessible names for meter elements"), broad trigger conditions that overlap with other accessibility-rule skills, and missing natural synonyms like "ARIA" or "accessibility".

Suggestions

Rewrite the embedded rule title into natural prose, e.g., "Use when reviewing HTML that includes meter elements (or role=meter) that may lack accessible names, such as gauges for battery, storage, or password strength."

Narrow the broad triggers ("interactive components, or design-system patterns") to meter-specific contexts and add common synonyms like "ARIA", "aria-label", and "accessibility" to improve both distinctiveness and trigger-term coverage.

Lead with the skill's core capability (auditing meter elements for accessible names and prescribing aria-label/aria-labelledby fixes) before the general inspection checklist, so the what is stated as concretely as the when.

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 are specific and reviewable. It falls short of the 5 anchor because the awkward embedded title "related to Provide accessible names for meter elements" leaves the core capability (validating meter labeling) stated only indirectly, and it exceeds the 3 anchor by naming multiple concrete inspection actions rather than just 1-2.

4 / 5

Completeness

Both parts are present: the "what" is the inspection procedure ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and the "when" is explicit ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to..."). It sits at 4 rather than 5 because the when-clause is broad ("interactive components, or design-system patterns" would match many sibling accessibility rules) and the rule-specific trigger is weakened by the capitalized title pasted mid-sentence, making it less explicit and concrete than the 5 anchor's targeted trigger phrasing.

4 / 5

Trigger Term Quality

Good natural-term coverage: "rendered HTML", "meter elements", "accessible names", "keyboard behavior", "focus flow", "screen-reader output" are phrases a user reviewing accessibility would plausibly say. A few natural terms are missing (e.g., "ARIA", "aria-label", "accessibility review"), so it does not reach the comprehensive 5 anchor, but it is well above the generic-keyword coverage of anchors 2-3.

4 / 5

Distinctiveness Conflict Risk

The meter-specific framing is a distinct niche, but the trigger conditions "reviewing rendered HTML, interactive components, or design-system patterns" and the generic checklist sentence about native semantics, keyboard behavior, focus flow, and screen-reader output would apply equally to virtually any accessibility rule skill, creating real overlap risk with siblings. It is more specific than the 2 anchor's near-total genericity but does not achieve the mostly-distinct profile of 4, since only one clause actually distinguishes this skill.

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

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