Document accessibility decisions and tradeoffs for a feature.

MITAuto-check passedFrontend & Design

Install Document

skills CLI
$ npx skills add Owl-Listener/inclusive-design-skills --skill document -a claude-code

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

GitHub CLI
$ gh skill install Owl-Listener/inclusive-design-skills document --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/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/accessibility-decisions/skills/document .claude/skills/document && 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
document
GitHub stars
103
Token cost
~475 tokens
SKILL.md length
217 words
Files
1
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Document accessibility decisions and tradeoffs for a feature.

  • Works in 4 steps: Identify Decisions → Document Each Decision → Analyse Tradeoffs → …
  • A feature is being designed
  • SKILL.md covers Process and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Document is an agent skill from Owl-Listener/inclusive-design-skills. Document accessibility decisions and tradeoffs for a feature. Chains: decision-documentation, tradeoff-analysis, compliance-mapping. Use when a feature is being designed or shipped and accessibility decisions need to be captured.

Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Accessibility. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.

When your agent uses it

  • A feature is being designed
  • Shipped and accessibility decisions need to be captured

Example prompts

  • “/document”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Identify Decisions
  2. Document Each Decision
  3. Analyse Tradeoffs
  4. Map to Standards

What it can do on your machine

Read from SKILL.md and the folder at commit 6e0740f. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Document loads about 475 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 217 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~475

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 Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 217 words, ~475 tokens.

Download SKILL.mdSave it as .claude/skills/document/SKILL.md (or your agent's skills folder).
name
document
description
Document accessibility decisions and tradeoffs for a feature. Chains: decision-documentation, tradeoff-analysis, compliance-mapping. Use when a feature is being designed or shipped and accessibility decisions need to be captured.

Document Accessibility Decisions

Capture all accessibility decisions for a feature in a single, structured record that will survive team changes and redesigns.

Process

Step 1: Identify Decisions

List every design or implementation choice that affects accessibility:

  • Interaction patterns chosen
  • Content and language decisions
  • Visual design decisions
  • What was included and what was deferred
  • Tradeoffs made under constraints
Step 2: Document Each Decision

Using decision-documentation, for each decision record:

  • Context: what prompted the decision
  • Decision: what was chosen
  • Alternatives: what was considered and rejected
  • Impact: who benefits, who is affected
  • Evidence: what supported the decision
Step 3: Analyse Tradeoffs

Using tradeoff-analysis, for any decision where accessibility was compromised or where user needs conflicted:

  • Who benefits from each option
  • Who is harmed by each option
  • Severity asymmetry (blocked vs friction)
  • Remediation plan for excluded users
  • Review date
Step 4: Map to Standards

Using compliance-mapping, map each decision to the relevant WCAG criteria:

  • Which criteria does this decision satisfy
  • Which criteria does this decision affect
  • Are there any conformance risks

Output

Deliver a feature accessibility decision record:

  1. Feature summary — what was built and for whom
  2. Decision log — each decision in the standard format
  3. Tradeoff register — any tradeoffs with remediation plans
  4. Compliance map — WCAG criteria coverage and gaps
  5. Open items — deferred decisions that need future resolution

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in accessibility-decisions/skills/document of Owl-Listener/inclusive-design-skills.

Open the folder on GitHubat commit 6e0740f

Compare with similar skills

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

Document compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Document this skillOwl-Listener/inclusive-design-skills103—~475Automated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k98 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.5k4 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 98 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.5k 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.5k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from Owl-Listener/inclusive-design-skills

All 55 skills in this repo
  • Assistive Technology Scenarios

    Owl-Listener/inclusive-design-skills

    Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.

    103 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Error Prevention and Recovery

    Owl-Listener/inclusive-design-skills

    Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.

    103 GitHub stars~739 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessible Heading Structure

    Owl-Listener/inclusive-design-skills

    Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.

    103 GitHub stars~763 tokensUpdated 4 mo ago
    Auto-check passed
  • Ability Spectrum Mapping

    Owl-Listener/inclusive-design-skills

    Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.

    103 GitHub stars~917 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessibility Debt Tracking

    Owl-Listener/inclusive-design-skills

    Track and manage accessibility debt — known accessibility issues that have been deferred.

    103 GitHub stars~869 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessibility Testing Strategy

    Owl-Listener/inclusive-design-skills

    Plan what to test, how to test, and who should test for accessibility.

    103 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Document

What does Document do?

Document accessibility decisions and tradeoffs for a feature. Document is an agent skill from Owl-Listener/inclusive-design-skills. Document accessibility decisions and tradeoffs for a feature.

When should I use Document?

Document fits situations like: A feature is being designed; shipped and accessibility decisions need to be captured.

How do I install Document in Claude Code?

Run `npx skills add Owl-Listener/inclusive-design-skills --skill document -a claude-code`. Or copy the skill folder (accessibility-decisions/skills/document in Owl-Listener/inclusive-design-skills) into .claude/skills/document in your project. Claude Code loads it when a task matches its description.

How do I install Document in Codex?

Run `npx skills add Owl-Listener/inclusive-design-skills --skill document -a codex`. Or copy the skill folder (accessibility-decisions/skills/document in Owl-Listener/inclusive-design-skills) into .agents/skills/document in your project. Codex loads it when a task matches its description.

Can I use Document 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 Owl-Listener/inclusive-design-skills --skill document -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/document, .gemini/skills/document, .github/skills/document and .opencode/skills/document in your project.

What does Document need to run?

SKILL.md names no scripts, command-line tools or credentials: Document is instructions for the agent only.

Does Document 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 Document 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 Document use?

Document is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Document use?

About 475 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Document?

Skills that share tags, products or a category with Document: 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.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Document?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 103 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.

Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.