How do I install the Research Synthesis skill?

Run npx skillmds@latest add nota-america/research-synthesis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Research Synthesis safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Research Synthesis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Research Synthesis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Research Synthesis?

nota-america (@nota-america) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Research Synthesis by nota-america — Agent Skill

Name: Research Synthesis
Author: nota-america

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.

nota-america Updated Sep 17, 2026

File contents

/research-synthesis

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md ({{ref:connectors}}).

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
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]

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.

---name: research-synthesisdescription: 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.---# /research-synthesis> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (`{{ref:connectors}}`).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```markdown## 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 %] |### Recommendations1. **[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]```## If Connectors AvailableIf **~~user feedback** is connected:- Pull support tickets, feature requests, and NPS responses to supplement research data- Cross-reference themes with real user complaints and requestsIf **~~product analytics** is connected:- Validate qualitative findings with usage data and behavioral metrics- Quantify the impact of identified pain pointsIf **~~knowledge base** is connected:- Search for prior research studies and findings to compare against- Publish the synthesis to your research repository## Tips1. **Include raw quotes** — Direct participant quotes make insights credible and memorable.2. **Separate observations from interpretations** — "5 of 8 users clicked the wrong button" is an observation. "The button placement is confusing" is an interpretation.3. **Quantify where possible** — "Most users" is vague. "7 of 10 users" is specific.

Frequently asked questions