Research Synthesis

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

FeaturedInstructions onlyResearch & Analysis
AI-generated overview

Synthesizes user research data into themes, insights, segments, and prioritized recommendations.

What it does
Takes interview transcripts, survey results, usability test notes, support tickets, or NPS/CSAT responses and distills them into a structured synthesis report. The output includes an executive summary, key themes with prevalence and supporting quotes, an insights-to-opportunities table, identified user segments, prioritized recommendations, open questions, and methodology notes. It also describes optional connector integrations for pulling feedback, validating findings with analytics, and publishing to a research repository.
When to use it
Use when you have raw user research material that needs to be distilled into patterns, user segments, and prioritized next steps. Suited to product or UX research synthesis after interviews, surveys, or usability tests.
Requirements
Instructions only; no scripts. Optional connectors for user feedback, product analytics, and knowledge base are described but not required.

/research-synthesis

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Synthesize user research data into actionable insights. See the user-research skill for research methods, interview guides, and analysis frameworks.

Usage

/research-synthesis $ARGUMENTS

What I Accept

  • Interview transcripts or notes
  • Survey results (CSV, pasted data)
  • Usability test recordings or notes
  • Support tickets or feedback
  • NPS/CSAT responses
  • App store reviews

Output

markdown
## Research Synthesis: [Study Name]**Method:** [Interviews / Survey / Usability Test] | **Participants:** [X]**Date:** [Date range] | **Researcher:** [Name]
### Executive Summary[3-4 sentence overview of key findings]
### Key Themes
#### Theme 1: [Name]**Prevalence:** [X of Y participants]**Summary:** [What this theme is about]**Supporting Evidence:**- "[Quote]" — P[X]- "[Quote]" — P[X]**Implication:** [What this means for the product]
#### Theme 2: [Name][Same format]
### Insights → Opportunities
| Insight | Opportunity | Impact | Effort ||---------|-------------|--------|--------|| [What we learned] | [What we could do] | High/Med/Low | High/Med/Low |
### User Segments Identified| Segment | Characteristics | Needs | Size ||---------|----------------|-------|------|| [Name] | [Description] | [Key needs] | [Rough %] |
### Recommendations1. **[High priority]** — [Why, based on which findings]2. **[Medium priority]** — [Why]3. **[Lower priority]** — [Why]
### Questions for Further Research- [What we still don't know]
### Methodology Notes[How the research was conducted, any limitations or biases to note]

If Connectors Available

If ~~user feedback is connected:

  • Pull support tickets, feature requests, and NPS responses to supplement research data
  • Cross-reference themes with real user complaints and requests

If ~~product analytics is connected:

  • Validate qualitative findings with usage data and behavioral metrics
  • Quantify the impact of identified pain points

If ~~knowledge base is connected:

  • Search for prior research studies and findings to compare against
  • Publish the synthesis to your research repository

Tips

  1. Include raw quotes — Direct participant quotes make insights credible and memorable.
  2. Separate observations from interpretations — "5 of 8 users clicked the wrong button" is an observation. "The button placement is confusing" is an interpretation.
  3. Quantify where possible — "Most users" is vague. "7 of 10 users" is specific.

Source and attribution

Source:anthropics/knowledge-work-pluginsindesign/skills/research-synthesisat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today