New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Accessibility Review

by Asymmetric-al in Asymmetric-al/core

Audit and fix accessibility in Core UI. An agent skill from Asymmetric-al/core.

AGPL-3.0Auto-check passedFrontend & Design

Install Accessibility Review

skills CLI
$ npx skills add Asymmetric-al/core --skill accessibility-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Asymmetric-al/core accessibility-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Asymmetric-al/core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/accessibility-review .claude/skills/accessibility-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
accessibility-review
GitHub stars
381
Token cost
~1.1k tokens
SKILL.md length
503 words
Files
2 (incl. references)
Skills in repo
43
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Audit and fix accessibility in Core UI. An agent skill from Asymmetric-al/core.

  • Works in 5 steps: Read docs/ai/rules/frontend.md and… → Reuse @asym/ui Base UI primitives for… → Prefer native HTML semantics before… → …
  • Reviewing buttons
  • SKILL.md covers Authority and boundaries, Workflow, Core patterns and Verification, plus 2 more sections
  • Calls bun

What it does

Accessibility Review is an agent skill from Asymmetric-al/core. Audit and fix accessibility in Core UI. Use when changing or reviewing buttons, links, forms, validation, dialogs, menus, tabs, tables, keyboard interactions, focus management, accessible names, announcements, contrast, touch targets, reduced motion, or WCAG/a11y behavior.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/upstream.md`).

It sits in Frontend & Design, covering Accessibility. The repository describes itself as: A high-performance, enterprise-grade Next.js 16 application for mission-focused non-profit organizations. Built for high impact teams. The licence is AGPL-3.0.

When your agent uses it

  • Reviewing buttons
  • Keyboard interactions
  • Focus management
  • Accessible names

Example prompts

  • “/accessibility-review”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read docs/ai/rules/frontend.md and docs/ai/rules/testing.md first.
  2. Reuse @asym/ui Base UI primitives for dialogs, menus, tabs, tooltips,
  3. Prefer native HTML semantics before adding roles or ARIA. ARIA supplements
  4. Use docs/ai/skills/components-build/SKILL.md for component API work and
  5. Keep fixes scoped. Do not migrate UI libraries or refactor unrelated layout.

What it can do on your machine

Read from SKILL.md and the folder at commit 71b81fa. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Accessibility Review loads about 1.1k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 503 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Asymmetric-al/core at commit 71b81fa, republished under its AGPL-3.0 licence (© Asymmetric-al). 503 words, ~1,080 tokens.

Download SKILL.mdSave it as .claude/skills/accessibility-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
accessibility-review
description
Audit and fix accessibility in Core UI. Use when changing or reviewing buttons, links, forms, validation, dialogs, menus, tabs, tables, keyboard interactions, focus management, accessible names, announcements, contrast, touch targets, reduced motion, or WCAG/a11y behavior.

Accessibility review

Apply a focused accessibility pass without replacing Core's component system or mistaking automated checks for conformance.

Authority and boundaries

  1. Read docs/ai/rules/frontend.md and docs/ai/rules/testing.md first.
  2. Reuse @asym/ui Base UI primitives for dialogs, menus, tabs, tooltips, comboboxes, and other behavior-heavy widgets. Do not build ARIA replicas of behavior that a shared primitive already implements.
  3. Prefer native HTML semantics before adding roles or ARIA. ARIA supplements semantics; it does not repair incorrect interaction behavior.
  4. Use docs/ai/skills/components-build/SKILL.md for component API work and docs/ai/skills/emil-design-engineering/touch-accessibility.md for Core's touch and keyboard conventions.
  5. Keep fixes scoped. Do not migrate UI libraries or refactor unrelated layout.

Workflow

  1. Map the states. Identify the interactive controls, reading order, keyboard path, loading/empty/error states, responsive variants, and any content revealed only by hover or pointer input.
  2. Check semantics and names. Verify landmarks, headings, lists, table headers, labels, accessible names, descriptions, values, and state attributes.
  3. Exercise interaction. Use Tab and Shift+Tab, Enter/Space, arrow keys where the widget pattern requires them, and Escape for dismissible overlays. Check visible focus, initial focus, focus containment, and focus restoration.
  4. Check feedback. Associate helper and error text with fields, announce material async status changes, and ensure color, toast, or hover is never the only carrier of essential information.
  5. Check perception. Inspect contrast, zoom/reflow, touch targets, alt text, captions where applicable, and reduced-motion behavior. Preserve Core's global reduced-motion baseline instead of redeclaring it in an app.
  6. Verify proportionately. Run the focused automated suite, then perform the manual checks automation cannot prove. If asked only to review, report exact file:line evidence and concrete fixes without editing source.
Show full SKILL.md (234 more words)Show less

Core patterns

  • Give every interactive control an accessible name. Label icon-only buttons; keep decorative icons out of the accessibility tree.
  • Use real button, a, label, fieldset, legend, th, ul/ol, and heading elements when they express the behavior.
  • Connect field help and errors with stable IDs and aria-describedby; set aria-invalid only when the field is invalid.
  • Expose expanded, selected, checked, pressed, busy, and current state through the native element or the applicable ARIA state.
  • Keep DOM order aligned with visual and keyboard order. Never use positive tabIndex to repair a broken sequence.
  • Use Core's touch-target tokens and shared controls instead of shrinking the hit area to match the visible glyph.

Verification

bash
bun run test:a11y

For new or materially changed routes, update tests/e2e/accessibility.spec.ts. Use @axe-core/playwright for repeatable violations and Playwright role locators for behavior. An axe pass does not prove keyboard order, focus quality, usable labels, alt-text intent, or complete WCAG conformance, so keep the manual interaction pass.

Checklist

  • Native semantics or an established Base UI primitive owns behavior.
  • Names, descriptions, relationships, values, and states are exposed.
  • Keyboard operation, focus visibility, containment, and restoration work.
  • Forms expose instructions and errors without relying on color or toast.
  • Contrast, zoom/reflow, touch, media, and reduced motion were considered.
  • Relevant automated and manual checks ran; remaining limits are stated.
  • Findings cite exact files/lines, or fixes remain minimal and targeted.

Provenance

See references/upstream.md for the reviewed upstream source, license, Core adaptations, and refresh workflow.

© Asymmetric-al, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/accessibility-review of Asymmetric-al/core.

  • SKILL.md
  • references/upstream.md

Open the folder on GitHubat commit 71b81fa

Compare with similar skills

Accessibility Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Accessibility Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Accessibility Review this skillAsymmetric-al/core381—~1.1kAutomated safety check: PassAGPL-3.0
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.6k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed

  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed

  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed

  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.6k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed

  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed

  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.6k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from Asymmetric-al/core

All 43 skills in this repo

  • Idempotency Handling

    Asymmetric-al/core

    Implement idempotency keys and handling to ensure operations can be safely retried without duplicate effects.

    381 GitHub stars~867 tokensUpdated today
    Auto-check passed

  • Agent Email Inbox

    Asymmetric-al/core

    A skill your agent uses when building any system where email content triggers actions — AI agent inboxes, automated support handlers, email-to-task pipelines, or any workflow processing untrusted…

    381 GitHub stars~4.1k tokensUpdated today
    Auto-check: notes

  • Components Build

    Asymmetric-al/core

    Build modern, composable, and accessible React UI components following the components.build specification.

    381 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Create Agent

    Asymmetric-al/core

    Guides a one-question-at-a-time design interview, captures alignment in agent/EVE-BRIEF.md, then scaffolds and implements a runnable eve agent with verbose teaching comments.

    381 GitHub stars~2.6k tokensUpdated today
    Auto-check: notes

  • Emil Design Engineering

    Asymmetric-al/core

    Design engineering principles and patterns for building polished, accessible web interfaces.

    381 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Grill For Unknowns

    Asymmetric-al/core

    Use only when the user explicitly invokes grill-for-unknowns or asks for a map-vs-territory unknowns pass, blindspot discovery, unknown-known prototypes, or a subagent launch packet before…

    381 GitHub stars~4.6k tokensUpdated today
    Auto-check passed

Categories

Questions about Accessibility Review

What does Accessibility Review do?

Audit and fix accessibility in Core UI. An agent skill from Asymmetric-al/core. Accessibility Review is an agent skill from Asymmetric-al/core. Audit and fix accessibility in Core UI.

When should I use Accessibility Review?

Accessibility Review fits situations like: reviewing buttons; keyboard interactions; focus management; accessible names.

How do I install Accessibility Review in Claude Code?

Run `npx skills add Asymmetric-al/core --skill accessibility-review -a claude-code`. Or copy the skill folder (.agents/skills/accessibility-review in Asymmetric-al/core) into .claude/skills/accessibility-review in your project. Claude Code loads it when a task matches its description.

How do I install Accessibility Review in Codex?

Run `npx skills add Asymmetric-al/core --skill accessibility-review -a codex`. Or copy the skill folder (.agents/skills/accessibility-review in Asymmetric-al/core) into .agents/skills/accessibility-review in your project. Codex loads it when a task matches its description.

Can I use Accessibility Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Asymmetric-al/core --skill accessibility-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/accessibility-review, .gemini/skills/accessibility-review, .github/skills/accessibility-review and .opencode/skills/accessibility-review in your project.

What does Accessibility Review need to run?

Going by SKILL.md and its folder, Accessibility Review needs the command-line tools its instructions call (bun).

Does Accessibility Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Accessibility Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Accessibility Review use?

Accessibility Review is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Accessibility Review use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 328 tokens, read only when the agent opens those files.

What are the alternatives to Accessibility Review?

Skills that share tags, products or a category with Accessibility Review: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Accessibility Review?

Asymmetric-al (a GitHub organization) maintains it in Asymmetric-al/core, which has 381 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 11, 2026.

Source: Asymmetric-al/core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.