Skip to content
Back to skills

Test Scenario

ASecurity

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

  • 158 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
code-qualitygoexpress

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add NVlabs/Skill2Env --skill test-scenario --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Test Scenario?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Test Scenario
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nvlabs-test-scenario/badge)](https://www.skillsdirectory.com/skills/nvlabs-test-scenario)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: test-scenario
description: Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.
---
# 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)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…