Agent skill · Testing & QA

usability-testing

Plan and run usability tests on existing or prototype designs including test design, task scripts, moderation, observation, and findings synthesis. Use this skill whenever the user wants to test usability, run a moderated test, run an unmoderated test, validate a design, find usability issues, or improve task completion. Triggers on usability test, usability testing, moderated test, unmoderated test, task script, think aloud, prototype testing, user testing, design validation, task completion. Also triggers when the user has built something and wants to know if real users can use it before shi

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill usability-testing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/usability-testing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Usability Testing Plan and run tests that find usability problems before users hit them in production. Stack-agnostic. Tool-agnostic. This skill is for testing existing designs or prototypes. For broader discovery research, use `ux-research`. For conversion testing in production, use `cro-optimization`. --- ## When to use - Before launching a new flow or major redesign - After a redesign to verify it doesn't introduce new problems - When analytics show drop-off but you don't know why - When customer support tickets pattern around specific UI areas - Pre-launch user validation - Comparing two design directions ## When NOT to use - Discovery / generative research (use `ux-research`) - Live conversion optimization (use `cro-optimization`) - Mapping the broader experience (use `journey-mapping`) - Pure quantitative measurement (use `analytics-strategy`) --- ## Required inputs - The design or prototype to test (functional or near-functional) - Specific tasks users would do - The audience (who should be tested) - Testing infrastructure (moderated tool, unmoderated tool, in-person setup) --- ## The framework: 5 phases ### 1. Define what to test Don't test the whole product. Test specifi

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 5 phases
  5. 1. Define what to test
  6. 2. Choose moderated or unmoderated
  7. 3. Recruit
  8. 4. Run the test
  9. 5. Synthesize and report
  10. Workflow
  11. Failure patterns
  12. Output format
  13. Reference files
Ships with 1 file
  • references/task-script-patterns.md
More from claude-skills
All skills →
About this skill
What does the usability-testing skill do?

Plan and run usability tests on existing or prototype designs including test design, task scripts, moderation, observation, and findings synthesis. Use this skill whenever the user wants to test usability, run a moderated test, run an unmoderated test, validate a design, find usability issues, or improve task completion. Triggers on usability test, usability testing, moderated test, unmoderated test, task script, think aloud, prototype testing, user testing, design validation, task completion. Also triggers when the user has built something and wants to know if real users can use it before shi

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill usability-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going