CtrlK
BlogDocsLog inGet started
Tessl Logo

modular-ds-accessibility-contract

Use when: determining which Primer React API type (config, presentational, base, or utility) should own a specific accessibility responsibility, or documenting that ownership for a new component. Covers a responsibility matrix mapping ARIA requirements to API types, worked examples for Dialog and Tabs, and how to build a matrix for a new ARIA pattern.

65

Quality

77%

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 ./.github/skills/modular-ds-accessibility-contract/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is a high-quality, executable guidance document: concrete code, specific APIs and paths, a clear multi-step process, and well-organized structure. It earns 4s across dimensions, held from 5 by minor repetition, a few deferred-to-other-skills mechanisms, and the absence of an explicit feedback-loop format.

Suggestions

Tighten the 'document the call' discussion — the same failure mode is restated three ways; consolidate to one crisp rule plus one example.

Show the callback-ref registration mechanism inline (or in a referenced file) rather than only pointing to modular-ds-utilities, so the aria-labelledby gating guidance is fully self-contained.

Add an explicit validate→fix→retry checkpoint for the matrix-building workflow (e.g., 're-read the APG optional-semantics list and confirm each has a recorded decision before committing').

DimensionReasoningScore

Conciseness

Dense and opinionated with no padding about concepts Claude already knows, though a few failure-mode points (e.g. 'document the call') are re-emphasized across multiple paragraphs and could be trimmed.

4 / 5

Actionability

Provides an executable useDevOnlyEffect/warning TSX snippet, concrete file paths, and specific APIs (getRootProps, getTitleProps, useFocusZone), with minor gaps where mechanisms are deferred to other skills rather than shown.

4 / 5

Workflow Clarity

The 'Applying this to other ARIA patterns' section gives a clear 5-step sequence with checkpoints (cover both paths in tests/stories/docs; commit the matrix as a deliverable), though it stops short of an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized into clear sections and tables with one-level cross-skill references signaled inline (modular-ds-spectrum-model, modular-ds-utilities, ADR-012); no bundle files exist to score against, and the inlined Dialog/Tabs matrices are appropriately the core deliverable.

4 / 5

Total

16

/

20

Passed

Description

80%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.

The description is strong: it explicitly states both what the skill does and when to use it, with a concrete trigger clause and a clearly distinct niche. Its weakest point is trigger-term quality, where it leans on domain jargon rather than natural user phrasing or synonyms.

Suggestions

Add natural-language synonyms a non-expert might say (e.g., 'ARIA roles', 'accessibility semantics', 'which layer handles a11y') to broaden trigger-term coverage.

Consider naming a couple more concrete actions (e.g., 'decide default-on vs opt-in for optional APG semantics') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — determining which API type owns a responsibility, documenting ownership, mapping ARIA requirements to API types, building a matrix — with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (responsibility matrix mapping ARIA requirements to API types with worked examples) and when (a concrete 'Use when:' clause naming the determining/documenting triggers).

5 / 5

Trigger Term Quality

Contains relevant domain keywords (accessibility responsibility, ARIA requirements, Dialog and Tabs, responsibility matrix) but lacks common synonyms and natural user-facing variations.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Primer React accessibility contract ownership across API abstraction types — with distinct triggers and minimal risk of firing for the wrong skill.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
primer/react
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.