CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

custom-element-accessibility

Use when reviewing custom element class definitions or Web Component source code to check for missing ARIA reflection, keyboard handling, and form association.

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

71%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 overview with a clean one-level reference split and concrete, API-specific guidance. The main weakness is redundancy: the shadow-DOM/ARIA point and the review checklist are each repeated across sections, and there is no post-fix verification step.

Suggestions

Deduplicate the 'shadow DOM does not automatically expose ARIA' explanation — it appears in the intro, Quick Reference bullet 5, and the 'Explain' section; stating it once is enough.

Merge or clearly differentiate the 'Check' and 'Code Review' sections, which currently list nearly the same set of things to inspect.

Add an explicit post-fix verification step (e.g., confirm the element announces the correct role/label with ElementInternals set, and re-check keyboard interaction with Tab/Enter/Space/Arrow keys).

DimensionReasoningScore

Conciseness

Mostly efficient, but the same key fact ('the shadow DOM does not automatically expose ARIA without ElementInternals') is stated three times — intro, Quick Reference bullet 5, and the 'Explain' section — and 'Check' and 'Code Review' cover nearly identical ground, matching anchor 3 (could be tightened) rather than 4 (only minor trims).

3 / 5

Actionability

Concrete instruction-style guidance naming exact APIs ('ElementInternals', 'ariaRole and ariaLabel reflection', 'formAssociated', 'roving tabindex') with a specific check list and explicit ordering ('First verify that the widget truly needs to be custom'); inline code is absent but deliberately deferred to a well-signaled reference containing full executable TypeScript, fitting anchor 4 rather than the copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Clear thematic sequence (Check → Fix → Explain → Code Review) with a decision checkpoint up front ('First verify that the widget truly needs to be custom rather than a native control with styling') and conditional guidance ('Replace the component with native HTML when...'), but no explicit post-fix verification step, so it lands on anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A concise ~45-line overview with well-organized sections and a clearly signaled one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which was verified to exist and contain the full implementation details, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

87%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 and specific 'Use when' trigger clause and concrete named checks. Its only weakness is missing natural synonyms like 'accessibility'/'a11y' that a user might say when requesting this skill.

DimensionReasoningScore

Specificity

Names the domain precisely ('custom element class definitions', 'Web Component source code') and lists several specific checks ('missing ARIA reflection, keyboard handling, and form association'), but centers on a single review verb rather than multiple comprehensive actions, matching anchor 4 instead of 5.

4 / 5

Completeness

Explicitly answers both what ('check for missing ARIA reflection, keyboard handling, and form association') and when ('Use when reviewing custom element class definitions or Web Component source code') with concrete trigger phrases, exceeding anchor 4 where the when is only weakly specified.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('custom element', 'Web Component', 'ARIA', 'keyboard handling', 'form association'), but misses common synonyms such as 'accessibility', 'a11y', 'screen reader', and 'shadow DOM' that users would naturally say, so it does not reach the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (custom elements / Web Components accessibility) with distinct, specific triggers; minimal risk of firing for unrelated skills.

5 / 5

Total

18

/

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/custom-element-accessibility/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.