# Summarize Interview

Turn one interview transcript into themes, supporting quotes, and action items.

- Repository: https://github.com/Owl-Listener/designer-skills (3196 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-05
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Owl-Listener/designer-skills --skill summarize-interview -g -a claude-code -y`
Codex: `npx skills add Owl-Listener/designer-skills --skill summarize-interview -g -a codex -y`
Cursor: `npx skills add Owl-Listener/designer-skills --skill summarize-interview -g -a cursor -y`
Gemini CLI: `npx skills add Owl-Listener/designer-skills --skill summarize-interview -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Owl-Listener/designer-skills`

## Description

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`.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.