Color Audit
rome-os/rome
Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…
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.
Install Ability Spectrum Mapping
$ npx skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills ability-spectrum-mapping --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/inclusive-personas/skills/ability-spectrum-mapping .claude/skills/ability-spectrum-mapping && rm -rf skills-srcUse ~/.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/
Install the "ability-spectrum-mapping" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/ability-spectrum-mapping into .claude/skills/ability-spectrum-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ability-spectrum-mapping", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/ability-spectrum-mappingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills ability-spectrum-mapping --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/inclusive-personas/skills/ability-spectrum-mapping .agents/skills/ability-spectrum-mapping && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ability-spectrum-mapping" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/ability-spectrum-mapping into .agents/skills/ability-spectrum-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ability-spectrum-mapping", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills ability-spectrum-mapping --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/inclusive-personas/skills/ability-spectrum-mapping .cursor/skills/ability-spectrum-mapping && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ability-spectrum-mapping" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/ability-spectrum-mapping into .cursor/skills/ability-spectrum-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ability-spectrum-mapping", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path inclusive-personas/skills/ability-spectrum-mapping--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills ability-spectrum-mapping --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/inclusive-personas/skills/ability-spectrum-mapping .gemini/skills/ability-spectrum-mapping && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ability-spectrum-mapping" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/ability-spectrum-mapping into .gemini/skills/ability-spectrum-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ability-spectrum-mapping", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills ability-spectrum-mappingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/inclusive-personas/skills/ability-spectrum-mapping .github/skills/ability-spectrum-mapping && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ability-spectrum-mapping" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/ability-spectrum-mapping into .github/skills/ability-spectrum-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ability-spectrum-mapping", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills ability-spectrum-mapping --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/inclusive-personas/skills/ability-spectrum-mapping .opencode/skills/ability-spectrum-mapping && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ability-spectrum-mapping" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/ability-spectrum-mapping into .opencode/skills/ability-spectrum-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ability-spectrum-mapping", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ability-spectrum-mapping- GitHub stars
- 103
- Token cost
- ~917 tokens
- SKILL.md length
- 456 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 4 steps: List Core Tasks → Define the Spectrums → Map Each Task → …
- Planning accessibility coverage for a new feature before design starts
- SKILL.md covers Why a Spectrum, How to Build an Ability…, Presenting to Stakeholders and Template, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill treats accessibility as a range instead of a yes-or-no question about who can use a product. You list the five to ten most important tasks, define four or five points on each relevant spectrum (vision, hearing, motor and cognitive), then rate every task at every point as works well, works with friction, works with workaround or fails.
The ratings reveal breakpoints, the places where the design moves from working to failing, which mark the edge of who is currently excluded. The skill then helps you present the map to stakeholders, as a way to show where accessibility investment matters most and that accessibility is a continuum rather than a checkbox. It is a method and rating scale only, with no scripts or bundled files.
When your agent uses it
- Planning accessibility coverage for a new feature before design starts
- Finding where a signup or checkout flow breaks for keyboard-only or screen reader users
- Explaining accessibility scope and known gaps to stakeholders
Example prompts
- “Build an ability spectrum map for our online checkout across vision, hearing, motor and cognitive needs.”
- “Where does our video upload flow fail for users with limited hand movement?”
- “Turn the spectrum map into a one-page accessibility scope summary for the leadership team.”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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
Ability Spectrum Mapping loads about 917 tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 456 words of instructions outside code blocks.
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). 456 words, ~917 tokens.
Download SKILL.mdSave it as
.claude/skills/ability-spectrum-mapping/SKILL.md (or your agent's skills folder).- name
- ability-spectrum-mapping
- description
- Map how a product or feature works across the full spectrum of human ability — not just 'can use' and 'can't use'. Use when planning accessibility coverage, identifying gaps, or communicating accessibility scope to stakeholders. Triggers on: ability spectrum, range of users, who can use this, who can't use this, accessibility coverage, accessibility scope, ability range, spectrum of needs.
Ability Spectrum Mapping
Map how a feature performs across the full range of human ability — from full capability to no capability in each dimension — to identify where the design starts to break down and who gets excluded.
Why a Spectrum
Accessibility is not binary. It's not "can see" vs "blind." The reality is a continuous spectrum:
- Full vision → needs glasses → low vision → legally blind → no vision
- Full hearing → mild loss → moderate loss → severe loss → deaf
- Full dexterity → mild tremor → limited range → single hand → no hands
- Full cognition → mild difficulty → moderate difficulty → significant support needs
Products don't go from "works" to "doesn't work" in a single step. They degrade gradually. The spectrum map shows you exactly where your design starts failing and for whom.
How to Build an Ability Spectrum Map
Step 1: List Core Tasks
Identify the 5–10 most important tasks a user performs with the product.
Step 2: Define the Spectrums
For each relevant ability dimension, define 4–5 points:
Vision spectrum: Full vision → Corrected vision → Low vision (magnification) → Very low vision (screen reader + some vision) → No vision (screen reader only)
Hearing spectrum: Full hearing → Mild loss (louder volume) → Moderate loss (captions needed) → Severe loss (captions + visual alerts) → Deaf (fully visual communication)
Motor spectrum: Full dexterity → Reduced precision (larger targets) → Limited range (keyboard only) → Minimal movement (switch or voice) → No hand use (eye tracking, sip-and-puff)
Cognitive spectrum: Comfortable with complexity → Prefers simplicity → Needs plain language → Needs step-by-step guidance → Needs significant support
Step 3: Map Each Task
For each task × ability point, rate:
- Works well — no barriers
- Works with friction — possible but harder than it should be
- Works with workaround — user must find their own solution
- Fails — task cannot be completed
Show full SKILL.md (176 more words)Show less
Step 4: Identify the Breakpoints
Where does the design shift from "works" to "fails"? That breakpoint is your accessibility boundary. Everything to the right of it is excluded.
The goal is to push that boundary as far right as possible.
Presenting to Stakeholders
The spectrum map is a powerful communication tool because it shows:
- Exactly how many users are affected at each point
- Where investment in accessibility has the highest return
- That accessibility is a continuum, not a checkbox
- Which fixes would move the boundary and include more people
Template
| Task | Full vision | Low vision | Screen reader |
|---|---|---|---|
| Search for a product | Works well | Works with friction (small targets) | Fails (search suggestions not announced) |
| Complete checkout | Works well | Works well | Works with friction (form errors not associated) |
Assessment Questions
- Have you mapped core tasks across at least vision, motor, and cognitive spectrums?
- Can you identify the exact breakpoint where each task fails?
- Do you know which fixes would include the most additional users?
- Can you communicate the spectrum to stakeholders without technical jargon?
© 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 inclusive-personas/skills/ability-spectrum-mapping of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Ability Spectrum Mapping 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ability Spectrum Mapping this skillOwl-Listener/inclusive-design-skills | 103 | — | ~917 | Automated safety check: Pass | MIT | |
| Color Auditrome-os/rome | 725 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Dont Make Me Thinkluongnv89/skills | 131 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Super UI UX Designsyahiidkamil/Software-Engineer-AI-Agent-Atlas | 401 | — | ~9k | Automated safety check: Pass | None | |
| Design Critiquegetcrew44/crew44 | 356 | — | ~691 | Automated safety check: Pass | MIT | |
| UI Automation Workflowsconorluddy/xclaude-plugin | 183 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Dont Make Me Think
luongnv89/skills
Review UI usability using Steve Krug's principles and produce a scannable report.
Super UI UX Design
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete UI/UX design capability — a wiki-style knowledge map of design theory (UX laws, Nielsen heuristics, usability, visual hierarchy, typography, contrast/WCAG, design systems…
Design Critique
getcrew44/crew44
Walks an agent through five review passes on a screen, flow or mockup, then returns ranked findings with a severity and a suggested fix for each one.
UI Automation Workflows
conorluddy/xclaude-plugin
Accessibility-first UI automation using IDB. An agent skill from conorluddy/xclaude-plugin.
Lamina UX
aryaniyaps/lamina
Design understandable and accessible product interactions. An agent skill from aryaniyaps/lamina.
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoAssistive 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.
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.
Accessible Heading Structure
Owl-Listener/inclusive-design-skills
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Accessibility Testing Strategy
Owl-Listener/inclusive-design-skills
Plan what to test, how to test, and who should test for accessibility.
Alt Text Design
Owl-Listener/inclusive-design-skills
Write meaningful alternative text for images, charts, diagrams, and visual content.
Related
Categories
Questions about Ability Spectrum Mapping
What does Ability Spectrum Mapping do?
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. This skill treats accessibility as a range instead of a yes-or-no question about who can use a product. You list the five to ten most important tasks, define four or five points on each relevant spectrum (vision, hearing, motor and cognitive), then rate every task at every point as works well, works with friction, works with workaround or fails.
When should I use Ability Spectrum Mapping?
Ability Spectrum Mapping fits situations like: planning accessibility coverage for a new feature before design starts; finding where a signup or checkout flow breaks for keyboard-only or screen reader users; explaining accessibility scope and known gaps to stakeholders.
How do I install Ability Spectrum Mapping in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping -a claude-code`. Or copy the skill folder (inclusive-personas/skills/ability-spectrum-mapping in Owl-Listener/inclusive-design-skills) into .claude/skills/ability-spectrum-mapping in your project. Claude Code loads it when a task matches its description.
How do I install Ability Spectrum Mapping in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping -a codex`. Or copy the skill folder (inclusive-personas/skills/ability-spectrum-mapping in Owl-Listener/inclusive-design-skills) into .agents/skills/ability-spectrum-mapping in your project. Codex loads it when a task matches its description.
Can I use Ability Spectrum Mapping 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 ability-spectrum-mapping -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ability-spectrum-mapping, .gemini/skills/ability-spectrum-mapping, .github/skills/ability-spectrum-mapping and .opencode/skills/ability-spectrum-mapping in your project.
What does Ability Spectrum Mapping need to run?
SKILL.md names no scripts, command-line tools or credentials: Ability Spectrum Mapping is instructions for the agent only.
Does Ability Spectrum Mapping 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 Ability Spectrum Mapping 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 Ability Spectrum Mapping use?
Ability Spectrum Mapping 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 Ability Spectrum Mapping use?
About 917 tokens (SKILL.md is roughly 3.7k 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 Ability Spectrum Mapping?
Skills that share tags, products or a category with Ability Spectrum Mapping: Color Audit (rome-os/rome, 725 stars), Dont Make Me Think (luongnv89/skills, 131 stars), Super UI UX Design (syahiidkamil/Software-Engineer-AI-Agent-Atlas, 401 stars) and Design Critique (getcrew44/crew44, 356 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ability Spectrum Mapping?
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.