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.

by Anthropic, PBC · Anthropic, PBC, Apache-2.0 · version 1 · license Apache-2.0

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.

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

Source material given with the request

Notes app "Quillpad". Version 3.2 was released on September 9. T-401 Sep 2 Charged twice for the monthly plan. T-402 Sep 4 Would love a dark mode. T-403 Sep 5 Password reset email never arrives. T-404 Sep 10 Notes edited on iPad don't show up on my laptop (v3.2). T-405 Sep 10 Invoice shows the wrong company name. T-406 Sep 11 Edits made offline were lost when I reconnected. T-407 Sep 12 After the update I have duplicate copies of every notebook. T-408 Sep 12 Please add calendar integration. T-409 Sep 13 Since the update the sync spinner never stops. T-410 Sep 15 Want a refund on my annual plan. T-411 Sep 16 Shared notebook isn't updating for my teammate. T-412 Sep 17 Lost two days of edits on my phone.

with the skill

## Quillpad support-ticket synthesis **Scope:** 12 tickets, September 2–17. Version 3.2 released September 9. ### Ticket groups | Theme | Tickets | Count | What we’re seeing | |---|---|---:|---| | **Sync and data integrity** | T-404, T-406, T-407, T-409, T-411, T-412 | **6/12** | Cross-device and shared-notebook updates failing, lost edits, duplicate notebooks, and a persistent sync spinner | | **Billing and refunds** | T-401, T-405, T-410 | **3/12** | Double charge, incorrect invoice details, and an annual-plan refund request | | **Feature requests** | T-402, T-408 | **2/12** | Dark mode and calendar integration | | **Account access** | T-403 | **1/12** | Password-reset email not arriving | ### What to look at first **1. Investigate sync and data integrity as a potential v3.2 regression.** All six tickets in this group arrived after the release, and three explicitly reference v3.2 or the update. That makes a release-related issue a strong hypothesis—not a confirmed cause. Within this group, prioritize:

Show the rest (21 more lines)

- **Lost edits — T-406, T-412:** Highest potential harm. Investigate offline reconnection and edit recovery; preserve relevant logs and available revision history. - **Missing updates — T-404, T-411:** Determine whether edits are delayed, failing to propagate, or actually lost. - **Duplication and stuck sync — T-407, T-409:** Check whether these share a cause with the missing or lost edits rather than assuming one underlying bug. **Evidence:** “Edits made offline were lost when I reconnected” and “Lost two days of edits on my phone.” **Immediate checks:** Compare sync failures before and after September 9, segment by app version and platform, and reproduce offline-edit → reconnect and cross-device workflows. If an active regression is confirmed, assess a targeted fix or rollback. **2. Resolve financial harm and access problems in parallel.** - **T-401:** Verify and correct the double charge promptly. - **T-403:** Investigate reset-email delivery; this may prevent account access entirely. - **T-405 and T-410:** Correct the invoice and handle the refund request. Ask why the refund was requested—there is no evidence yet connecting it to sync problems. **3. Keep feature requests in the backlog.** Record dark mode and calendar integration as demand signals, but don’t prioritize them over data loss, billing errors, or blocked access based on this sample. ### Key caveat These are **ticket counts, not confirmed unique users or incident rates**. The post-release clustering warrants urgent investigation, but without usage volumes, version details, and an earlier baseline, we cannot establish whether v3.2 caused an increase.

without

## Ticket groups | Group | Tickets | Assessment | |---|---|---| | **Lost edits / possible data loss** | **T-406:** Offline edits lost on reconnect; **T-412:** Two days of phone edits lost | Highest severity: potential loss of user work. | | **Sync and notebook consistency** | **T-404:** iPad edits missing on laptop; **T-407:** Duplicate notebooks; **T-409:** Sync spinner never stops; **T-411:** Shared notebook not updating | Potentially related to the data-loss reports, but a common cause is not yet confirmed. | | **Billing and refunds** | **T-401:** Double charge; **T-405:** Wrong company name on invoice; **T-410:** Annual-plan refund request | Handle through billing support; prioritize the double charge. The refund reason is unknown. | | **Account access** | **T-403:** Password-reset email missing | Potential account lockout; investigate promptly. | | **Feature requests** | **T-402:** Dark mode; **T-408:** Calendar integration | Product backlog, below active reliability and access issues. | ## What to look at first **1. Investigate data loss and sync as a possible v3.2 incident.** All six data-loss/sync tickets arrived after the September 9 release. T-404 explicitly names v3.2, and T-407 and T-409 explicitly link their symptoms to the update. That is a strong reason to investigate a regression—not proof that all six share a cause. - Start with **T-406 and T-412**: determine whether edits are deleted, recoverable, or merely not syncing. - Check v3.2 changes to offline reconciliation, conflict handling, and cross-device/shared-notebook sync. - Confirm app versions and affected platforms for all six tickets; compare with pre-release reports and telemetry. - Preserve relevant logs and recoverable note history before recommending resets or reinstalls. - If ongoing data loss is confirmed, prioritize containment and recovery over routine fixes.

Show the rest (7 more lines)

**2. Address account access and the double charge in parallel.** T-403 may block use entirely; T-401 represents direct financial harm. Neither should wait for the sync investigation. **3. Resolve the remaining billing requests, then triage feature requests.** Correct T-405’s invoice and process T-410 under the refund policy. Ask why the customer wants a refund rather than assuming it is release-related. **Bottom line:** The first engineering priority is **potential data loss following v3.2**, with the other sync symptoms investigated alongside it.

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.