skills / research

research-synthesis

what it does

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.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Here are last month's NPS responses. What's our score, and what's driving it?”

Source material given with the request

Score | Comment 10 | Support answered in minutes. 9 | Love the support team. 3 | Price went up 40% in March for the same features. 8 | Works fine. 10 | Reports save me hours every week. 2 | Too expensive after the March increase. 9 | Support is fantastic. 7 | Okay, a bit slow on mobile. 6 | The price hike made me look at alternatives. 10 | Reports are great. 9 | Support helped us migrate. 4 | The March price change was not communicated well. 8 | Does what we need. 10 | Best support of any vendor we use. 5 | Mobile app crashes when I upload photos. 9 | Reports and support are both great. 7 | Fine. 1 | Paying more for nothing new since March. 10 | Support team is great.
Show the rest (2 more lines)
8 | Mostly good, mobile is slow.
with the skill
## NPS Synthesis: Last Month's Responses **Method:** NPS survey | **Responses:** 20 ### Score: **+15** | Group | Count | % | |---|---|---| | Promoters (9-10) | 9 | 45% | | Passives (7-8) | 5 | 25% | | Detractors (0-6) | 6 | 30% | NPS = 45% − 30% = **+15**. With only 20 responses, one or two people changing their answer would move the score by 5-10 points, so treat it as directional. ### What's driving it **Support and reports drive the promoters; the March price increase drives the detractors.** #### Theme 1: Support is the top promoter driver **Prevalence:** 7 of 20 mention it, and all 7 scored 9-10 (7 of the 9 promoters). - "Best support of any vendor we use." (10) - "Support helped us migrate." (9)
Show the rest (52 more lines)
- "Support answered in minutes." (10) **Implication:** Support is your strongest asset and a real differentiator. #### Theme 2: Reports deliver core value **Prevalence:** 3 of 20, scores 10, 10, 9. - "Reports save me hours every week." (10) **Implication:** Reports are the product's value anchor, so they are worth leading with in positioning and retention messaging. #### Theme 3: The March price increase is the main detractor driver **Prevalence:** 5 of 20 mention it, and all 5 scored 1-6. That accounts for 5 of the 6 detractors. - "Price went up 40% in March for the same features." (3) - "Paying more for nothing new since March." (1) - "The March price change was not communicated well." (4) - "The price hike made me look at alternatives." (6) There are two separate problems here. One is a **value perception gap** (more cost, no new features). The other is **poor communication** of the change. The "looking at alternatives" comment signals churn risk. #### Theme 4: Mobile is a secondary drag **Prevalence:** 3 of 20, scores 7, 5, 8. - "Mobile app crashes when I upload photos." (5) - "Okay, a bit slow on mobile." (7) Mobile mostly holds passives back from being promoters. It produces one detractor, through a crash bug. ### Insights → Opportunities | Insight | Opportunity | Impact | Effort | |---|---|---|---| | Price increase accounts for 5 of 6 detractors | Ship visible value alongside pricing, or offer grandfathering or transition discounts to at-risk accounts | High | Med | | Communication was poor | Proactive outreach to affected customers, and a playbook for future pricing changes | High | Low | | One user is evaluating alternatives | Flag and follow up with price-sensitive accounts | High | Low | | Mobile slowness and a crash bug hold back passives | Fix the photo-upload crash and improve performance | Med | Med | | Support and reports are loved | Use them in marketing and retention, and look at what makes support work | Med | Low | ### Segments | Segment | Characteristics | Needs | Size | |---|---|---|---| | Support/reports advocates | Score 9-10, value service and time savings | Keep service quality and report depth | ~45% | | Price-frustrated | Score 1-6, cite March increase | Clear value justification, communication, possibly pricing relief | ~25-30% | | Neutral/satisfied | Score 7-8, generic comments ("Fine," "Does what we need") | A reason to be enthusiastic, and mobile fixes | ~25% | ### Recommendations 1. **Address the price backlash.** It explains most of the negative scores. Reach out to detractors and show or ship new value. 2. **Fix the mobile photo-upload crash.** It's a concrete bug tied to a detractor score, and general mobile speed affects passives. 3. **Protect and promote support and reports.** They are what's keeping your promoters. ### Limitations and Further Research - **Small sample (n=20)**, so the percentages are rough. - No data on **response rate or who responded**, so non-response bias is possible. Churned customers may not have answered. - Comments are short and single-reason, which may understate multiple drivers. - Open questions: How many customers were affected by the price increase overall? Did any actually churn? Is the 40% increase uniform across plans? What new features would justify the price to unhappy customers? Compare with your previous month's NPS to see whether the March increase moved the score.
without
# NPS: +15 **Breakdown (n=20)** - Promoters (9-10): 9 → 45% - Passives (7-8): 5 → 25% - Detractors (0-6): 6 → 30% NPS = 45 − 30 = **+15** ## What's driving it **Positive: support (and reports)** - Support is mentioned in 7 of the 9 promoter comments ("answered in minutes," "helped us migrate," "best of any vendor"). - Reports are mentioned in 3 promoter comments, mainly for time saved. **Negative: the March price increase** - 5 of 6 detractors cite it, with scores of 1, 2, 3, 4, and 6. - The complaints are about value ("same features," "nothing new") and about poor communication of the change. - If those 5 had been passives, NPS would be about +40. Pricing is what's holding the score down.
Show the rest (12 more lines)
**Secondary: mobile** - 3 comments mention it (scores 5, 7, 8): slowness, plus one crash on photo upload. - It's not driving detractors much yet, but it keeps some customers at passive instead of promoter. **Passives** (7-8) mostly gave lukewarm comments like "Works fine" or "Fine," with no strong complaints. ## Takeaways 1. The price increase is the biggest drag. Consider whether the value story (new features, better communication) can be fixed, especially for customers who are already looking at alternatives. 2. Support is your strongest asset, so use it in retention outreach to the unhappy price-sensitive accounts. 3. Fix the mobile photo-upload crash and the slowness before they spread to more customers. **Caveat:** With 20 responses, a couple of people changing their scores would move NPS by 10 points or more. Treat the themes as more reliable than the exact number.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 1 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 1 Nov 2026

The tasks

written by Carte Blanche
biased-feature-survey

“We surveyed users about what to build next. Write up the findings for the team.”

expense-interviews

“I ran six interviews about our expense app last week. Can you pull out the main themes and what we should do about them?”

export-usability-test

“Summarize what we learned from this usability test on report export.”

nps-verbatims

“Here are last month's NPS responses. What's our score, and what's driving it?”

support-ticket-spike

“Group these support tickets and tell me what we should look at first.”

Install

Download the .zip and unzip it. Put its files, in a folder named research-synthesis, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.