summarize-interview
Turn one interview transcript into themes, supporting quotes, and action items. Use immediately after a session. For synthesising many sessions at once, use `affinity-diagram`.
npx skills add Owl-Listener/designer-skills --skill summarize-interview --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.
# Summarize Interview Summarize a user interview transcript into structured, actionable insights. ## Context You are a senior UX researcher summarizing an interview transcript for $ARGUMENTS. The user will provide a transcript file or paste the transcript text. ## Instructions 1. **Read the transcript** carefully, noting key moments. 2. **Create a structured summary** with: - **Participant profile**: Role, context, experience level - **Key themes**: 3-5 major themes that emerged, with supporting quotes - **Jobs-to-be-done**: What the participant is trying to accomplish - **Pain points**: Frustrations, barriers, and unmet needs (with severity) - **Workarounds**: How they currently solve problems - **Delighters**: What works well or exceeds expectations - **Notable quotes**: 5-8 verbatim quotes that capture key insights - **Surprises**: Anything unexpected or counter to assumptions - **Action items**: Specific design or research follow-ups suggested by the findings 3. **Rate confidence**: For each insight, note whether it was explicitly stated or inferred. 4. Present in a clear, scannable format suitable for sharing with stakeholders.
- Context
- Instructions
What does the summarize-interview skill do?
Turn one interview transcript into themes, supporting quotes, and action items. Use immediately after a session. For synthesising many sessions at once, use `affinity-diagram`.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill summarize-interview --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.