What is analyze-research?

A method for turning user interviews, research transcripts, surveys, and feedback into organized findings. It identifies repeated themes, user problems, insights, and user profiles called personas.

Use it to summarize interviews, find common pain points, create personas, or write research reports with practical recommendations.

It reduces the manual work of reading many research notes and turning scattered comments into clear conclusions.

analyze-research — Skill for Claude Code by samkawsarani

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 samkawsarani/sams-product-plugins --skill analyze-research

Clone the repo

git clone --depth 1 https://github.com/samkawsarani/sams-product-plugins

Made for: Claude Code.

Or install analyze-research, the plugin that ships this one along with the rest of its 1 skill.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/analyze-research/github.svg)](https://agentmods.dev/skills/samkawsarani/sams-product-plugins/analyze-research)

Your own site

<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/analyze-research"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/analyze-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/analyze-research"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/analyze-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,098 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00078	$0.01098
Opus 5.5	$0.00031	$0.00439
Sonnet 5.5	$0.00016	$0.00220
Haiku 4.5	$0.00008	$0.00110

Measured 2mo ago against content hash 5f58a079fdbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyze-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 2mo 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.

plugins/analyze-research/skills/analyze-research/SKILL.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dependency Check

Before starting, check optional dependencies:

qmd (optional): Run command -v qmd.
- If available: Use qmd query for semantic search across knowledge bases — this gives the best results.
- If missing: Fall back to Grep and Glob for keyword search. Note to the user that qmd would improve search quality, but proceed without it.

User Research Analysis

Overview

Systematically analyze user interviews, research transcripts, surveys, and feedback to extract themes, identify patterns, generate actionable insights, and create comprehensive synthesis reports or personas.

Analysis Workflow

1. Understand the Request

Clarify what type of analysis is needed:

Theme extraction: Identify recurring topics and patterns
Insight generation: Synthesize findings into actionable recommendations
Persona creation: Build user profiles from research data
Quick synthesis: Summarize key findings
Full report: Comprehensive research synthesis document

Determine the source materials:

Location of transcripts (ask the user if not provided)
Related files — initiatives, specs, or prior research
Timeframe or specific interviews to analyze

Find relevant transcripts and documents using available search tools.

Any specific questions to answer

2. Review Source Materials

Read through all relevant materials:

Interview transcripts
Survey responses
Feedback forms
Meeting notes
Related product specs, opportunities, or initiatives

Use the analysis framework by reading references/analysis-framework.md for systematic guidance on:

How to extract themes
How to categorize findings
How to quote effectively
How to generate insights from observations

3. Perform Analysis

Based on the analysis framework, systematically:

Extract themes:

Identify recurring pain points, feature requests, behaviors
Quote verbatim with source attribution
Note frequency (how many users mentioned it)
Assess intensity (how strongly they felt about it)

Read the full file on GitHub · 143 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2mo ago First seen · 143 lines · 78 tokens per session scan A 5f58a079fdbf

Subscribe to this mod's changes

analyze-research is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,098 once invoked, about $0.0003 per session on Opus 5.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-08-31.

Analytics and metrics Research

analyze-research next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
analyze-researchsamkawsarani/sams-product-plugins	Skill	2	1mo ago	MIT	A	78	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
chat-pet-sprite-creationmicrosoft/vscode	Skill	195k	today	MIT	A	53	Claude Code, Codex