Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
owl-listener avatar

Usability Testing

  • 11 installs
  • 233 repo stars
  • Updated June 23, 2026
  • owl-listener/designpowers

Helps with testing & qa tasks during AI-assisted development.

About

usability-testing is a Claude Code skill for testing & qa. It helps developers move faster with AI-assisted coding.

  • usability-testing
  • Testing & QA
  • AI-coding skill

Usability Testing by the numbers

  • 11 all-time installs (skills.sh)
  • Ranked #1,539 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 1, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designpowers --skill usability-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs11
repo stars233
Last updatedJune 23, 2026
Repositoryowl-listener/designpowers

What it does

Helps with testing & qa tasks during AI-assisted development.

Files

SKILL.mdMarkdownGitHub ↗

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

MethodWhen to useMinimum participants
Moderated think-aloudNew flows, complex interactions5
Unmoderated remoteSimple tasks, large sample8-12
Guerrilla (hallway)POC validation, time-constrained3-5
Accessibility audit with AT usersAfter build, before ship2-3

Step 4: Write the Test Script

1. Welcome — explain what you're testing (the design, not them) 2. Background — 2-3 questions about their relationship to the problem 3. Tasks — present each scenario one at a time, observe silently 4. 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

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.