Interview Script
- 944 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
interview-script is a Claude Code skill that generates structured, bias-reduced user interview scripts with warm-up, exploration, and wrap-up sections for developers and designers who need JTBD insights before building f
About
interview-script is a UX research skill from owl-listener/designer-skills that produces structured qualitative interview scripts using open-ended questions, funnel sequencing, and Steve Portigal-style interviewing principles. The skill reads personas, research goals, and product context when provided, then outputs warm-up, core exploration, and wrap-up sections designed to surface motivations, behaviors, and mental models. Developers and designers reach for interview-script when planning discovery interviews, ensuring consistent conversations across sessions, and converting ambiguous feature ideas into evidence-backed user needs before writing specs or code.
- Produces five-section interview script: Introduction, Warm-up, Core exploration, Specific scenarios, and Wrap-up
- Follows Steve Portigal and JTBD methodologies with open-ended non-leading questions
- Automatically incorporates any provided personas, research goals or product context files
- Includes built-in follow-up probes and funnel structure from broad context to specific tasks
- Delivers ready-to-use script with suggested timing per section
Interview Script by the numbers
- 944 all-time installs (skills.sh)
- +42 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #502 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill interview-scriptAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 944 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you write a bias-free user interview script for discovery?
Generate consistent, bias-free user interview scripts that uncover real motivations and JTBD insights before building features.
Who is it for?
Product-minded developers and designers preparing qualitative discovery interviews before scoping or prototyping new features.
Skip if: Quantitative survey design, usability test task scripts, or teams that already have a finalized research protocol and only need analysis.
When should I use this skill?
A developer or designer asks to prepare user interview questions, discovery scripts, or JTBD research conversations before building.
What you get
Structured interview script with warm-up, core questions, wrap-up, and funnel-ordered JTBD prompts.
- user interview script
- JTBD question funnel
- session facilitation outline
Files
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.
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
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Choose interview-script for pre-build qualitative discovery; use analytics or survey skills when validating with quantitative data instead.
FAQ
What sections does interview-script generate?
interview-script from owl-listener/designer-skills creates a structured script with warm-up, core exploration, and wrap-up sections. Questions follow a funnel from broad context toward specific motivations and behaviors.
Can interview-script use existing personas?
interview-script reads user-provided personas, research goals, and product context files before drafting questions. That keeps interview prompts aligned with defined audience segments and study objectives.
Is Interview Script safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.