← ClaudeAtlas

insight-processorlisted

Turns raw user research into a structured insight matrix mapping user statements to problem statements. Reads interview transcripts, call recording transcripts, written call notes, or survey verbatims and distills them into themes, problem statements, verbatim quotes, severity, and frequency — instead of manual tagging in a spreadsheet. Use whenever the user uploads or references interview transcripts, call notes, user interviews, customer feedback, or qualitative research, or asks to "synthesize," "find themes in," "pull insights from," "tag," "code," or "make sense of" research data — even without saying "insight matrix." Also use for casual phrasings like "what are customers complaining about" or "what's coming up across these calls," or requests to find pain points, recurring complaints, or unexpected/workaround user behaviors. Handles a single transcript or a batch from the same project, offering a combined cross-interview matrix once each is processed.
pruthivim/claude-pm-skills · ★ 1 · Data & Documents · score 64
Install: claude install-skill pruthivim/claude-pm-skills
# Insight Processor Turn raw, messy interview transcripts or notes into a structured insight matrix that a PM or researcher can hand straight to stakeholders. ## Workflow ### 1. Identify inputs Check what was provided: one file, or several files from the same research project (e.g. multiple interviews for one study). If it's unclear how many files or which ones belong to the same project, ask before proceeding. ### 2. Read each file Read the full transcript or notes file. If it's not in your context (only a path was given), use the file-reading skill's guidance to read it properly rather than guessing from the filename. Note whether interviewees are identified (name, "P1"/"P2", role, segment). If so, carry that identifier through to the matrix. If not, use a generic placeholder like "Interviewee" or the filename. ### 3. Extract insights against the theme taxonomy Use this starter taxonomy, but treat it as a hybrid seed list, not a fixed one — if something important doesn't fit, create a new theme rather than forcing it into the wrong bucket: - Onboarding friction - Pricing / value confusion - Feature discoverability - Trust & credibility concerns - Workflow interruption / context-switching - Support & documentation gaps - Performance / reliability complaints - Unexpected / workaround behavior (user doing something the product wasn't designed for) For each distinct insight in the transcript: - Assign it to a theme (existing or new) - Write a **problem statement**: a