Interview Script
Generate a timed, funnel-structured user interview script before talking to customers so discovery stays consistent and non-leading.
Overview
Interview Script is an agent skill most often used in Idea (also Validate scope and Grow support) that produces a structured qualitative interview script with warm-up, exploration, scenarios, and wrap-up.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill interview-scriptWhat is this skill?
- Four script blocks: Introduction, Warm-up, Core exploration, Specific scenarios, and Wrap-up with minute budgets
- Funnel approach: broad context before feature-specific questions; JTBD probes (when did you last…, what happened next)
- Explicit guardrails: avoid leading questions, hypotheticals, and yes/no questions
- Reads user-supplied personas, research goals, and product context files before drafting
- Step 1 clarifies objectives, participants, and interview duration before writing the script
- Script sections include Introduction (2–3 min), Warm-up (3–5 min), Core exploration (20–30 min), Specific scenarios (10–
Adoption & trust: 559 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to talk to users but only have a vague question list, so interviews risk being inconsistent, leading, or too shallow to inform product decisions.
Who is it for?
Indie founders doing their own discovery on a new product, feature area, or positioning shift before writing a spec.
Skip if: Quantitative surveys, unmoderated usability tests only, or contexts where you already have a locked spec and only need QA test cases.
When should I use this skill?
Preparing for user research interviews to ensure consistent, insightful conversations with warm-up, core exploration, and wrap-up.
What do I get? / Deliverables
You receive a timed, theme-organized interview script with probes and consent-friendly intro so each session yields comparable insights for scope and positioning.
- Full interview script with themed questions and follow-up probes
- Consent-friendly introduction and timed section outline
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Primary shelf is Idea because interviews validate problems and mental models before you commit to build scope. Research subphase fits qualitative discovery—Portigal-style interviews, JTBD probes, and theme-based exploration—not wireframing.
Where it fits
Draft a 45-minute script to learn how solo developers choose AI coding tools before you pick a niche.
Create warm-up and core themes aligned to a persona file to clarify who feels the pain most acutely.
Run scenario walk-throughs on a prototype workflow to decide which v1 features survive cut-down.
Interview power users about recent support friction to prioritize lifecycle fixes without guessing.
How it compares
Structured research script generator, not a generic brainstorming chat or a analytics dashboard skill.
Common Questions / FAQ
Who is interview-script for?
Solo builders and small teams running qualitative user interviews who want Portigal- and JTBD-informed scripts without a dedicated researcher.
When should I use interview-script?
In Idea research before committing to a build; in Validate scope when you need evidence from live conversations; optionally in Grow support when exploring why users struggle or churn.
Is interview-script safe to install?
It is documentation-driven research guidance; check the Security Audits panel on this page and avoid pasting sensitive participant PII into prompts you do not control.
SKILL.md
READMESKILL.md - Interview Script
# 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 1. **Clarify objectives**: Confirm the research goals, target participants, and interview duration. 2. **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 3. **Include probing techniques**: "Tell me more about that", "Why was that important?", "What happened next?" 4. **Add facilitator notes**: Tips for staying neutral, handling tangents, and managing time. 5. Think step by step. Present the script in a ready-to-use format. ## Further Reading - Interviewing Users — Steve Portigal - Just Enough Research — Erika Hall