Research Synthesis
Synthesize user research into themes, insights, and recommendations. Use when you have interview transcripts, survey results, usability test notes, support tickets, or NPS responses that need to be distilled into patterns, user segments, and prioritized next steps.
$ npx promptcreek add research-synthesisAuto-detects your installed agents and installs the skill to each one.
What This Skill Does
The research synthesis skill analyzes user research data to extract actionable insights. It's designed for user researchers, product managers, and designers who need to understand user needs and identify opportunities. It synthesizes various data types like interviews, surveys, and usability tests.
When to Use
- Synthesize interview transcripts.
- Analyze survey results.
- Summarize usability test findings.
- Identify key themes from user feedback.
- Generate insights and opportunities.
- Create user segment profiles.
Key Features
Installation
$ npx promptcreek add research-synthesisAuto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.
View Full Skill Content
/research-synthesis
> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Synthesize user research data into actionable insights. See the user-research skill for research methods, interview guides, and analysis frameworks.
Usage
/research-synthesis $ARGUMENTS
What I Accept
- Interview transcripts or notes
- Survey results (CSV, pasted data)
- Usability test recordings or notes
- Support tickets or feedback
- NPS/CSAT responses
- App store reviews
Output
## Research Synthesis: [Study Name]
Method: [Interviews / Survey / Usability Test] | Participants: [X]
Date: [Date range] | Researcher: [Name]
Executive Summary
[3-4 sentence overview of key findings]
Key Themes
#### Theme 1: [Name]
Prevalence: [X of Y participants]
Summary: [What this theme is about]
Supporting Evidence:
- "[Quote]" — P[X]
- "[Quote]" — P[X]
Implication: [What this means for the product]
#### Theme 2: [Name]
[Same format]
Insights → Opportunities
| Insight | Opportunity | Impact | Effort |
|---------|-------------|--------|--------|
| [What we learned] | [What we could do] | High/Med/Low | High/Med/Low |
User Segments Identified
| Segment | Characteristics | Needs | Size |
|---------|----------------|-------|------|
| [Name] | [Description] | [Key needs] | [Rough %] |
Recommendations
- [High priority] — [Why, based on which findings]
- [Medium priority] — [Why]
- [Lower priority] — [Why]
Questions for Further Research
- [What we still don't know]
Methodology Notes
[How the research was conducted, any limitations or biases to note]
If Connectors Available
If ~~user feedback is connected:
- Pull support tickets, feature requests, and NPS responses to supplement research data
- Cross-reference themes with real user complaints and requests
If ~~product analytics is connected:
- Validate qualitative findings with usage data and behavioral metrics
- Quantify the impact of identified pain points
If ~~knowledge base is connected:
- Search for prior research studies and findings to compare against
- Publish the synthesis to your research repository
Tips
- Include raw quotes — Direct participant quotes make insights credible and memorable.
- Separate observations from interpretations — "5 of 8 users clicked the wrong button" is an observation. "The button placement is confusing" is an interpretation.
- Quantify where possible — "Most users" is vague. "7 of 10 users" is specific.
Supported Agents
Attribution
Details
- License
- MIT
- Source
- admin
- Published
- 3/18/2026
Tags
Related Skills
CPO Advisor
Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.
Onboarding CRO
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
Paywall Upgrade CRO
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.