Interview Summarizer

Summarize interview

by phuryn · MIT license · ★ 26,557 on GitHub · updated Sep 14

Summarize interview cover

Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items. Use when processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview…

---
name: summarize-interview
description: "Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items. Use when processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview summaries."
---

## Summarize Customer Interview

Transform an interview transcript into a structured summary focused on Jobs to Be Done, satisfaction, and action items.

### Context

You are summarizing a customer interview for the product discovery of **$ARGUMENTS**.

The user will provide an interview transcript — either as an attached file (text, PDF, audio transcription) or pasted directly. Read any attached files first.

### Instructions

1. **Read the full transcript** carefully before summarizing.

Overview

Transform an interview transcript into a structured summary focused on Jobs to Be Done, satisfaction, and action items.

Manual install (npx, ZIP)
Claude Codenpx skills add phuryn/pm-skills --skill summarize-interview -g -a claude-code
Claude Code (degit)npx degit phuryn/pm-skills/pm-product-discovery/skills/summarize-interview#main ~/.claude/skills/summarize-interview
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md2.0 KB
Read SKILL.md here
phuryn/main1 file shown
SKILL.md
Show the full text54 lines
summarize-interview/SKILL.md54 lines · 2.0 KB

Summarize Customer Interview

Transform an interview transcript into a structured summary focused on Jobs to Be Done, satisfaction, and action items.

Context

You are summarizing a customer interview for the product discovery of $ARGUMENTS.

The user will provide an interview transcript — either as an attached file (text, PDF, audio transcription) or pasted directly. Read any attached files first.

Instructions
  1. Read the full transcript carefully before summarizing.

  2. Fill in the summary template below. Use "-" if information is unavailable. Replace numeric values with qualitative descriptions if needed (e.g., "not satisfied").

  3. Use clear, simple language — a primary school graduate should be able to understand the summary.

Output Template
**Date**: [Date and time of the interview]
**Participants**: [Full names and roles]
**Background**: [Background information about the customer]

**Current Solution**: [What solution they currently use]

**What They Like About Current Solution**:
- [Job to be done, desired outcome, importance, and satisfaction level]

**Problems With Current Solution**:
- [Job to be done, desired outcome, importance, and satisfaction level]

**Key Insights**:
- [Unexpected findings or notable quotes]

**Action Items**:
- [Date, Owner, Action — e.g., "2025-01-15, Paweł Huryn, Follow up with customer about pricing"]

Save the summary as a markdown document in the user's workspace.


Further Reading
1---
2name: summarize-interview
3description: "Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items. Use when processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview summaries."
4---
5 
6## Summarize Customer Interview
7 
8Transform an interview transcript into a structured summary focused on Jobs to Be Done, satisfaction, and action items.
9 
10### Context
11 
12You are summarizing a customer interview for the product discovery of **$ARGUMENTS**.
13 
14The user will provide an interview transcript — either as an attached file (text, PDF, audio transcription) or pasted directly. Read any attached files first.
15 
16### Instructions
17 
181. **Read the full transcript** carefully before summarizing.
19 
202. **Fill in the summary template** below. Use "-" if information is unavailable. Replace numeric values with qualitative descriptions if needed (e.g., "not satisfied").
21 
223. **Use clear, simple language** — a primary school graduate should be able to understand the summary.
23 
24### Output Template
25 
26```
27**Date**: [Date and time of the interview]
28**Participants**: [Full names and roles]
29**Background**: [Background information about the customer]
30 
31**Current Solution**: [What solution they currently use]
32 
33**What They Like About Current Solution**:
34- [Job to be done, desired outcome, importance, and satisfaction level]
35 
36**Problems With Current Solution**:
37- [Job to be done, desired outcome, importance, and satisfaction level]
38 
39**Key Insights**:
40- [Unexpected findings or notable quotes]
41 
42**Action Items**:
43- [Date, Owner, Action — e.g., "2025-01-15, Paweł Huryn, Follow up with customer about pricing"]
44```
45 
46Save the summary as a markdown document in the user's workspace.
47 
48---
49 
50### Further Reading
51 
52- [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate)
53- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
54 
View all files on GitHub →

Details

Updated
Sep 14, 2026
License
MIT
Stars on the repo
★ 26,557
Checked
Source
phuryn/pm-skills ↗
Creator
phuryn · 69 listings
View creator

Similar skills

See all →
Skill360 Feedback Surveymohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillExpert Knowledge Extractorinhouseseo/superseo-skills · by inhouseseoUse when extracting first-party expertise from a subject-matter expert before writing content. Produces a knowledge document of contrarian takes, specific examples, and surprising outcomes that AI can't fabricate.★ 353 GitHub starsSkillCreator Persona ResearcherTheMattBerman/scrollclaw · by TheMattBermanStart of the UGC pipeline for persona research, creator profiles, format selection, and scriptwriting. Use when the user is clearly asking for messaging work rather than broad full-pipeline orchestration.★ 71 GitHub starsSkillQuestionnaire Generatormattpocock/skills · by mattpocockTell us who you need answers from and what you're missing; get back a clean form you send them to fill in.★ 267k GitHub starsSkillIntent Interview Assistantaddyosmani/agent-skills · by addyosmaniExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.★ 98.7k GitHub starsSkillBehavioral Science for Marketingcoreyhaines31/marketingskills · by coreyhaines31When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.★ 51.1k GitHub stars

More from phuryn

SkillA/B Test Analyzerphuryn/pm-skills · by phurynAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.★ 26.6k GitHub starsSkillFeature Request Prioritizerphuryn/pm-skills · by phurynAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.★ 26.6k GitHub starsSkillAnsoff Matrix Generatorphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillAI Text Humanizerphuryn/work-humanizer · by phurynEdit AI-sounding text so it reads like a careful person wrote it, without changing what it says or commits to. Built for work writing where the wording matters: sales and marketing copy, support replies, HR and legal letters, emails, docs, release notes, posts, landing pages. Two modes. Rewrite: edit the text you are given. Interview: when a draft is AI-composed and thin, ask the writer 3-5 sharp questions and build the piece from their answers, in their words. Also writes from the writer's own notes or a voice-memo transcript. Calibrated on measured differences between human and AI writing.★ 110 GitHub starsSkillMarket Segment Identifierphuryn/pm-skills · by phurynIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.★ 26.6k GitHub starsSkillProduct Experiment Designerphuryn/pm-skills · by phurynDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.★ 26.6k GitHub stars