User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
A skill your agent uses when defining who a design serves — creating personas, user stories, or scenarios — ensures the full ability spectrum and situational contexts are represented from the start…
Install Inclusive Personas
$ npx skills add Owl-Listener/designpowers --skill inclusive-personas -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers inclusive-personas --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/designpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/inclusive-personas .claude/skills/inclusive-personas && 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 "inclusive-personas" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inclusive-personas into .claude/skills/inclusive-personas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inclusive-personas", 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/designpowers/tree/main/skills/inclusive-personasType 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/designpowers --skill inclusive-personas -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers inclusive-personas --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/inclusive-personas .agents/skills/inclusive-personas && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "inclusive-personas" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inclusive-personas into .agents/skills/inclusive-personas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inclusive-personas", 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/designpowers --skill inclusive-personas -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers inclusive-personas --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/inclusive-personas .cursor/skills/inclusive-personas && 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 "inclusive-personas" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inclusive-personas into .cursor/skills/inclusive-personas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inclusive-personas", 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/designpowers.git --path skills/inclusive-personas--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/designpowers --skill inclusive-personas -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers inclusive-personas --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/inclusive-personas .gemini/skills/inclusive-personas && 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 "inclusive-personas" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inclusive-personas into .gemini/skills/inclusive-personas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inclusive-personas", 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/designpowers inclusive-personasInstalls 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/designpowers --skill inclusive-personas -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/inclusive-personas .github/skills/inclusive-personas && 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 "inclusive-personas" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inclusive-personas into .github/skills/inclusive-personas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inclusive-personas", 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/designpowers --skill inclusive-personas -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/designpowers inclusive-personas --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/inclusive-personas .opencode/skills/inclusive-personas && 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 "inclusive-personas" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inclusive-personas into .opencode/skills/inclusive-personas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inclusive-personas", 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
inclusive-personas- GitHub stars
- 251
- Token cost
- ~1k tokens
- SKILL.md length
- 448 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when defining who a design serves — creating personas, user stories, or scenarios — ensures the full ability spectrum and situational contexts are represented from the start…
- Works in 6 steps: Map the Ability Spectrum → Identify Relevant Personas → Build Each Persona → …
- Defining who a design serves — creating personas
- SKILL.md covers The Principle, Process, Integration and Anti-Patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Inclusive Personas is an agent skill from Owl-Listener/designpowers. Use when defining who a design serves — creating personas, user stories, or scenarios — ensures the full ability spectrum and situational contexts are represented from the start, not retrofitted
Its SKILL.md is about 1k 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 Product & Project Management, covering User stories. The repository describes itself as: An agent design team you control: 10 agents that run an inclusive design process while you direct. The licence is MIT.
When your agent uses it
- Defining who a design serves — creating personas
- Scenarios — ensures the full ability spectrum and situational contexts are represented from the start
- Not retrofitted
Example prompts
- “/inclusive-personas”
Workflow steps
6 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 cb00757. 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 (its code samples are markdown).
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
Inclusive Personas loads about 1k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 448 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/designpowers at commit cb00757, republished under its MIT licence (© Owl-Listener). 448 words, ~1,039 tokens.
Download SKILL.mdSave it as
.claude/skills/inclusive-personas/SKILL.md (or your agent's skills folder).- name
- inclusive-personas
- description
- Use when defining who a design serves — creating personas, user stories, or scenarios — ensures the full ability spectrum and situational contexts are represented from the start, not retrofitted
Inclusive Personas
Personas shape every design decision that follows. If your personas only represent able-bodied, neurotypical, tech-savvy adults with fast internet, your design will only work for those people. This skill ensures the full range of human experience is represented from the beginning.
The Principle
"Nothing About Us Without Us." Design for the margins and the centre benefits. Design for the centre and the margins get excluded.
Process
Step 1: Map the Ability Spectrum
For the design context, identify the relevant spectrum across:
Permanent conditions:
- Vision: blind, low vision, colour blind
- Hearing: deaf, hard of hearing
- Motor: limited fine motor, limited reach, tremor, paralysis
- Cognitive: learning differences, memory challenges, attention differences
- Speech: non-verbal, speech differences
Temporary conditions:
- Broken arm, ear infection, concussion, medication effects, post-surgery
Situational conditions:
- Bright sunlight, noisy environment, one hand occupied, driving, multitasking, emotional distress, unfamiliar language, slow connection
Step 2: Identify Relevant Personas
Not every project needs every persona. Select 4-6 personas that represent:
- 2-3 primary users — the most common use cases
- 1-2 edge case users — people at the margins whose needs reveal design weaknesses
- 1 stress case user — someone using the design under difficult circumstances
Step 3: Build Each Persona
For each persona, document:
## [Name]
**Context:** [Who they are, what they do, their relationship to this product]
**Abilities and conditions:** [Permanent, temporary, or situational factors that affect how they interact with interfaces]
**Technology:** [Devices, assistive technology, connection speed, technical confidence]
**Goals:** [What they need to accomplish]
**Frustrations:** [What typically goes wrong for them with similar products]
**Environment:** [Where and when they use this — lighting, noise, distractions, time pressure]Step 4: Write Inclusive User Stories
For each persona, write stories that capture:
- The standard path: "As [persona], I want to [goal] so that [outcome]"
- The assisted path: "As [persona] using [assistive technology], I want to [goal] so that [outcome]"
- The stress path: "As [persona] under [stressful condition], I need to [goal] without [negative outcome]"
Show full SKILL.md (194 more words)Show less
Step 5: Identify Scenario Intersections
Map where personas overlap in unexpected ways:
- A sighted user in bright sunlight has similar needs to a low-vision user
- A stressed parent holding a baby has similar motor constraints to someone with limited hand mobility
- A non-native speaker has similar needs to someone with a cognitive processing difference
These intersections reveal universal design opportunities.
Step 6: Present and Validate
Present personas to the user. Ask:
- Who is missing from this set?
- Do these feel like real people or cardboard cutouts?
- Which persona makes you most uncomfortable? (That one probably needs the most attention)
Save to: docs/designpowers/personas/YYYY-MM-DD-<project>-personas.md
Integration
- Called by:
research-planning,design-discovery - Informs: Every subsequent design skill — personas should be referenced when making any design decision
- Pairs with:
cognitive-accessibility,adaptive-interfaces
Anti-Patterns
| Pattern | Problem |
|---|---|
| "Our users are everyone" | If everyone is your user, nobody is. Define specific people |
| Personas without disabilities | You have excluded a quarter of the population |
| Edge cases treated as afterthoughts | Edge cases reveal the quality of your design. They come first, not last |
| Personas based on demographics alone | Age and job title do not determine how someone uses an interface. Focus on behaviour, ability, and context |
© 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 skills/inclusive-personas of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Inclusive Personas 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 |
|---|---|---|---|---|---|---|
| Inclusive Personas this skillOwl-Listener/designpowers | 251 | — | ~1k | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from Owl-Listener/designpowers
All 33 skills in this repoAdaptive Interfaces
Owl-Listener/designpowers
A skill your agent uses when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density, or any interface behaviour that should adapt to…
Design Debate
Owl-Listener/designpowers
A skill your agent uses when a design direction is uncertain, when the team could go multiple ways, or when the user wants to see competing approaches argued before committing — orchestrates…
Design Debt Tracker
Owl-Listener/designpowers
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
Design Discovery
Owl-Listener/designpowers
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying user-facing behaviour.
Design Handoff
Owl-Listener/designpowers
A skill your agent uses when design work is complete and needs to be communicated to engineering — creates specifications, documents rationale, accessibility requirements, and interaction details in…
Design Review
Owl-Listener/designpowers
A skill your agent uses when the user wants to evaluate something that ALREADY EXISTS rather than build something new — "review this", "audit this screen", "what's wrong with this page", "is this…
Related
Categories
Questions about Inclusive Personas
What does Inclusive Personas do?
A skill your agent uses when defining who a design serves — creating personas, user stories, or scenarios — ensures the full ability spectrum and situational contexts are represented from the start…. Inclusive Personas is an agent skill from Owl-Listener/designpowers.
When should I use Inclusive Personas?
Inclusive Personas fits situations like: defining who a design serves — creating personas; scenarios — ensures the full ability spectrum and situational contexts are represented from the start; not retrofitted.
How do I install Inclusive Personas in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill inclusive-personas -a claude-code`. Or copy the skill folder (skills/inclusive-personas in Owl-Listener/designpowers) into .claude/skills/inclusive-personas in your project. Claude Code loads it when a task matches its description.
How do I install Inclusive Personas in Codex?
Run `npx skills add Owl-Listener/designpowers --skill inclusive-personas -a codex`. Or copy the skill folder (skills/inclusive-personas in Owl-Listener/designpowers) into .agents/skills/inclusive-personas in your project. Codex loads it when a task matches its description.
Can I use Inclusive Personas 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/designpowers --skill inclusive-personas -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inclusive-personas, .gemini/skills/inclusive-personas, .github/skills/inclusive-personas and .opencode/skills/inclusive-personas in your project.
What does Inclusive Personas need to run?
SKILL.md names no scripts, command-line tools or credentials: Inclusive Personas is instructions for the agent only.
Does Inclusive Personas 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 Inclusive Personas 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 Inclusive Personas use?
Inclusive Personas 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 Inclusive Personas use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Inclusive Personas?
Skills that share tags, products or a category with Inclusive Personas: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Inclusive Personas?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designpowers, which has 251 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on June 23, 2026.
Source: Owl-Listener/designpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.