agentsclimarketplace

Usability testing

Skill trevorgrogers/ux-designer-skills/skills/usability-testing

Usability testing methodology - study design, task creation, moderation techniques, analysis, and reporting. Use when planning user tests, writing test scripts, analyzing results, or presenting findings.From its SKILL.md

Install
npx -y skills add trevorgrogers/ux-designer-skills --skill usability-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, as published. Nobody here has run it

Usability Testing

Most teams skip usability testing because they think it's slow and expensive. It's neither. Five users, one afternoon, and a prototype that doesn't even need to work. That's it. The alternative is shipping something nobody can use and spending 3 months fixing it. Testing is faster.

When to Use This Skill

Auto-loaded by agents:

  • usability-researcher - For all research work

Use when you need:

  • Test plan for a design or prototype
  • Task scenarios for usability testing
  • Analysis framework for test results
  • Report template for stakeholders

Test Types

TypeParticipantsBest ForCost
Moderated (in-person)5-8Complex flows, early concepts, nuanced feedbackHigh
Moderated (remote)5-8Same as above, broader geographyMedium
Unmoderated (remote)15-30Validation, specific tasks, quantitative metricsLow
Guerrilla3-5Quick feedback, low-fi prototypes, cafes/hallwaysVery low
A/B testing1000+Comparing two specific variations, measuring conversionMedium (time)

Writing Good Tasks

Bad: "Find the settings page" Good: "You want to change your notification preferences so you only get emails about sales. How would you do that?"

Task Principles

  • Frame as realistic scenarios, not instructions
  • Don't use the same words as the UI labels
  • Include context and motivation
  • One goal per task
  • Write 5-7 tasks per session (30-45 min)

Key Metrics

MetricWhat It MeasuresTarget
Task success rateCan users complete the task?>78% (average benchmark)
Time on taskHow long does it take?Varies by complexity
Error rateHow many mistakes?<2 per task
SUS scoreOverall perceived usability>68 (average), >80 (good)
Task difficulty (SEQ)Perceived ease>5 on 7-point scale

The 5-User Rule

Jakob Nielsen's research shows 5 users find ~85% of usability problems. Run small tests frequently rather than large tests infrequently.

The biggest mistake teams make isn't skipping testing. It's testing to validate instead of testing to learn. If you go in wanting to prove your design works, you'll ignore every signal that it doesn't. Go in wanting to find problems. They're there.


Related Skills

  • design-heuristics - Expert evaluation (complements user testing)
  • laws-of-ux - Principles for diagnosing why users struggle

Keep looking

Skills are one crate of 610,220. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.