synthesize-research

synthesize-research is a skill for Claude Code from nota-america/forgecat-agent-profiles. It costs 63 tokens per session (3,299 once invoked), scanned A, a copy of synthesize-research, Apache-2.0.

A workflow for turning interviews, surveys, support tickets, and other user feedback into organized findings. User research is information collected from or about people who use a product.

In plain words
What is it for?
It is for analyzing interview notes, survey answers, usability findings, support requests, sales notes, and related product data. It helps produce ranked insights and recommendations for the roadmap.
Why use it?
It reduces the work of reading many research sources separately and finding repeated themes by hand. It connects those themes to their frequency, impact, and possible product decisions.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit It is for analyzing interview notes, survey answers, usability findings, support requests, sales notes, and related product data. It helps produce ranked insights and recommendations for the roadmap.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nota-america/forgecat-agent-profiles/synthesize-research
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nota-america/forgecat-agent-profiles --skill synthesize-research
Clone the repo
git clone --depth 1 https://github.com/nota-america/forgecat-agent-profiles

Made for: Claude Code.

Wrote 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.

agentmods badge for synthesize-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/synthesize-research/github.svg)](https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/synthesize-research)
Your own site
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/synthesize-research"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/synthesize-research/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for synthesize-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/synthesize-research"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/synthesize-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 98% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.03299
Opus 5 $0.00032 $0.01649
Sonnet 5 $0.00013 $0.00660
Haiku 4.5 $0.00006 $0.00330

Measured 8d ago against content hash d92e6b74b8f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 8d 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.

Origin

This is a copy

98% identical to synthesize-research — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

profiles/anthropics/knowledge-work-plugins/anthropics_knowledge-work-plugins_product-management/for-claude/.claude/skills/synthesize-research/SKILL.md · 317 lines

How it starts

The opening of the file, as written. The whole thing — 317 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 (.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_product-management/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.

Read the full file on GitHub · 317 lines

Changes

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.

  1. 8d ago First seen · 317 lines · 63 tokens per session scan A d92e6b74b8f7

Subscribe to this mod's changes

synthesize-research is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 3,299 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to synthesize-research, differing in 10 lines, and is treated as a copy.