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
## Your NPS is **+15** Across 20 responses: | Group | Scores | Responses | Share | |---|---|---:|---:| | Promoters | 9–10 | 9 | 45% | | Passives | 7–8 | 5 | 25% | | Detractors | 0–6 | 6 | 30% | **NPS = % promoters − % detractors = 45 − 30 = +15.** ## What’s driving it? ### Positive: Support is your standout strength **7 of 9 promoters** praise support, citing speed, helpfulness, and migration assistance. - “Support answered in minutes.” - “Best support of any vendor we use.” **Implication:** Preserve support quality—it is the most frequently mentioned reason for recommending you.
Show the rest (27 more lines)
### Positive: Reporting delivers tangible value **3 of 9 promoters** praise reporting; one also praises support. - “Reports save me hours every week.” **Implication:** Time savings are a concrete value story worth reinforcing in onboarding and customer communications. ### Negative: The March price increase dominates dissatisfaction **5 of 6 detractors** mention the March increase. Their concerns include affordability, lack of added value, and poor communication. - “Price went up 40% in March for the same features.” - “The price hike made me look at alternatives.” - “The March price change was not communicated well.” **Implication:** Pricing is the clearest issue to investigate first. These comments suggest both a **price–value mismatch** and a **communication problem**, with an explicit signal of switching risk. ### Negative: Mobile performance is a secondary pain point **3 of 20 respondents** report mobile problems: two passives mention slowness, and one detractor reports crashes during photo uploads. - “Mobile app crashes when I upload photos.” **Implication:** Investigate upload crashes first, then mobile speed. These issues appear in both neutral and negative feedback. ## Recommended priorities 1. **Address pricing-related dissatisfaction:** Follow up with affected customers, assess churn risk, and distinguish affordability concerns from perceived value and communication gaps. 2. **Fix mobile reliability:** Reproduce photo-upload crashes and measure mobile performance. 3. **Protect and reinforce what works:** Maintain support quality and make reporting’s time-saving benefits more visible. **Bottom line:** Support and reporting earn advocacy; the March price increase is the dominant complaint among detractors. This is a small, self-selected sample: it identifies strong themes, but without prior-month data it cannot establish whether NPS has declined or whether pricing caused a change.
without
## Your NPS is **+15** NPS = % promoters (9–10) − % detractors (0–6). | Group | Responses | Share | |---|---:|---:| | Promoters | 9 | 45% | | Passives (7–8) | 5 | 25% | | Detractors | 6 | 30% | | **Total** | **20** | **100%** | **45% − 30% = +15** ## What’s driving it? - **Support is the biggest positive theme.** Seven respondents praised support, and all seven were promoters. Fast responses, migration help, and team quality stand out. - **Reporting is another strength.** Three promoters praised reports, including one who said they save hours every week. One also praised support, so these themes overlap. - **The March price increase is the dominant negative theme.** Five of the six detractors cited it. Comments point to both **poor perceived value**—paying more for the same features—and **poor communication**. One respondent explicitly mentioned looking at alternatives. - **Mobile reliability and speed are secondary issues.** Three respondents mentioned mobile: two passives reported slowness, and one detractor reported crashes during photo uploads.
Show the rest (7 more lines)
## What to prioritize 1. **Address pricing dissatisfaction first:** follow up with affected customers, understand the value gap, and improve how pricing changes are explained. 2. **Fix mobile upload crashes and investigate slowness.** 3. **Protect what’s working:** support quality and time-saving reports are clear strengths. **Bottom line:** Support and reporting are earning advocacy, while the March pricing change is the main source of dissatisfaction in these responses. With only 20 responses, treat this as a directional snapshot rather than a definitive picture of all customers.

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.