Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to extract and communicate findings across participants. Distinct from foundation-meeting-recap, which summarizes one internal meeting for its attendees; this skill aggregates research conversations into evidence-backed findings.
SkillScore67Maintained
Automatic
◆Product Management pack
Last verified 8/18/2026
What it changes
Passed 16 of 24 test cases with the skill, and 12 of 24 without it.
Without skill50%
With skill67%
Checks it passed that the model alone missed
Attributes every quote explicitly to a participant identifier
Connects each recommendation directly to a specific synthesized insight
Orders participant profile creation prior to theme identification and quote extraction
and 3 more in the full report
6 fixed10 passed either way6 still failing2 broke
Pass-rate lift
+17 pp
Tokens
+24%
Agent turns
0%
Response time
-39%
Model gemini-3.6-flashMeasured 8/18/2026v216 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
I spoke with 2 beta testing users yesterday about our new dashboard widget. Here are the transcripts for P1 and P2. Please synthesize these into a research synthesis document identifying key recurring user patterns across the study.
What was checked, without and with the skill
Checked
Without skill
With skill
Notes that identifying robust thematic patterns requires notes from at least 3 participants
Missed
Passed
case-08 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md80 lines3 files
Interview Synthesis
An interview synthesis transforms raw user research data into structured insights that drive product decisions. Rather than simply listing what participants said, a good synthesis identifies patterns across conversations, connects observations to underlying user needs, and translates findings into actionable recommendations.
When to Use
After completing a round of user interviews (typically 5+ participants)
Following customer discovery calls or sales feedback sessions
After usability testing sessions to consolidate observations
When stakeholders need a summary of research findings
Before ideation sessions to ground the team in user reality
When NOT to Use
You are summarizing one internal meeting for its attendees -> use foundation-meeting-recap
You need patterns across multiple meetings over time -> use foundation-meeting-synthesize
Your data is survey responses rather than interviews -> use measure-survey-analysis
The findings are synthesized and you are ready to frame the problem -> use define-problem-statement
You have synthesized findings and want to map them onto a customer's journey across stages and touchpoints -> use discover-journey-map
Instructions
When asked to synthesize interview findings, follow these steps:
Gather the Raw Material
Collect all interview notes, transcripts, or recordings. Ensure you have data from at least 3 participants to identify meaningful patterns. Note the research objective and methodology used.
Create Participant Profiles
Document each participant with relevant context: their role, segment, tenure, and any notable characteristics. This helps readers assess the representativeness of findings.
Identify Recurring Themes
Read through all notes and tag observations by topic. Look for themes that appear across multiple participants (ideally 3+). Distinguish between frequently mentioned topics and one-off comments.
Extract Meaningful Quotes
Capture 3-5 verbatim quotes per theme that powerfully illustrate the insight. Good quotes are specific, emotional, or particularly articulate. Always attribute quotes to participant IDs.
Synthesize into Insights
Transform themes into insight statements. An insight goes beyond observation ("users mentioned X") to interpretation ("users need Y because of Z"). Connect what you heard to why it matters.
Specialized skill for synthesizing qualitative user research into actionable insights. Analyzes interview transcripts, extracts patterns and themes, identifies pain points, creates affinity diagrams, and generates persona attributes from research data.
Close match
+43 pp pass-rate lift
Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach. Use at project kickoff, when taking over from another PM, or when resistance signals misalignment. For the update you send to those stakeholders, use foundation-stakeholder-update instead; this skill maps them, that one talks to them.