PluginBench
Skill
Pass
Audit score 90

summarize-interview

owl-listener/designer-skills

Turn interview transcripts into structured themes, quotes, and action items for immediate research insights.

What is summarize-interview?

Summarize a single user interview transcript into organized themes, supporting quotes, pain points, and next steps. Use this immediately after conducting a session to capture key insights while the conversation is fresh. For synthesizing patterns across multiple interviews, use the affinity-diagram skill instead.

  • Extract participant profile, role, and context
  • Identify 3–5 major themes with supporting verbatim quotes
  • Surface jobs-to-be-done, pain points, and workarounds
  • Highlight delighters and unexpected findings
  • Generate specific design and research action items
  • Rate confidence level (explicit vs. inferred) for each insight

How to install summarize-interview

npx skills add https://github.com/owl-listener/designer-skills --skill summarize-interview
Claude Code
Cursor
Windsurf
Cline

How to use summarize-interview

  1. 1.Provide the interview transcript (paste text or reference a file)
  2. 2.The skill will analyze the transcript and structure findings
  3. 3.Review the generated summary for accuracy and completeness
  4. 4.Share the output with your team or use insights to inform design decisions
  5. 5.Reference action items for follow-up research or design work

Use cases

Good for
  • Summarize a customer discovery interview within hours of the session
  • Prepare interview findings for stakeholder review or design critique
  • Identify follow-up research questions or design hypotheses to test
  • Document pain points and unmet needs for product roadmap input
  • Extract quotes for presentations or research reports
Who it's for
  • UX researchers conducting user interviews
  • Product managers gathering customer feedback
  • Design teams synthesizing research findings
  • User researchers preparing insights for stakeholders

summarize-interview FAQ

What format should the interview transcript be in?

Plain text, markdown, or a pasted transcript. The skill will parse any readable format.

Can I use this for multiple interviews at once?

No. This skill is designed for a single interview. Use the affinity-diagram skill to synthesize patterns across many sessions.

How long should the interview be?

Works best with 30–90 minute interviews. Longer sessions may produce longer summaries; very short clips may lack sufficient depth.

Will the summary include direct quotes?

Yes. The skill extracts 5–8 verbatim quotes that best capture key insights and surprises.

How do I know if an insight is reliable?

The skill rates confidence for each finding, noting whether it was explicitly stated by the participant or inferred from context.

Full instructions (SKILL.md)

Source of truth, from owl-listener/designer-skills.


name: summarize-interview 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.

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.