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

Scenario Map

by Owl-Listener in Owl-Listener/inclusive-design-skills

Map inclusive usage scenarios across ability spectrums for a product or feature.

MITAuto-check passedTesting & QA

Install Scenario Map

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

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

GitHub CLI
$ gh skill install Owl-Listener/inclusive-design-skills scenario-map --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/inclusive-personas/skills/scenario-map .claude/skills/scenario-map && 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
scenario-map
GitHub stars
104
Token cost
~568 tokens
SKILL.md length
262 words
Files
1
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Map inclusive usage scenarios across ability spectrums for a product or feature.

  • Works in 5 steps: Identify Core Tasks → Map the Ability Spectrum → Map Situational Contexts → …
  • Planning test coverage
  • SKILL.md covers Process and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Scenario Map is an agent skill from Owl-Listener/inclusive-design-skills. Map inclusive usage scenarios across ability spectrums for a product or feature. Chains: ability-spectrum-mapping, situational-impairment-mapping, assistive-technology-scenarios. Use when planning test coverage, identifying accessibility gaps, or understanding how a feature performs across diverse users.

Its SKILL.md is about 570 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 Testing & QA, covering Test coverage and 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

  • Planning test coverage
  • Identifying accessibility gaps
  • Understanding how a feature performs across diverse users

Example prompts

  • “/scenario-map”

Workflow steps

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

  1. Identify Core Tasks
  2. Map the Ability Spectrum
  3. Map Situational Contexts
  4. Write Critical Scenarios
  5. Identify Gaps and Priorities

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

Scenario Map loads about 568 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 262 words of instructions outside code blocks.

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

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). 262 words, ~568 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-map/SKILL.md (or your agent's skills folder).
name
scenario-map
description
Map inclusive usage scenarios across ability spectrums for a product or feature. Chains: ability-spectrum-mapping, situational-impairment-mapping, assistive-technology-scenarios. Use when planning test coverage, identifying accessibility gaps, or understanding how a feature performs across diverse users.

Map Inclusive Usage Scenarios

Generate a comprehensive map of how a product or feature is experienced across different abilities, technologies, and contexts — surfacing gaps before users find them.

Process

Step 1: Identify Core Tasks

List the 5–10 most important tasks for the product or feature. Focus on the tasks that matter most to users — the ones where failure means the product has failed.

Step 2: Map the Ability Spectrum

Using ability-spectrum-mapping, for each core task, rate performance across vision, hearing, motor, and cognitive spectrums. Identify the breakpoints where each task degrades or fails.

Step 3: Map Situational Contexts

Using situational-impairment-mapping, identify the realistic contexts where users encounter your product and the impairments those contexts create. Cross-reference with the ability spectrum to find compounding effects.

Step 4: Write Critical Scenarios

Using assistive-technology-scenarios, write detailed scenarios for the highest-risk combinations: the tasks most likely to fail for the users most likely to be affected.

Prioritise:

  • Core tasks that fail at common ability levels
  • Situational contexts that affect large user populations
  • Combinations where multiple impairments compound
Step 5: Identify Gaps and Priorities

Map all findings into a single view showing:

  • Which tasks work for whom
  • Where the breakpoints are
  • Which fixes would include the most users

Output

Deliver a scenario map containing:

  1. Task × ability matrix — showing works / friction / fails for each combination
  2. Situational context overlay — which contexts compound which ability barriers
  3. Critical scenarios — detailed narratives for highest-risk combinations
  4. Gap analysis — where the product fails and for whom
  5. Priority fixes — ranked by number of users unblocked and severity of current failure

© 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/scenario-map of Owl-Listener/inclusive-design-skills.

Open the folder on GitHubat commit 6e0740f

Compare with similar skills

Scenario Map 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.

Scenario Map compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Map this skillOwl-Listener/inclusive-design-skills104—~568Automated safety check: PassMIT
Ds Test Componentbaloise/design-system114—~2.1kAutomated safety check: PassApache-2.0
Libreqos Review Subagents WorkflowLibreQoE/LibreQoS719—~1.2kAutomated safety check: PassGPL-2.0
Amann Revisionbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.5kAutomated safety check: PassMIT
Arecon Revisionbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.9kAutomated safety check: PassMIT
Arsoc Revisionbrycewang-stanford/Awesome-Journal-Skills1.2k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Ds Test Component

    baloise/design-system

    Auto-generate all test files for DS components including visual, a11y, component, page object, and unit tests.

    114 GitHub stars~2.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Libreqos Review Subagents Workflow

    LibreQoE/LibreQoS

    Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions.

    719 GitHub stars~1.2k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Amann Revision

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework/attitude asks, coverage gaps, balance complaints, and…

    1.2k GitHub stars~1.5k tokensUpdated 12 days ago
    Frontend & DesignAuto-check passed

  • Arecon Revision

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to Editorial Committee and referee feedback on an Annual Review of Economics (ARE) review — coverage gaps, balance/accuracy complaints, framework/structure…

    1.2k GitHub stars~1.9k tokensUpdated 12 days ago
    Frontend & DesignAuto-check passed

  • Arsoc Revision

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps, balance/accuracy complaints, framework/structure…

    1.2k GitHub stars~2.1k tokensUpdated 12 days ago
    Frontend & DesignAuto-check passed

  • Jel Revision

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to editor and referee feedback on a Journal of Economic Literature (JEL) survey — coverage gaps, balance complaints, framework/structure asks, and…

    1.2k GitHub stars~1.3k tokensUpdated 12 days ago
    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.

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

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

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

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

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

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

Categories

Questions about Scenario Map

What does Scenario Map do?

Map inclusive usage scenarios across ability spectrums for a product or feature. Scenario Map is an agent skill from Owl-Listener/inclusive-design-skills. Map inclusive usage scenarios across ability spectrums for a product or feature.

When should I use Scenario Map?

Scenario Map fits situations like: planning test coverage; identifying accessibility gaps; understanding how a feature performs across diverse users.

How do I install Scenario Map in Claude Code?

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

How do I install Scenario Map in Codex?

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

Can I use Scenario Map 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 scenario-map -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-map, .gemini/skills/scenario-map, .github/skills/scenario-map and .opencode/skills/scenario-map in your project.

What does Scenario Map need to run?

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

Does Scenario Map 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 Scenario Map 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 Scenario Map use?

Scenario Map 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 Scenario Map use?

About 568 tokens (SKILL.md is roughly 2.3k 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 Scenario Map?

Skills that share tags, products or a category with Scenario Map: Ds Test Component (baloise/design-system, 114 stars), Libreqos Review Subagents Workflow (LibreQoE/LibreQoS, 719 stars), Amann Revision (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Arecon Revision (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Map?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 104 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.