Lean UX Canvas v2
deanpeters/Product-Manager-Skills
Guides a team through Jeff Gothelf's Lean UX Canvas v2 to frame a business problem, surface assumptions and decide what to learn and test next.
A skill your agent uses when planning or conducting usability tests — writing test scripts, defining tasks, selecting participants, analysing findings, and turning observations into design actions
Install Usability Testing
$ npx skills add Owl-Listener/designpowers --skill usability-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers usability-testing --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/usability-testing .claude/skills/usability-testing && 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 "usability-testing" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/usability-testing into .claude/skills/usability-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-testing", 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/usability-testingType 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 usability-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers usability-testing --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/usability-testing .agents/skills/usability-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "usability-testing" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/usability-testing into .agents/skills/usability-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-testing", 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 usability-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers usability-testing --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/usability-testing .cursor/skills/usability-testing && 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 "usability-testing" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/usability-testing into .cursor/skills/usability-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-testing", 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/usability-testing--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 usability-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers usability-testing --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/usability-testing .gemini/skills/usability-testing && 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 "usability-testing" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/usability-testing into .gemini/skills/usability-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-testing", 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 usability-testingInstalls 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 usability-testing -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/usability-testing .github/skills/usability-testing && 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 "usability-testing" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/usability-testing into .github/skills/usability-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-testing", 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 usability-testing -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 usability-testing --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/usability-testing .opencode/skills/usability-testing && 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 "usability-testing" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/usability-testing into .opencode/skills/usability-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-testing", 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
usability-testing- GitHub stars
- 251
- Token cost
- ~710 tokens
- SKILL.md length
- 357 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning or conducting usability tests — writing test scripts, defining tasks, selecting participants, analysing findings, and turning observations into design actions
- Works in 6 steps: Define What You're Testing → Select Participants → Choose Method → …
- Conducting usability tests — writing test scripts
- SKILL.md covers When to Use, Process, What You Deliver and Integration
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Usability Testing is an agent skill from Owl-Listener/designpowers. Use when planning or conducting usability tests — writing test scripts, defining tasks, selecting participants, analysing findings, and turning observations into design actions
Its SKILL.md is about 710 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 research and UX design. 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
- Conducting usability tests — writing test scripts
- Selecting participants
- Analysing findings
- Turning observations into design actions
Example prompts
- “/usability-testing”
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.
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
Usability Testing loads about 710 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 357 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). 357 words, ~710 tokens.
Download SKILL.mdSave it as
.claude/skills/usability-testing/SKILL.md (or your agent's skills folder).- name
- usability-testing
- description
- Use when planning or conducting usability tests — writing test scripts, defining tasks, selecting participants, analysing findings, and turning observations into design actions
Usability Testing
Testing with real people is how you find out if the design works — not by looking at it, but by watching someone use it.
When to Use
- After design-builder produces a working prototype
- Before declaring a design complete
- When the design-critic flags persona coverage gaps
- When assumptions about user behaviour need evidence
Process
Step 1: Define What You're Testing
Write 3-5 task scenarios that map to the core jobs in the brief. Each task:
- Starts with a realistic trigger — "You just bought a new plant and want to add it to the app"
- Has a clear success condition — "The plant appears in your list with a watering schedule"
- Does not tell the user how — never say "tap the + button"
Step 2: Select Participants
Recruit 5-8 participants. At minimum include:
- 1 person who uses a screen reader
- 1 person over 60
- 1 person who is not a native speaker of the interface language
- 1 person with low tech confidence
Reference inclusive-personas for the ability spectrum.
Step 3: Choose Method
| Method | When to use | Minimum participants |
|---|---|---|
| Moderated think-aloud | New flows, complex interactions | 5 |
| Unmoderated remote | Simple tasks, large sample | 8-12 |
| Guerrilla (hallway) | POC validation, time-constrained | 3-5 |
| Accessibility audit with AT users | After build, before ship | 2-3 |
Show full SKILL.md (151 more words)Show less
Step 4: Write the Test Script
- Welcome — explain what you're testing (the design, not them)
- Background — 2-3 questions about their relationship to the problem
- Tasks — present each scenario one at a time, observe silently
- Debrief — "What was hardest?" "What would you change?"
Never help during a task. Silence is data.
Step 5: Analyse Findings
Classify outcomes per task:
- Completed easily — no hesitation, no errors
- Completed with difficulty — hesitation or errors but recovered
- Failed — could not complete
- Completed wrong — thought they succeeded but didn't
Severity: Critical (blocks 2+ participants), Major (significant difficulty), Minor (noticed but not impeding).
Step 6: Turn Findings Into Actions
Every finding becomes a design action: "[Severity] [What happened] → [Design action] → [Which agent handles it]"
What You Deliver
- Task success rates table
- Ranked findings by severity
- Design actions with agent assignments
- Recommendation: iterate / ship / rethink
Integration
- Informed by:
inclusive-personas,design-discovery - Feeds into:
design-lead,design-builder,design-strategist
© 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/usability-testing of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Usability Testing 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 |
|---|---|---|---|---|---|---|
| Usability Testing this skillOwl-Listener/designpowers | 251 | — | ~710 | Automated safety check: Pass | MIT | |
| Lean UX Canvas v2deanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~6.2k | Automated safety check: Pass | Custom licence | |
| Usability TestingProrise-cool/Claude-Code-Multi-Agent | 305 | — | ~4.2k | Automated safety check: Pass | None | |
| Research PlannerLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Product Design Super Intelligencecoco-research/coco | 482 | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| UX Researcher Designeralirezarezvani/claude-skills | 28k | 1 repos | ~3k | Automated safety check: Pass | MIT |
Similar skills
Usability Testing
Prorise-cool/Claude-Code-Multi-Agent
Design and plan usability tests - task creation, think-aloud protocols, moderator scripts, metrics definition, and analysis frameworks.
Research Planner
LeoYeAI/openclaw-master-skills
Designs market and user research plans focused on methodology selection and research material authoring (screeners, surveys, interview guides, usability task scripts, etc.).
Product Design Super Intelligence
coco-research/coco
Your product + design brain trust and decision partner. An agent skill from coco-research/coco.
UX Researcher Designer
alirezarezvani/claude-skills
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis.
Product Research
alirezarezvani/claude-skills
A skill your agent uses when planning and synthesizing product/user research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test…
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
Questions about Usability Testing
What does Usability Testing do?
A skill your agent uses when planning or conducting usability tests — writing test scripts, defining tasks, selecting participants, analysing findings, and turning observations into design actions. Usability Testing is an agent skill from Owl-Listener/designpowers.
When should I use Usability Testing?
Usability Testing fits situations like: conducting usability tests — writing test scripts; selecting participants; analysing findings; turning observations into design actions.
How do I install Usability Testing in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill usability-testing -a claude-code`. Or copy the skill folder (skills/usability-testing in Owl-Listener/designpowers) into .claude/skills/usability-testing in your project. Claude Code loads it when a task matches its description.
How do I install Usability Testing in Codex?
Run `npx skills add Owl-Listener/designpowers --skill usability-testing -a codex`. Or copy the skill folder (skills/usability-testing in Owl-Listener/designpowers) into .agents/skills/usability-testing in your project. Codex loads it when a task matches its description.
Can I use Usability Testing 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 usability-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/usability-testing, .gemini/skills/usability-testing, .github/skills/usability-testing and .opencode/skills/usability-testing in your project.
What does Usability Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Usability Testing is instructions for the agent only.
Does Usability Testing 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 Usability Testing 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 Usability Testing use?
Usability Testing 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 Usability Testing use?
About 710 tokens (SKILL.md is roughly 2.8k 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 Usability Testing?
Skills that share tags, products or a category with Usability Testing: Lean UX Canvas v2 (deanpeters/Product-Manager-Skills, 7.2k stars), Usability Testing (Prorise-cool/Claude-Code-Multi-Agent, 305 stars), Research Planner (LeoYeAI/openclaw-master-skills, 2.2k stars) and Product Design Super Intelligence (coco-research/coco, 482 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Usability Testing?
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.