mcpField
S
summarize-interview

summarize-interview

github.com/owl-listenerDesign & UI3.1k2.1k installsUpdated 8w ago
Repository

About summarize-interview

A UX research skill that turns an interview transcript into a structured summary for stakeholders. It organizes themes, participant goals, pain points, workarounds, quotes, and follow-up actions, while distinguishing explicit findings from inferences.

Key features

  1. 01Participant profile and key themes
  2. 02Jobs-to-be-done and pain points
  3. 03Workarounds and delighters
  4. 04Verbatim quotes and surprises
  5. 05Action items and confidence ratings

Use cases

  1. 01Summarizing user interview transcripts
  2. 02Sharing research findings with stakeholders
  3. 03Identifying design and research follow-ups

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill summarize-interview

After installing, type/summarize-interviewin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported