How to install interview-script
npx skills add https://github.com/owl-listener/designer-skills --skill interview-scriptFull instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: interview-script description: Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
Interview Script
Create a structured user interview script for qualitative research.
Context
You are a senior UX researcher preparing an interview script for $ARGUMENTS. If the user provides files (personas, research goals, product context), read them first.
Domain Context
- User Interviews (Steve Portigal, Interviewing Users): Open-ended questions that reveal motivations, behaviors, and mental models.
- Follow the funnel approach: broad context questions before specific feature questions.
- Use JTBD probing: When did you last...? What were you trying to accomplish? What happened next?
- Avoid leading questions, hypotheticals, and yes/no questions.
Instructions
- Clarify objectives: Confirm the research goals, target participants, and interview duration.
- Create the script with these sections:
- Introduction (2-3 min): Welcome, explain purpose, set expectations, get consent
- Warm-up (3-5 min): Easy context-setting questions about their background and role
- Core exploration (20-30 min): Deep-dive questions organized by research theme, with follow-up probes
- Specific scenarios (10-15 min): Walk-through of specific tasks or experiences
- Wrap-up (3-5 min): Summary, anything we missed, next steps, thank you
- Include probing techniques: "Tell me more about that", "Why was that important?", "What happened next?"
- Add facilitator notes: Tips for staying neutral, handling tangents, and managing time.
- Think step by step. Present the script in a ready-to-use format.
Question Quality Guardrails
Ensure all questions are non-leading. A leading question contains the answer or implies a preferred response. Replace any question that assumes sentiment, behaviour, or outcome.
| Leading (avoid) | Non-leading (use) |
|---|---|
| "Was that frustrating?" | "How did you feel about that?" |
| "Did you find it easy?" | "How easy or difficult was that for you?" |
| "Did you like the feature?" | "What did you notice about that feature, if anything?" |
| "Would you use this?" | "How would you use this in your work, if at all?" |
Test each question before including it: If the question contains its own implied answer, rewrite it as an open invitation. If the question can be answered with yes or no, extend it ("...and why?").
Further Reading
- Interviewing Users — Steve Portigal
- Just Enough Research — Erika Hall
Related skills
More from owl-listener/designer-skills and the wider catalog.
jobs-to-be-done
Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations. Use when reframing product decisions around user motivations rather than features.
journey-map
Create an end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas. Use when mapping the full user experience for a product, feature, or service.
layout-grid
Define responsive layout grid systems with columns, gutters, margins, and breakpoint behavior.
loading-states
Design loading, skeleton, and progressive content reveal patterns.
metrics-definition
Define UX metrics and KPIs that connect design decisions to measurable business and user outcomes.
micro-interaction-spec
Specify micro-interactions with trigger, rules, feedback, and loop/mode definitions.