Individual skill

interview-synthesis

Turn a pile of interview notes into findings that survive scrutiny — the code-then-theme pass, the counting discipline (how many actually said it), the quote selection that illustrates instead of cherry-picks, and the confidence lines a small sample earns. Use when asked synthesize these user/customer/exit interviews, what did we actually learn from the calls, turn 12 transcripts into insights, or are these themes real. Produces the coded themes with counts, the divergences preserved, the illustrative quotes, and the claims sized to the sample.

skills/interview-synthesis/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Interview Synthesis Skill

Interview piles get "synthesized" two bad ways: the highlight reel (the quotes that confirmed what the team hoped) and the mush ("users want simplicity" — twelve hours of conversation flattened into a poster). Honest synthesis is mechanical before it's interpretive: code the notes (what did each person actually say, tagged), count the themes (a theme is something *multiple* people said — with the number attached), preserve the divergences (the two dissenters are data, not noise), and size every claim to the sample — twelve interviews support "we repeatedly heard," never "users want."

> **Not quite this?** Use `user-interview-synthesis` when the interviews are product-discovery research with users.

## What This Skill Produces

- **The coded pass** — each interview's statements tagged to emerging codes, traceable back to the speaker
- **The theme table** — themes with counts (7/12 raised unprompted; 3 more agreed when asked — the prompted/unprompted split matters)
- **The divergence report** — who disagreed with each theme and why; the outliers examined, not deleted
- **The claims, sample-sized** — findings phrased at what N interviews can carry, with the quotes that illustrate honestly

## Required Inputs
Back to top