Skip to main content
affpapa.org
RU EN
skill CX Codex

summarize-interview · owl-listener — Claude Code skill: what it does, how to install

Turns a single interview transcript into themes, quotes and follow-up tasks, in a format you can hand to stakeholders.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add Owl-Listener/designer-skills --skill summarize-interview -a claude-code
Open on GitHub

What summarize-interview does

The skill reads one transcript and fills in a fixed set of sections: who the participant was, the main themes with quotes attached, the jobs they were trying to get done, pain points graded by severity, workarounds, what delighted them, quotes worth keeping, surprises and follow-up tasks.

It also tags every insight as either stated by the participant or inferred by the model. That line matters when you reopen the summary weeks later and need to know which parts came straight from the transcript.

Feed it a transcript file or paste the text in; there is nothing to analyse without one. It handles a single session. Synthesising several interviews at once is the job of affinity-diagram from the same collection.

What it helps with

  • sort a long transcript into themes with supporting quotes
  • pull quotes you can paste into a report
  • mark which findings were stated outright and which you inferred
  • log pain points with a severity rating
  • get follow-up tasks while the session is still fresh

Example prompts for the agent

  • Summarize interview-07.md into themes, quotes, pain points and action items.
  • Go through this transcript and note for each finding whether the participant said it or you inferred it.
  • What surprised us in this interview, compared with our assumptions?

How to install summarize-interview

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill summarize-interview -a claude-code

2Manually: put the files in place

~/.claude/skills/summarize-interview/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/summarize-interview/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about summarize-interview

How do I install summarize-interview in Claude Code?

Run npx skills add Owl-Listener/designer-skills --skill summarize-interview -a claude-code. The skill lands at ~/.claude/skills/summarize-interview/SKILL.md.

What does summarize-interview do?

It reads one interview transcript and builds a structured summary: themes, quotes, jobs-to-be-done, pain points, workarounds and action items. Each insight is flagged as stated or inferred.

How is it different from affinity-diagram?

This one covers a single session. To combine several interviews, the same collection has affinity-diagram.

Source text

SKILL.md · MIT 
---
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.

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →

summarize-interview by other authors comes first.

summarize-interview phuryn This skill transforms an interview transcript into a structured report with Jobs to Be Done, satisfaction signals, and action items. Saves time parsing recordings and helps organize insights for product discovery. CX Codex +1 2,800installs frontend-design official anthropics This skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. 1,025,790installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. 1,424,476installs design-taste-frontend Leonxlnx This skill directs the design of public pages and work screens, then checks the result in a browser through screenshots. Use it when an interface feels generic or unfinished. CX Codex +1 678,700installs prototype Matt Pocock Creates throwaway prototypes for checking state logic or exploring UI before committing the decision to the main codebase. 986,201installs grilling Matt Pocock Stress-test a plan, decision, or idea through structured rounds of questions. Use it when you need to expose assumptions before acting. 979,543installs codebase-design Matt Pocock This skill helps design modules with small interfaces and hidden complexity. Use it when refactoring code, choosing a seam, or making tests easier to write. 850,344installs

From the same set111

critique-visual-hierarchy This skill reviews a rendered screen across four dimensions and tells you where the eye actually lands. Useful when attention goes to the wrong place. CX Codex +1 2,000installs click-test-plan Turns a findability question into a test plan: where users click first and whether they locate items in your navigation. Useful when a design is ready but untested. CX Codex +1 2,000installs design-sprint-plan Plans structured design sprints to move from a challenge statement to a tested prototype in days. Ideal when you need to compress discovery work into a single week. CX Codex +1 2,000installs design-system-adoption Builds an adoption strategy and enablement materials when teams are bypassing an existing design system. It helps plan education, migration support and measurement. CX Codex +1 2,000installs team-workflow Designs an operating cadence for design teams, covering task tracking, regular rituals, and developer handoff. Helpful when day-to-day design collaboration lacks structure. CX Codex +1 2,000installs opportunity-framework Turns a pile of possible improvements into a ranked roadmap using impact-effort and RICE. Handy when ideas outnumber capacity. CX Codex +1 2,000installs design-review-process A skill that sets four review gates for design work, from concept to implementation QA. Useful when things ship without a consistent review step. CX Codex +1 2,000installs north-star-vision Articulates a long-horizon product vision across 1-year, 2-3 year, and 5+ year horizons. Useful when a team lacks a clear strategic direction. CX Codex +1 2,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor