CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/aria-authoring-patterns

Use when building or reviewing a custom interactive widget with no native HTML equivalent (combobox, dialog, menu, tabs, tree and more). Gives the W3C ARIA Authoring Practices pattern: required roles and states, keyboard interaction and common violations.

Quality

79%

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

Overview
Quality
Evals
Security
Files

Quality

Content

67%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-organized, largely actionable reference with concrete code for the most common patterns and excellent failure/anti-pattern tables. Its main weaknesses are redundant catalog one-liners that restate common knowledge and per-pattern coverage that stops at four patterns despite the skill's stated scope.

Suggestions

Trim the 31-pattern catalog to the patterns that genuinely need guidance (those with no native equivalent or non-obvious rules), replacing entries like Breadcrumb, Landmarks, and Table with a one-line pointer to the APG site.

Add per-pattern essentials (required roles and keyboard model) for Menu, Tree View, and Listbox, or move all per-pattern detail into a references/ file and keep only the decision guidance in SKILL.md.

State an explicit ordered procedure for the reviewing use case (e.g., check native-first violations, then role/state completeness, then keyboard model, then the failures and anti-patterns tables).

DimensionReasoningScore

Conciseness

The per-pattern essentials, ARIA states table, and failure/fix tables are high-signal, but sizable stretches restate what Claude already knows: one-liners like "Breadcrumb: Hierarchical-location indicator", "Table: Tabular data (use `<table>`)", "Landmarks: Navigation regions", and a ~30-line 'first rule' section on native-vs-custom preferences. This is more than minor over-explanation (not 4) but the bulk is dense reference material (not 2).

3 / 5

Actionability

Copy-paste-ready HTML for Combobox, Tabs, Disclosure, and Tooltip, each paired with required-ARIA and keyboard-behavior tables, plus concrete failure-to-fix and anti-pattern tables. It is not 5 because only 4 of the 31 cataloged patterns receive essentials — menu, tree, listbox, and treegrid keyboard models are absent despite the skill promising keyboard interaction per pattern.

4 / 5

Workflow Clarity

A clear implicit decision flow runs through the sections: prefer native HTML (first-rule table), match the APG pattern exactly when custom is required, then audit against the failures and anti-patterns tables. It is not 5 because no explicit procedure is stated for the advertised 'reviewing' use case (e.g., an ordered audit checklist), though as a reference skill it has no risky multi-step operation requiring validation checkpoints.

4 / 5

Progressive Disclosure

The single file is well-sectioned (Overview, When to use, pattern catalog, per-pattern essentials, states reference, failures, References), and external references (APG site, WAI-ARIA 1.2, sibling skills) are clearly listed and one level deep. It is not 5 because at ~240 lines the full 31-pattern catalog is content that could be split into reference files, though navigation remains easy.

4 / 5

Total

15

/

20

Passed

Description

83%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' clause, concrete trigger widgets, and a clear statement of what it provides. Its only weaknesses are a few missing natural synonyms (accessibility, a11y, screen reader) and minor overlap risk with sibling keyboard-navigation skills.

DimensionReasoningScore

Specificity

"Gives the W3C ARIA Authoring Practices pattern: required roles and states, keyboard interaction and common violations" lists several concrete deliverables, and "building or reviewing" names two user actions. It is not 5 because the 'what' omits capabilities the body actually covers (native-vs-custom decision guidance, DOM structure conventions), leaving minor gaps in coverage.

4 / 5

Completeness

Both halves are explicit: "Use when building or reviewing a custom interactive widget with no native HTML equivalent (combobox, dialog, menu, tabs, tree and more)" gives concrete when-triggers, and the second sentence states the what ("required roles and states, keyboard interaction and common violations"). This matches the 5 anchor; it is not 4 because the 'when' is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

"combobox, dialog, menu, tabs, tree", "ARIA", and "custom interactive widget" are phrases users naturally say when needing this skill. It falls short of 5 because common synonyms like "accessible", "accessibility", "a11y", and "screen reader" are missing.

4 / 5

Distinctiveness Conflict Risk

"custom interactive widget with no native HTML equivalent" carves a clear niche distinct from generic skills. It is not 5 because "keyboard interaction" content overlaps with the closely related wcag-keyboard-navigation skill the body itself references, leaving minor conflict risk.

4 / 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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page