
Summarize Interview
- 925 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
summarize-interview is an agent skill that converts raw user interview transcripts into structured UX research summaries with participant profiles, themes, quotes, pain points, and action items for developers who need sc
About
summarize-interview is a Claude Code skill from owl-listener/designer-skills that guides an agent through senior UX-researcher-style synthesis of interview transcripts supplied as a file or pasted text. The workflow reads the full transcript, then produces a structured summary covering participant profile (role, context, experience level), key themes, supporting quotes, pain points, and action items. Developers and product engineers reach for summarize-interview right after user interviews when notes are long, inconsistent, or hard to share with a team. Instead of manually highlighting transcripts, the skill standardizes output so findings can feed roadmap discussions, PRDs, and design critiques without re-reading raw dialogue.
- Extracts 3-5 key themes with supporting quotes
- Identifies jobs-to-be-done, pain points with severity, workarounds, and delighters
- Surfaces 5-8 notable verbatim quotes plus surprises and action items
- Rates confidence for each insight as explicitly stated or inferred
- Delivers stakeholder-ready structured summary from transcript text or file
Summarize Interview by the numbers
- 925 all-time installs (skills.sh)
- +41 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #449 of 1,888 Design & UI/UX 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 summarize-interviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 925 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you summarize user interview transcripts into themes?
Turn raw user interview transcripts into structured, scannable insights with themes, quotes, pain points, and action items.
Who is it for?
Developers and PMs who just finished user interviews and need a consistent, shareable research summary without manual transcript markup.
Skip if: Teams that need live interview facilitation, survey quantitative analysis, or automated transcription from audio without a text transcript.
When should I use this skill?
A developer or PM provides a user interview transcript file or pasted text and asks for themes, quotes, pain points, or action items from the session.
What you get
Structured interview summary with participant profile, key themes, verbatim quotes, pain points, and prioritized action items.
- structured interview summary
- themed pain-point list
- prioritized action items
By the numbers
- Produces five summary sections: participant profile, key themes, quotes, pain points, and action items
- Readme specifies key themes as a required structured output field per interview
Files
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.
Related skills
How it compares
Use summarize-interview for post-session transcript synthesis; pair with transcription tools first when you only have audio recordings.
FAQ
What does summarize-interview output from a transcript?
summarize-interview outputs a structured UX research summary with participant profile, key themes, supporting quotes, pain points, and action items. Developers supply a transcript file or pasted text; the skill applies a senior-researcher template so findings are scannable for pr
When should developers use summarize-interview?
Developers and PMs should use summarize-interview immediately after conducting user interviews, when raw transcripts or notes need conversion into shareable themes and next steps. The skill fits discovery and validation work before feature scoping or implementation.
What input does summarize-interview require?
summarize-interview requires a user interview transcript provided as a file path or pasted text. The skill reads the full dialogue, notes key moments, and synthesizes role, context, and experience level into a participant profile alongside themed findings.
Is Summarize Interview safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.