Verify Repo Skill
VectorSpaceLab/AREX-Skill
Verifies a generated or refreshed repo-specific Agent Skill by creating assertion-backed usability test cases, running content-level self-refine, checking backend-classified native repo…
Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide.
Install Usability Test Plan
$ npx skills add Owl-Listener/designer-skills --skill usability-test-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills usability-test-plan --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/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-research/skills/usability-test-plan .claude/skills/usability-test-plan && 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-test-plan" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/usability-test-plan into .claude/skills/usability-test-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-test-plan", 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/designer-skills/tree/main/design-research/skills/usability-test-planType 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/designer-skills --skill usability-test-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills usability-test-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/design-research/skills/usability-test-plan .agents/skills/usability-test-plan && 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-test-plan" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/usability-test-plan into .agents/skills/usability-test-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-test-plan", 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/designer-skills --skill usability-test-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills usability-test-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/design-research/skills/usability-test-plan .cursor/skills/usability-test-plan && 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-test-plan" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/usability-test-plan into .cursor/skills/usability-test-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-test-plan", 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/designer-skills.git --path design-research/skills/usability-test-plan--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/designer-skills --skill usability-test-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills usability-test-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/design-research/skills/usability-test-plan .gemini/skills/usability-test-plan && 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-test-plan" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/usability-test-plan into .gemini/skills/usability-test-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-test-plan", 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/designer-skills usability-test-planInstalls 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/designer-skills --skill usability-test-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/design-research/skills/usability-test-plan .github/skills/usability-test-plan && 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-test-plan" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/usability-test-plan into .github/skills/usability-test-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-test-plan", 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/designer-skills --skill usability-test-plan -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/designer-skills usability-test-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/design-research/skills/usability-test-plan .opencode/skills/usability-test-plan && 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-test-plan" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/usability-test-plan into .opencode/skills/usability-test-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usability-test-plan", 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-test-plan- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~410 tokens
- SKILL.md length
- 175 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide.
- Works in 4 steps: Define objectives: What specific… → Create the test plan with → Include a pilot test checklist: What to… → …
- Planning the study as a whole
- SKILL.md covers Context, Instructions and Further Reading
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Usability Test Plan is an agent skill from Owl-Listener/designer-skills. Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use test-scenario (prototyping-testing).
Its SKILL.md is about 410 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 Testing & QA, covering UX design, Test generation and Hypothesis generation. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Planning the study as a whole
- Tasks that involve UX design
- Tasks that involve Test generation
Example prompts
- “/usability-test-plan”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Define objectives: What specific questions should this test answer?
- Create the test plan with
- Include a pilot test checklist: What to verify before the real sessions.
- Think step by step. Present in a ready-to-use format.
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. 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 Test Plan loads about 410 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 175 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/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 175 words, ~410 tokens.
Download SKILL.mdSave it as
.claude/skills/usability-test-plan/SKILL.md (or your agent's skills folder).- name
- usability-test-plan
- description
- Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing).
Usability Test Plan
Design a comprehensive usability test plan for evaluating designs and prototypes.
Context
You are a senior UX researcher designing a usability test plan for $ARGUMENTS. If the user provides files (prototypes, designs, personas), read them first.
Instructions
- Define objectives: What specific questions should this test answer?
- Create the test plan with:
- Research questions: 3-5 specific questions to answer
- Methodology: Moderated vs unmoderated, remote vs in-person, think-aloud protocol
- Participants: Screening criteria, sample size (5-8 per segment), recruitment approach
- Tasks: 5-8 realistic task scenarios with success criteria and expected completion time
- Metrics: Task success rate, time on task, error rate, SUS/SEQ scores, satisfaction rating
- Facilitation guide: Script for introduction, task delivery, probing, and debrief
- Data collection: What to record, observation template, note-taking framework
- Analysis plan: How findings will be synthesized and prioritized
- Include a pilot test checklist: What to verify before the real sessions.
- Think step by step. Present in a ready-to-use format.
Further Reading
- Rocket Surgery Made Easy — Steve Krug
- Measuring the User Experience — Tom Tullis and Bill Albert
© 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 design-research/skills/usability-test-plan of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Usability Test Plan 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 Test Plan this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~410 | Automated safety check: Pass | MIT | |
| Verify Repo SkillVectorSpaceLab/AREX-Skill | 330 | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Exploratory Testtobihagemann/turbo | 409 | — | ~2k | Automated safety check: Pass | MIT | |
| Exploratory Testtobihagemann/turbo | 409 | — | ~2k | Automated safety check: Pass | MIT | |
| HTML Feature Mocksimbue-ai/bouncer | 400 | — | ~677 | Automated safety check: Pass | AGPL-3.0 | |
| Product Design Workflow BundleXiaomiMiMo/MiMo-Code | 14k | — | ~721 | Automated safety check: Pass | MIT |
Similar skills
Exploratory Test
tobihagemann/turbo
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens…
Exploratory Test
tobihagemann/turbo
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens…
HTML Feature Mocks
imbue-ai/bouncer
Explores a feature idea through HTML mocks that match the project's existing UI, keeping every earlier version and logging each requested tweak in a context file.
Product Design Workflow Bundle
XiaomiMiMo/MiMo-Code
Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.
Prototype
plugin87/ux-ui-agent-skills
Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Usability Test Plan
What does Usability Test Plan do?
Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Usability Test Plan is an agent skill from Owl-Listener/designer-skills. Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide.
When should I use Usability Test Plan?
Usability Test Plan fits situations like: planning the study as a whole; tasks that involve UX design; tasks that involve Test generation.
How do I install Usability Test Plan in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill usability-test-plan -a claude-code`. Or copy the skill folder (design-research/skills/usability-test-plan in Owl-Listener/designer-skills) into .claude/skills/usability-test-plan in your project. Claude Code loads it when a task matches its description.
How do I install Usability Test Plan in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill usability-test-plan -a codex`. Or copy the skill folder (design-research/skills/usability-test-plan in Owl-Listener/designer-skills) into .agents/skills/usability-test-plan in your project. Codex loads it when a task matches its description.
Can I use Usability Test Plan 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/designer-skills --skill usability-test-plan -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-test-plan, .gemini/skills/usability-test-plan, .github/skills/usability-test-plan and .opencode/skills/usability-test-plan in your project.
What does Usability Test Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Usability Test Plan is instructions for the agent only.
Does Usability Test Plan 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 Test Plan 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 Test Plan use?
Usability Test Plan 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 Test Plan use?
About 410 tokens (SKILL.md is roughly 1.6k 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 Test Plan?
Skills that share tags, products or a category with Usability Test Plan: Verify Repo Skill (VectorSpaceLab/AREX-Skill, 330 stars), Exploratory Test (tobihagemann/turbo, 409 stars), Exploratory Test (tobihagemann/turbo, 409 stars) and HTML Feature Mocks (imbue-ai/bouncer, 400 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Usability Test Plan?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,862 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.