Agent skill · Data & Analytics

user-research-synthesis

Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps. For interview transcripts specifically use user-interview-synthesis instead.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill user-research-synthesis --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/user-research-synthesis/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# User Research Synthesis Skill This skill helps analyze user research data and transform it into actionable insights following a structured methodology. ## Required Inputs Ask the user for these if not provided: - **Research data** (transcripts, notes, survey results, or summary bullets) - **Research method** (interviews, surveys, usability tests, etc.) - **Number of participants** and their profiles (role, context) - **Research questions** the study aimed to answer ## Reads from / Writes to the Brain If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, use it before asking: - **Read first:** open `hypotheses/` (which assumptions this research can validate or invalidate) and `context.md` (who the users are). - **Write after:** update each touched hypothesis's status, add durable insights to `knowledge/users.md`, and keep the raw notes in `source/`. Tag interview-derived claims `[interview]` — never launder them into `[data]`. ## Synthesis Framework ### 1. Data Collection Overview - **Research Type**: Interviews, surveys, usability tests, etc. - **Participant Profile**: Demographics, segments, sample size - **Research Questions**: What we sought to learn -

What's inside
Steps it walks through
  1. Required Inputs
  2. Reads from / Writes to the Brain
  3. Synthesis Framework
  4. 1. Data Collection Overview
  5. 2. Key Themes Identification
  6. 3. Pain Points Analysis
  7. 4. Feature Requests
  8. 5. User Workflow Insights
  9. 6. Segmentation Insights
  10. 7. Competitive Insights
  11. 8. Recommendations
  12. 9. Open Questions
  13. Analysis Guidelines
  14. Deeper Materials
Ships with 3 files
  • references/theme-validity.md
  • references/worked-example.md
  • templates/synthesis-report.md
More from pm-claude-skills
All skills →
About this skill
What does the user-research-synthesis skill do?

Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps. For interview transcripts specifically use user-interview-synthesis instead.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill user-research-synthesis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going