- Home
- Skills
- Anthropics
- Knowledge Work Plugins
- User Research Synthesis
user-research-synthesis_skill
- Python
- Official
7.4k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill anthropics/knowledge-work-plugins --skill user-research-synthesis- SKILL.md11.0 KB
Overview
This skill synthesizes qualitative and quantitative user research into clear, actionable insights and prioritized opportunity areas. It helps product teams convert interview notes, survey responses, support tickets, and behavioral data into themes, personas, and opportunity scores that drive product decisions. The output is structured findings with evidence, confidence levels, and suggested next steps.
How this skill works
The skill applies thematic analysis and affinity mapping to qualitative data: it codes observations, groups codes into themes, and refines theme definitions with representative quotes and frequency counts. It triangulates across methods and sources, integrates survey and analytics data to validate and prioritize themes, and produces persona profiles and opportunity sizing with transparent assumptions and scores. Results include evidence strength, recommended actions, and a ranked opportunity list.
When to use it
- After a round of user interviews to turn notes into validated themes and personas
- When open-ended survey responses need coding and frequency analysis
- To analyze support tickets or usability test transcripts for recurring pain points
- To combine behavioral analytics with qualitative findings for prioritization
- When preparing a research-backed roadmap or product brief
Best practices
- Start by familiarizing yourself with all raw data before coding
- Code generously, then merge similar codes during theme development
- Keep one observation per note during affinity mapping
- Triangulate findings across methods and report disagreements explicitly
- Score opportunities with transparent assumptions and use ranges
Example use cases
- Transform 30 interview transcripts into 4 validated themes, 3 personas, and a prioritized opportunity list
- Code 500 open-ended survey responses to surface unexpected feature requests and their prevalence
- Analyze support ticket volumes plus interviews to size the impact of a recurring onboarding friction
- Combine product analytics with interview quotes to explain a retention drop and propose fixes
- Create evidence-based personas and estimate their relative segment sizes for roadmap decisions
FAQ
Report the disagreement, check if populations differ, examine whether stated preferences match observed behavior, and recommend targeted follow-up research to resolve the discrepancy.
What level of sample size is needed to trust survey-backed findings?
There is no fixed cutoff: prioritize response rate, segment representativeness, and effect size. Treat small samples as hypothesis-generating and validate with additional methods.