New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Synthesises user interview transcripts into structured

User Interview Synthesis Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

User Interview Synthesis Skill cover

Synthesises user interview transcripts into structured research findings. Use when asked to analyse interview notes, synthesise qualitative research, identify themes from interviews, or turn raw interview data into actionable product…

---
name: user-interview-synthesis
description: "Synthesises user interview transcripts into structured research findings. Use when asked to analyse interview notes, synthesise qualitative research, identify themes from interviews, or turn raw interview data into actionable product insights. Produces a themed synthesis with supporting quotes per theme, 'so what' implications, and recommended next steps. For mixed sources beyond interviews (surveys, tickets, feedback) use user-research-synthesis instead."
---

# User Interview Synthesis Skill

Transform raw interview transcripts into a structured synthesis document that surfaces themes, pain points, and actionable insights.

## Required Inputs

Ask the user for these if not provided:
- **Interview transcripts or notes** (even rough notes work)
- **Number of participants and their profiles** (role, company size, context)
- **Research questions** (what was the study trying to answer?)
- **Date range** of research (for context)

## Process

Overview

Transform raw interview transcripts into a structured synthesis document that surfaces themes, pain points, and actionable insights.

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill user-interview-synthesis -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/user-interview-synthesis
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/e7cf60b900787f935ad5/user-interview-synthesis.zip" -OutFile "$env:TEMP\user-interview-synthesis.zip"; Expand-Archive "$env:TEMP\user-interview-synthesis.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP 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.md5.0 KB
  • references/2 files · 11.4 KB
  • templates/1 file · 974 B
Read the files here
mohitagw15856/f6ca7934 files
SKILL.md
Show the full text79 lines

User Interview Synthesis Skill

Transform raw interview transcripts into a structured synthesis document that surfaces themes, pain points, and actionable insights.

Required Inputs

Ask the user for these if not provided:

  • Interview transcripts or notes (even rough notes work)
  • Number of participants and their profiles (role, company size, context)
  • Research questions (what was the study trying to answer?)
  • Date range of research (for context)

Process

  1. Read all provided transcripts fully before drawing conclusions
  2. Identify recurring themes (minimum 3 mentions to qualify as a theme)
  3. Categorize findings into: Pain Points, Workflow Insights, Feature Requests, Delight Moments
  4. Select 2-3 verbatim quotes per theme that best represent the pattern
  5. Draft "So What" implications for each theme — what does this mean for the product?
  6. Validate — Confirm every theme has quotes from at least 3 participants. Flag any insight resting on fewer as low-confidence.

Output Structure

Research Synthesis: [Study Name]

Participants: [n] Date Range: [dates] Research Questions: [list]

Theme 1: [Theme Name]
  • Summary (2-3 sentences)
  • Supporting quotes (from at least 3 participants)
  • Implication for product

[Repeat for each theme]

Low-Confidence Signals (1-2 participants only)

[Findings worth tracking but not acting on yet — note what further research would confirm or deny]

[Specific, actionable recommendations based on findings]

Deeper Materials

This skill ships with support files — use them when they are available:

  • references/coding-transcripts.md — Coding Interview Transcripts Without Losing the Signal. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.
  • templates/per-session-capture.md — a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.

Scoring Rubric (0–40)

Score any output of this skill before handing it over; 32+ is ship-quality.

Dimension 0 5 10
Evidence traceability Themes asserted with no quotes or participant attribution Most themes carry quotes, but some rest on 1–2 participants or unattributed paraphrase Every theme carries verbatim quotes from ≥3 distinct participants, with frequency counts ("6 of 9") consistent with the roster
Implication actionability Implications restate the observation ("users find X frustrating") Implications gesture at direction but name no decision, owner, or change Every implication enables a specific product decision someone could act on this quarter
Contradiction honesty All findings conveniently support the sponsor's hypothesis; inconvenient data absent Contradictory evidence present but buried or softened; both-ways quotes trimmed to the helpful half Findings that contradict the hypothesis are surfaced prominently, and ambiguous quotes are kept whole with the tension flagged
Signal separation & question coverage Single-source anecdotes mixed into main themes; research questions ignored Low-confidence signals segregated but with no follow-up path, or one research question left unaddressed Every 1–2-participant signal sits in its own section with the cheap test that would confirm it, and every research question gets an explicit answer — including "inconclusive"

Quality Checks

  • Every theme is supported by quotes from at least 3 participants
  • Implications connect to specific product decisions, not just observations
  • Researcher bias check: no leading language, findings don't all support one hypothesis
  • Single-source signals are flagged separately, not mixed into main themes
  • Research questions from the study brief are each addressed (even if the answer is "inconclusive")

Anti-Patterns

  • Do not mix single-source signals into main themes — insights cited by only one participant must be flagged separately
  • Do not write implications that are observations restated rather than product decisions enabled
  • Do not include themes that only support the project hypothesis — contradictory findings must be surfaced, not omitted
  • Do not present findings without quotes — every theme requires verbatim evidence from at least 3 participants
  • Do not leave research questions unanswered — each question from the study brief must be explicitly addressed, even if the answer is inconclusive
1---
2name: user-interview-synthesis
3description: "Synthesises user interview transcripts into structured research findings. Use when asked to analyse interview notes, synthesise qualitative research, identify themes from interviews, or turn raw interview data into actionable product insights. Produces a themed synthesis with supporting quotes per theme, 'so what' implications, and recommended next steps. For mixed sources beyond interviews (surveys, tickets, feedback) use user-research-synthesis instead."
4---
5 
6# User Interview Synthesis Skill
7 
8Transform raw interview transcripts into a structured synthesis document that surfaces themes, pain points, and actionable insights.
9 
10## Required Inputs
11 
12Ask the user for these if not provided:
13- **Interview transcripts or notes** (even rough notes work)
14- **Number of participants and their profiles** (role, company size, context)
15- **Research questions** (what was the study trying to answer?)
16- **Date range** of research (for context)
17 
18## Process
191. Read all provided transcripts fully before drawing conclusions
202. Identify recurring themes (minimum 3 mentions to qualify as a theme)
213. Categorize findings into: Pain Points, Workflow Insights, Feature Requests, Delight Moments
224. Select 2-3 verbatim quotes per theme that best represent the pattern
235. Draft "So What" implications for each theme — what does this mean for the product?
246. **Validate** — Confirm every theme has quotes from at least 3 participants. Flag any insight resting on fewer as low-confidence.
25 
26## Output Structure
27 
28### Research Synthesis: [Study Name]
29**Participants:** [n]
30**Date Range:** [dates]
31**Research Questions:** [list]
32 
33#### Theme 1: [Theme Name]
34- Summary (2-3 sentences)
35- Supporting quotes (from at least 3 participants)
36- Implication for product
37 
38[Repeat for each theme]
39 
40#### Low-Confidence Signals (1-2 participants only)
41[Findings worth tracking but not acting on yet — note what further research would confirm or deny]
42 
43#### Recommended Next Steps
44[Specific, actionable recommendations based on findings]
45 
46## Deeper Materials
47 
48This skill ships with support files — use them when they are available:
49 
50- **`references/coding-transcripts.md`** — Coding Interview Transcripts Without Losing the Signal. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.
51- **`templates/per-session-capture.md`** — a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.
52 
53## Scoring Rubric (0–40)
54 
55Score any output of this skill before handing it over; 32+ is ship-quality.
56 
57| Dimension | 0 | 5 | 10 |
58|---|---|---|---|
59| Evidence traceability | Themes asserted with no quotes or participant attribution | Most themes carry quotes, but some rest on 1–2 participants or unattributed paraphrase | Every theme carries verbatim quotes from ≥3 distinct participants, with frequency counts ("6 of 9") consistent with the roster |
60| Implication actionability | Implications restate the observation ("users find X frustrating") | Implications gesture at direction but name no decision, owner, or change | Every implication enables a specific product decision someone could act on this quarter |
61| Contradiction honesty | All findings conveniently support the sponsor's hypothesis; inconvenient data absent | Contradictory evidence present but buried or softened; both-ways quotes trimmed to the helpful half | Findings that contradict the hypothesis are surfaced prominently, and ambiguous quotes are kept whole with the tension flagged |
62| Signal separation & question coverage | Single-source anecdotes mixed into main themes; research questions ignored | Low-confidence signals segregated but with no follow-up path, or one research question left unaddressed | Every 1–2-participant signal sits in its own section with the cheap test that would confirm it, and every research question gets an explicit answer — including "inconclusive" |
63 
64## Quality Checks
65 
66- [ ] Every theme is supported by quotes from at least 3 participants
67- [ ] Implications connect to specific product decisions, not just observations
68- [ ] Researcher bias check: no leading language, findings don't all support one hypothesis
69- [ ] Single-source signals are flagged separately, not mixed into main themes
70- [ ] Research questions from the study brief are each addressed (even if the answer is "inconclusive")
71 
72## Anti-Patterns
73 
74- [ ] Do not mix single-source signals into main themes — insights cited by only one participant must be flagged separately
75- [ ] Do not write implications that are observations restated rather than product decisions enabled
76- [ ] Do not include themes that only support the project hypothesis — contradictory findings must be surfaced, not omitted
77- [ ] Do not present findings without quotes — every theme requires verbatim evidence from at least 3 participants
78- [ ] Do not leave research questions unanswered — each question from the study brief must be explicitly addressed, even if the answer is inconclusive
79 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with user-interview-synthesis

User Interview Synthesis Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
User Interview Synthesis Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

User Interview Synthesis Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
User Interview Synthesis Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/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 starsSkillExtracting first-party expertise from a subject-matterExpert interviewinhouseseo/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 starsSkillStart of the UGC pipeline for persona researchPersona & ScriptTheMattBerman/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 starsSkillTell us who you need answers from and what you're missingTo questionnairemattpocock/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 starsSkillExtracts what the user actually wants instead of what theyInterview meaddyosmani/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 starsSkillMarketes psychology & mental modelsMarketing Psychology & Mental Modelscoreyhaines31/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 mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/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 starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars