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…
Write realistic usability task scenarios with success criteria and facilitation notes.
Install Test Scenario
$ npx skills add Owl-Listener/designer-skills --skill test-scenario -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills test-scenario --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/prototyping-testing/skills/test-scenario .claude/skills/test-scenario && 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 "test-scenario" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/test-scenario into .claude/skills/test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenario", 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/prototyping-testing/skills/test-scenarioType 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 test-scenario -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills test-scenario --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/prototyping-testing/skills/test-scenario .agents/skills/test-scenario && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-scenario" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/test-scenario into .agents/skills/test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenario", 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 test-scenario -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills test-scenario --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/prototyping-testing/skills/test-scenario .cursor/skills/test-scenario && 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 "test-scenario" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/test-scenario into .cursor/skills/test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenario", 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 prototyping-testing/skills/test-scenario--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 test-scenario -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills test-scenario --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/prototyping-testing/skills/test-scenario .gemini/skills/test-scenario && 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 "test-scenario" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/test-scenario into .gemini/skills/test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenario", 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 test-scenarioInstalls 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 test-scenario -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/prototyping-testing/skills/test-scenario .github/skills/test-scenario && 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 "test-scenario" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/test-scenario into .github/skills/test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenario", 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 test-scenario -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 test-scenario --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/prototyping-testing/skills/test-scenario .opencode/skills/test-scenario && 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 "test-scenario" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/prototyping-testing/skills/test-scenario into .opencode/skills/test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenario", 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
test-scenario- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~434 tokens
- SKILL.md length
- 203 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write realistic usability task scenarios with success criteria and facilitation notes.
- You have a study and need the tasks
- SKILL.md covers What You Do, Scenario Structure, Task Types and Scenario Writing Rules, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve UX design
What it does
Test Scenario is an agent skill from Owl-Listener/designer-skills. Write realistic usability task scenarios with success criteria and facilitation notes. Use when you have a study and need the tasks. For the surrounding study design, use usability-test-plan (design-research).
Its SKILL.md is about 430 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 Experimental design. 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
- You have a study and need the tasks
- Tasks that involve UX design
- Tasks that involve Test generation
Example prompts
- “/test-scenario”
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
Test Scenario loads about 434 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 203 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). 203 words, ~434 tokens.
Download SKILL.mdSave it as
.claude/skills/test-scenario/SKILL.md (or your agent's skills folder).- name
- test-scenario
- description
- Write realistic usability task scenarios with success criteria and facilitation notes. Use when you have a study and need the tasks. For the surrounding study design, use `usability-test-plan` (design-research).
Test Scenario
You are an expert in writing usability test scenarios that reveal genuine user behavior.
What You Do
You write test scenarios with realistic tasks, clear success criteria, and structured observation guides.
Scenario Structure
Context Setting
Brief, realistic backstory that gives the participant a reason to act without leading them.
Task
Specific goal to accomplish. Action-oriented, not question-based. Avoids UI terminology that hints at the answer.
Success Criteria
- Task completion (yes/no)
- Time to complete
- Number of errors or wrong paths
- Assistance requests
- Self-reported difficulty (1-5 scale)
Observation Guide
What to watch for: hesitations, facial expressions, verbal comments, navigation choices, error recovery behavior.
Task Types
- Exploratory: Find information (e.g., 'Find the return policy')
- Specific: Complete a goal (e.g., 'Add a blue shirt size M to your cart')
- Comparative: Choose between options
- Open-ended: Achieve a goal with multiple valid paths
Scenario Writing Rules
- Use participant's language, not product jargon
- Give motivation, not instructions
- One goal per task
- Don't reveal the UI path in the task wording
- Include both simple and complex tasks
Best Practices
- Pilot test your scenarios before real sessions
- Order tasks from easy to hard
- Include a warm-up task
- Prepare follow-up questions per task
- Write more scenarios than you need (allow flexibility)
© 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 prototyping-testing/skills/test-scenario 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
Test Scenario 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 |
|---|---|---|---|---|---|---|
| Test Scenario this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~434 | 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 | |
| Dvp Test Planhashgraph-online/awesome-codex-plugins | 1.3k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Playwright E2E Builderdavila7/claude-code-templates | 32k | — | ~5.3k | Automated safety check: Notes | 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…
Dvp Test Plan
hashgraph-online/awesome-codex-plugins
Design Verification Plan and Report (DVP&R) — build or review a test plan that links each DFMEA failure mode to a specific test, pass/fail criterion, sample size, and timing.
Playwright E2E Builder
davila7/claude-code-templates
Plan and build comprehensive Playwright E2E test suites with Page Object Model, authentication state persistence, custom fixtures, visual regression, and CI integration.
Vscuse Scenario Authoring
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when: reading a docs scenario, PRD, mockup, or user flow and using vscuse-ui/noVNC as the primary authoring surface to record, generate, replace, or update vscuse test plans…
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 Test Scenario
What does Test Scenario do?
Write realistic usability task scenarios with success criteria and facilitation notes. Test Scenario is an agent skill from Owl-Listener/designer-skills. Write realistic usability task scenarios with success criteria and facilitation notes.
When should I use Test Scenario?
Test Scenario fits situations like: you have a study and need the tasks; tasks that involve UX design; tasks that involve Test generation.
How do I install Test Scenario in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill test-scenario -a claude-code`. Or copy the skill folder (prototyping-testing/skills/test-scenario in Owl-Listener/designer-skills) into .claude/skills/test-scenario in your project. Claude Code loads it when a task matches its description.
How do I install Test Scenario in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill test-scenario -a codex`. Or copy the skill folder (prototyping-testing/skills/test-scenario in Owl-Listener/designer-skills) into .agents/skills/test-scenario in your project. Codex loads it when a task matches its description.
Can I use Test Scenario 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 test-scenario -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-scenario, .gemini/skills/test-scenario, .github/skills/test-scenario and .opencode/skills/test-scenario in your project.
What does Test Scenario need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Scenario is instructions for the agent only.
Does Test Scenario 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 Test Scenario 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 Test Scenario use?
Test Scenario 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 Test Scenario use?
About 434 tokens (SKILL.md is roughly 1.7k 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 Test Scenario?
Skills that share tags, products or a category with Test Scenario: Verify Repo Skill (VectorSpaceLab/AREX-Skill, 330 stars), Exploratory Test (tobihagemann/turbo, 409 stars), Exploratory Test (tobihagemann/turbo, 409 stars) and Dvp Test Plan (hashgraph-online/awesome-codex-plugins, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Scenario?
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.