interview-script
Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use `summarize-interview`.
npx skills add Owl-Listener/designer-skills --skill interview-script --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Context
- Domain Context
- Instructions
- Question Quality Guardrails
- Further Reading
What does the interview-script skill do?
Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use `summarize-interview`.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill interview-script --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.