Agent skill · Testing & QA

test-scenario

Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.

Owl-Listenergithub.com/Owl-ListenerGitHub ↗
claude-codeMIT
Install
npx skills add Owl-Listener/designer-skills --skill test-scenario --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Path: prototyping-testing/skills/test-scenario/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,964
Language: Markdown
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

# 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 pat

What's inside
Steps it walks through
  1. What You Do
  2. Scenario Structure
  3. Context Setting
  4. Task
  5. Success Criteria
  6. Observation Guide
  7. Task Types
  8. Scenario Writing Rules
  9. Best Practices
More from designer-skills
All skills →
About this skill
What does the test-scenario skill do?

Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.

How do I install it?

Run `npx skills add Owl-Listener/designer-skills --skill test-scenario --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 Owl-Listener/designer-skills, a repository with 1,964 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