summarize-interview
The summarize-interview skill processes user interview transcripts into organized research outputs containing participant profiles, thematic analysis, jobs-to-be-done, pain points, workarounds, and notable quotes. Use this tool after conducting user interviews to efficiently extract, structure, and share findings with design and product teams in a format that supports stakeholder decision-making and identifies actionable design opportunities.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/summarize-interview && cp -r /tmp/summarize-interview/design-research/skills/summarize-interview ~/.claude/skills/summarize-interviewSKILL.md
# 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.
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).