Knowledge Work Plugins is an open-source collection of Claude extensions organized around roles such as productivity, sales, and customer support. Each plugin combines role-specific guidance, connectors, commands, and sub-agents so knowledge workers can use Claude with their team’s tools and processes. The catalogue entries are examples of, or workflows from, this plugin collection.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsnpx agentmods add skills/anthropics/knowledge-work-plugins/synthesize-researchWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/anthropics/knowledge-work-plugins/synthesize-research)<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/synthesize-research"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/synthesize-research.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.03272 |
| Opus 5 | $0.00032 | $0.01636 |
| Sonnet 5 | $0.00013 | $0.00654 |
| Haiku 4.5 | $0.00006 | $0.00327 |
Grade A, and why
synthesize-research scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- synthesize-research — 98% identical, 10 lines differ
- synthesize-research-th — 92% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesize Research
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Synthesize user research from multiple sources into structured insights and recommendations.
Usage
/synthesize-research $ARGUMENTS
Workflow
1. Gather Research Inputs
Accept research from any combination of:
- Pasted text: Interview notes, transcripts, survey responses, feedback
- Uploaded files: Research documents, spreadsheets, recordings summaries
- ~~knowledge base (if connected): Search for research documents, interview notes, survey results
- ~~user feedback (if connected): Pull recent support tickets, feature requests, bug reports
- ~~product analytics (if connected): Pull usage data, funnel metrics, behavioral data
- ~~meeting transcription (if connected): Pull interview recordings, meeting summaries, and discussion notes
Ask the user what they have:
- What type of research? (interviews, surveys, usability tests, analytics, support tickets, sales call notes)
- How many sources / participants?
- Is there a specific question or hypothesis they are investigating?
- What decisions will this research inform?
2. Process the Research
For each source, extract:
- Key observations: What did users say, do, or experience?
- Quotes: Verbatim quotes that illustrate important points
- Behaviors: What users actually did (vs what they said they do)
- Pain points: Frustrations, workarounds, and unmet needs
- Positive signals: What works well, moments of delight
- Context: User segment, use case, experience level
3. Identify Themes and Patterns
Apply thematic analysis — see Research Synthesis Methodology below for detailed guidance on thematic analysis, affinity mapping, and triangulation techniques.
Group observations into themes, count frequency across participants, and assess impact severity. Note contradictions and surprises.
Create a priority matrix:
- High frequency + High impact: Top priority findings
- Low frequency + High impact: Important for specific segments
- High frequency + Low impact: Quality-of-life improvements
- Low frequency + Low impact: Note but deprioritize
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 313 lines · 63 tokens per session scan A ae98c1110254
synthesize-research is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,902 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 3,272 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…