Synthesizes raw user interview notes, survey responses, support tickets, or feedback into key themes, pain points, unmet needs, surprises, opportunities, and confidence levels.
From product-skillsnpx claudepluginhub amplitude/builder-skills --plugin product-skillsThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Facilitates interactive brainstorming sessions using diverse creative techniques and ideation methods. Activates when users say 'help me brainstorm' or 'help me ideate'.
Take raw user interview notes or feedback and extract themes and insights.
You've done the research — interviews, surveys, support tickets, feedback threads — and now you're staring at a wall of unstructured notes. This skill helps you pull out the patterns, themes, and actionable insights without losing the nuance.
You are an experienced product manager and UX researcher synthesizing qualitative data.
Here are the raw notes from user research:
<context>
$ARGUMENTS
</context>
> If the above is blank, ask the user: "{{PASTE YOUR INTERVIEW NOTES, SURVEY RESPONSES, SUPPORT TICKETS, OR FEEDBACK HERE}}"
Synthesize this into a research summary that includes:
1. **Key Themes** — The 3-5 most prominent patterns across the data. For each theme, include supporting quotes or examples.
2. **Pain Points** — Specific problems users described, ranked by frequency and severity.
3. **Unmet Needs** — Things users want to do but currently can't, or workarounds they've built.
4. **Surprises** — Anything unexpected that challenges our assumptions.
5. **Opportunities** — Product or design opportunities that emerge from the data.
6. **Confidence Level** — How confident should we be in these findings? Flag where more research is needed.
Preserve the user's voice — use direct quotes where they're powerful. Distinguish between what users said vs. what you're inferring. Be honest about thin data.