usability-test-plan
Skill1 starsChanged 37 days agoMITView on GitHub
Plan a moderated or unmoderated usability test: goals, realistic tasks, success criteria, metrics, script and setup. Use when someone wants to test a prototype, flow, website or app with users, write test tasks or scenarios, or prepare a moderator script.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- pengGgxp/skillstheir own version, first seen Oct 11, 2026
- miovrag/claude-skillstheir own version, first seen Jun 12, 2026
- launchapp-dev/animus-clitheir own version, first seen Mar 15, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- launchapp-dev/animus-cli★ 39same name
- miovrag/claude-skills★ 1same name
- pengGgxp/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- accessibility-researchSkill
- ai-browser-walkthroughSkill
- analytics-insightsSkill
- card-sort-tree-testSkill
- competitive-analysisSkill
- diary-studySkill
- interview-guideSkill
- jobs-to-be-doneSkill
- journey-mapSkill
- research-planSkill
- research-readoutSkill
- screener-surveySkill
- stakeholder-interviewsSkill
- survey-designSkill
- synthetic-usersSkill
- usability-test-analysisSkill
- user-personasSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Test whether people can do what the product is for, without being told how.
- Distinctive: line 26
Don't help, lead or explain during tasks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Usability test plan
Test whether people can do what the product is for, without being told how.
Steps
- Goals: the two or three questions this test answers ("Can first time visitors start a quote from the homepage?").
- Participants: five to eight per distinct group finds most big problems. Include people who use assistive technology when you can.
- Tasks as scenarios: a realistic goal, no interface words, no hints. "Your renewal went up by 20%. Find out if you could pay less", not "Click Compare quotes".
- Success criteria for each task: what counts as success, partial success and failure, decided before testing.
- Metrics: task success, time on task, errors, a single ease question after each task (one to seven), and SUS at the end if you need a benchmark.
- Script: intro and consent, think aloud practice, tasks in a sensible order, post task questions, wrap up. Neutral prompts only: "What are you looking for?", "What would you do next?"
- Setup: device, prototype links, recording, note taking template, a pilot run with a colleague first.
Output
The plan with goals, participants, each task with its scenario and success criteria, metrics, and the full moderator script.
Don't
- Don't help, lead or explain during tasks. Don't test five features in one session; test the core flow well.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.