Skills › Knowledge Work Plugins › research-synthesis
research-synthesis
The facts
Its description
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.
The description the agent reads to decide when to use it.
From its settingsline 3
When it starts
It fires when someone hands over raw research material — interview transcripts, survey results, usability test notes, support tickets, NPS/CSAT responses or app store reviews — and wants it boiled down into themes, insights, user segments and prioritized recommendations.
Things a person might say (the model's guesses)
- “I've got transcripts from eight user interviews — can you pull out the themes?”
- “Here's our NPS survey export, tell me what users are actually complaining about”
- “We just finished usability testing, here are the notes — what should we fix first?”
A model's summary of when it is used.
A model's reading
What it takes when started
<research data, transcripts, or survey results>
What to type after its name when you start it.
From its settingsline 4
Licence
Apache-2.0, from LICENSE
The terms its author shares it under, which let it be shown here.
From the repositorylicence text
The text
Most marks come from matching words in the file, so treat them as pointers.
1---
2name: research-synthesis
3description: 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.
4argument-hint: "<research data, transcripts, or survey results>"
5---
7# /research-synthesis
9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
11Synthesize user research data into actionable insights. See the **user-research** skill for research methods, interview guides, and analysis frameworks.
/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.
Raw lines 1 to 12Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close
19## What I Accept
21- Interview transcripts or notes
22- Survey results (CSV, pasted data)
23- Usability test recordings or notes
24- Support tickets or feedback
25- NPS/CSAT responses
26- App store reviews
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
28## Output
30```markdown
31## Research Synthesis: [Study Name]
32**Method:** [Interviews / Survey / Usability Test] | **Participants:** [X]
33**Date:** [Date range] | **Researcher:** [Name]
35### Executive Summary
36[3-4 sentence overview of key findings]
38### Key Themes
40#### Theme 1: [Name]
41**Prevalence:** [X of Y participants]
42**Summary:** [What this theme is about]
43**Supporting Evidence:**
44- "[Quote]" — P[X]
45- "[Quote]" — P[X]
46**Implication:** [What this means for the product]
48#### Theme 2: [Name]
49[Same format]
51### Insights → Opportunities
53| Insight | Opportunity | Impact | Effort |
54|---------|-------------|--------|--------|
55| [What we learned] | [What we could do] | High/Med/Low | High/Med/Low |
57### User Segments Identified
58| Segment | Characteristics | Needs | Size |
59|---------|----------------|-------|------|
60| [Name] | [Description] | [Key needs] | [Rough %] |
62### Recommendations
631. **[High priority]** — [Why, based on which findings]
642. **[Medium priority]** — [Why]
653. **[Lower priority]** — [Why]
67### Questions for Further Research
68- [What we still don't know]
70### Methodology Notes
71[How the research was conducted, any limitations or biases to note]
72```
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
1. **[High priority]** — [Why, based on which findings]
2. **[Medium priority]** — [Why]
3. **[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]74## If Connectors Available
76If **~~user feedback** is connected:
77- Pull support tickets, feature requests, and NPS responses to supplement research data
78- Cross-reference themes with real user complaints and requests
80If **~~product analytics** is connected:
81- Validate qualitative findings with usage data and behavioral metrics
82- Quantify the impact of identified pain points
84If **~~knowledge base** is connected:
85- Search for prior research studies and findings to compare against
86- Publish the synthesis to your research repository
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
Uses an outside tool ~~user :76
Uses an outside tool ~~product :80
Uses an outside tool ~~knowledge :84
88## Tips
901. **Include raw quotes** — Direct participant quotes make insights credible and memorable.
912. **Separate observations from interpretations** — "5 of 8 users clicked the wrong button" is an observation. "The button placement is confusing" is an interpretation.
923. **Quantify where possible** — "Most users" is vague. "7 of 10 users" is specific.
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.
From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.