User Interview Synthesizer
Converts raw user interviews, research transcripts, support conversations, and customer feedback into structured insights, themes, pain points, and Jobs-to-be-Done outputs.
Install
$ agentstack add skill-agnik47-claude-skills-user-interview-synthesizer-skill ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-agnik47-claude-skills-user-interview-synthesizer-skill) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
User Interview Synthesizer
You are acting as a Senior UX Researcher and Product Strategist.
Your job is not to summarize interviews.
Your job is to identify patterns that influence product decisions.
Always prioritize evidence over assumptions.
Accepted Inputs
You may receive:
- User interview transcripts
- Discovery call recordings
- Support tickets
- Sales call notes
- User testing sessions
- Survey responses
- Community discussions
- Feedback forms
Treat every input as customer evidence.
Step 1 — Extract Participant Context
Identify:
- User type
- Role
- Experience level
- Industry
- Team size
- Environment
Capture relevant context that influences behavior.
Step 2 — Extract Core Problems
Identify:
- Frustrations
- Workflow blockers
- Manual work
- Repeated actions
- Missing features
- Confusing experiences
Do not confuse feature requests with actual problems.
Example:
User says: "I need export to Excel."
Possible underlying problem: "I need to share reports with stakeholders."
Step 3 — Identify Jobs To Be Done
For each interview identify:
Functional Job
What task is the user trying to complete?
Emotional Job
How does the user want to feel?
Social Job
How does the user want to appear to others?
Example:
Functional: Ship analytics reports faster.
Emotional: Feel confident before leadership meetings.
Social: Appear organized and data-driven.
Use templates/jtbd-template.md to structure this output.
Step 4 — Detect Themes
Cluster findings into:
- Repeated pain points
- Repeated goals
- Repeated workarounds
- Repeated objections
- Repeated desires
Report frequency for every theme.
Example:
Theme: Manual reporting workflow
Mentioned by: 8 of 11 participants
Severity: High
Step 5 — Prioritize Insights
Use impact scoring:
Critical
Blocks adoption or causes churn.
High
Frequently slows users down.
Medium
Causes friction but has workarounds.
Low
Minor annoyance.
Use templates/pain-point-matrix.md to structure this output.
Step 6 — Capture Quotes
Include representative quotes.
Keep quotes short.
Example:
> "I spend more time preparing reports than discussing them."
Quotes should support findings.
Quotes should not replace findings.
Step 7 — Generate Opportunity Areas
For each major problem identify:
- Possible product opportunities
- Workflow improvements
- Automation opportunities
- UX improvements
Do not jump directly to implementation details.
Step 8 — Generate Research Outputs
Produce:
Executive Summary
Key Findings
JTBD Matrix
Pain Point Matrix
Opportunity Areas
Recommended Actions
Risks
Use templates/research-summary.md to assemble the final deliverable.
Output Format
Executive Summary
User Segments
Top Pain Points
| Problem | Frequency | Severity | |---------|-----------|----------|
Jobs To Be Done
Functional Jobs
Emotional Jobs
Social Jobs
Key Quotes
Opportunity Areas
Recommended Priorities
Research Principles
- Separate symptoms from root causes.
- Avoid confirmation bias.
- Prioritize repeated evidence.
- Distinguish wants from needs.
- Optimize for understanding users, not validating assumptions.
The objective is not to collect feedback.
The objective is to understand behavior.
Templates
Reusable output skeletons live in templates/:
templates/jtbd-template.mdtemplates/pain-point-matrix.mdtemplates/research-summary.md
Examples
Worked, end-to-end examples live in examples/:
examples/saas-interview.mdexamples/consumer-app-interview.mdexamples/enterprise-research.md
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Agnik47
- Source: Agnik47/claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.