user-research
Skill12 starsChanged 29 days agoMITView on GitHub
User research skill — plan interviews, synthesize findings, and generate personas
19 other projects use a version of this.
Adopted by
Most recently taken up by
- Vujavujavuja/Stillmotion-onbrandtheir own version, first seen Nov 16, 2026
- Alter-ai/skill-labtheir own version, first seen Nov 15, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- AxlZero21/Skillstheir own version, first seen Nov 8, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
- sankar2code/Claude-Skill_SubAgent-Builder-Collectionstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use prd-writer, competitive-analysis and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nimbalystSkillprd-writer
Create structured Product Requirements Documents (PRDs) with prioritized requirements. Use when writing product specs, feature requirements, or project briefs.
Also in 3 projects that use this
AnthropicSkillcompetitive-analysis
Framework for building competitive landscape decks — market positioning, competitor deep-dives, comparative analysis, strategic synthesis. Use when the user asks for a competitive landscape, competitor analysis, peer comparison, market positioning assessment, strategic review, or investment memo deck. Also triggers on "who are the competitors to X", "benchmark X against peers", "build a market map", or any request to systematically evaluate competitive dynamics across an industry.
Also in 3 projects that use this
Microsoft AzureSkillgit-workflow
Squad branching model: dev-first workflow with insiders preview channel
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 5 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- anthropics/knowledge-work-plugins★ 36ksame name
- aakashg/pm-claude-code-setup★ 152same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- shayan-m81/layerwright★ 8same name
- kevinaimonster/skill-hub★ 4same name
- sankar2code/Claude-Skill_SubAgent-Builder-Collections★ 2same name
- Vujavujavuja/Stillmotion-onbrand★ 2same name
- AxlZero21/Skills★ 1same name
- huangqianqian120/skillslibrary★ 1same name
- NinjaSln-labs/agent-skills★ 1same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- agent/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- router/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/verification.mdcCursor rule
- agentic-agileSkill
- agentic-portfolioSkill
- client-onboardingSkill
- cooldown-resumeSkill
- drillSkill
- ecc-harness-patternsSkill
- fabric-patternsSkill
- graphiti-temporalSkill
- managed-agents-dreamsSkill
- model-catalogue-updateSkill
- platform-setupSkill
- repowise-intelligenceSkill
- risky-module-reviewSkill
- seo-audit-reportSkill
- video-contextSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Plan: Before kicking off a new research initiative — defines scope, objectives, methods, and sample size.
- Distinctive: line 31
Qual: After collecting 3+ interview transcripts or open-ended responses — finds themes and pain points.
- Distinctive: line 32
Quant: After collecting numeric survey data or experiment metrics — produces the descriptive stats and segment cuts.
- Distinctive: line 33
Synthesize: After both qual and quant are available — produces the executive brief a stakeholder will read.
- Very specific: line 40
All four capabilities are pure functions (plan_research, analyze_qualitative, analyze_quantitative, synthesize_research) that take and …
- Very specific: line 53
All inputs and outputs use Pydantic v2 with extra="forbid" so the executor cannot smuggle unknown fields past validation:
- Very specific: line 112
After auto_register() is called (or after agent/capability_registry.py discovers the module), the agent loop can invoke:
- Very specific: line 140
Default z=1.96 (95% confidence), e=0.05, p=0.5.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: user-research
Module:
agent/user_research_skill.pyAgent tools registered:user_research_plan,user_research_qual,user_research_quant,user_research_synthesizeCapability tag:user_research(sub-tags:plan,qualitative,quantitative,synthesis) Maturity: stable
Purpose
Structured user-research workflows for the agent platform. Implements the four core capabilities adapted from the cookiy-ai/user-research-skill reference architecture:
| Capability | Tool name | What it does |
| Plan | user_research_plan | Produce a structured research plan (objectives, hypotheses, methods, sample size, timeline) from a research question. |
| Qual | user_research_qual | Extract themes, pain points, and desires from interview transcripts or open-ended survey responses. |
| Quant | user_research_quant | Compute descriptive statistics (mean, median, σ, distribution, segment cuts) for a numeric series. |
| Synthesize | user_research_synthesize | Combine qual + quant into a decision-ready research brief with executive summary, findings, and recommendations. |
When to Use
- Plan: Before kicking off a new research initiative — defines scope, objectives, methods, and sample size.
- Qual: After collecting 3+ interview transcripts or open-ended responses — finds themes and pain points.
- Quant: After collecting numeric survey data or experiment metrics — produces the descriptive stats and segment cuts.
- Synthesize: After both qual and quant are available — produces the executive brief a stakeholder will read.
Architecture
The skill is implemented as a pure-function library with a thin tool-wrapping layer:
- All four capabilities are pure functions (
plan_research,analyze_qualitative,analyze_quantitative,synthesize_research) that take and return Pydantic v2 models. - The functions are then registered with the agent
ToolRegistryvia the@registry.agent_tooldecorator, so the agent loop can invoke them like any other tool. - No LLM calls inside the skill. The LLM is the executor that uses the tool; the tool provides the structural framework (Pydantic contracts, sample-size math, theme extraction heuristics, descriptive stats). This keeps the skill fast, testable, and free of hidden costs.
Pydantic Models (extra="forbid")
All inputs and outputs use Pydantic v2 with extra="forbid" so the executor
cannot smuggle unknown fields past validation:
ResearchPlan— output of PlanResearchObjective,ResearchHypothesis,ResearchMethod— sub-modelsQualAnalysis,QualTheme,QualQuote— output of QualQuantAnalysis,QuantSegment— output of QuantResearchBrief— output of Synthesize
Usage
As a Python library
from agent.user_research_skill import (
plan_research, analyze_qualitative,
analyze_quantitative, synthesize_research,
)
# 1. Plan
plan = plan_research(
title="Why do users churn after onboarding?",
primary_question="What causes week-1 churn?",
audience="Product team",
objectives=[{"statement": "Identify the top 3 friction points"}],
methods=[{"method": "interview", "target_participants": 8}],
)
print(plan.target_sample_size) # computed from method target + stats
# 2. Qual
qual = analyze_qualitative(
source="8 customer interviews",
transcripts=[
"Login is broken and slow, hate it.",
"Login is broken, otherwise fine.",
"Love the new dashboard, but login is broken.",
],
)
for theme in qual.pain_points:
print(theme.name, theme.frequency)
# 3. Quant
quant = analyze_quantitative(
source="NPS survey Q4",
values=[9, 9, 8, 10, 9, 8, 9, 10, 7, 9],
metric_name="NPS",
metric_type="rating",
)
print(quant.mean, quant.median, quant.stdev)
# 4. Synthesize
brief = synthesize_research(title="Q4 NPS + Interview Synthesis",
quant=quant, qual=qual)
print(brief.executive_summary)
print(brief.recommendations)As an agent tool
After auto_register() is called (or after agent/capability_registry.py
discovers the module), the agent loop can invoke:
# In an agent prompt, the model can call:
{
"tool": "user_research_plan",
"args": {
"title": "Onboarding friction study",
"primary_question": "What blocks first-week activation?",
"audience": "Product",
"objectives": [{"statement": "Identify top 3 blockers"}],
"methods": [{"method": "interview", "target_participants": 6}]
}
}…and receive a validated ResearchPlan back.
Sample-Size Math
The plan_research function computes the target sample size from the
larger of:
- The sum of
target_participantsacross all methods. - The standard normal-approximation sample size for a proportion, with
finite-population correction when
population_sizeis supplied.
Formula: n0 = z² · p(1-p) / e², then n = n0 / (1 + (n0-1)/N).
Default z=1.96 (95% confidence), e=0.05, p=0.5.
Sentiment + Theme Heuristics
The analyze_qualitative function uses a small rule-based sentiment
classifier (positive / neutral / negative) and a keyword-based theme
extractor. Themes are filtered by min_theme_frequency (default 2) to
avoid single-mention noise. Real production sentiment should use an
LLM call — these heuristics are deliberately minimal so the skill
scaffolding is fast and testable.
Tests
tests/test_user_research_skill.py covers:
- Plan: minimal plan, sample-size math, ID uniqueness, scope, extras rejection
- Qual: theme extraction, participant ID handling, sentiment, min-frequency filter
- Quant: basic stats, distributions, segments, edge cases
- Synthesize: quant-only, qual-only, combined, segment gap detection
- Tool registration: 4 tools, capability discovery, idempotency, OpenAI export
- End-to-end: plan → qual → synthesize
Run with:
pytest -x tests/test_user_research_skill.py -vAuto-Registration
The skill auto-registers with the module-level ToolRegistry singleton
on first import of agent.user_research_skill. To force registration
in a custom registry, call register_user_research_tools(registry)
explicitly.
Files
| File | Purpose |
agent/user_research_skill.py | Pydantic models + 4 capability functions + tool registration |
tests/test_user_research_skill.py | 35+ tests covering all capabilities and edge cases |
.claude/skills/user-research/SKILL.md | This document |
See Also
agent/capability_registry.py— the dynamic tool registry.claude/skills/research/SKILL.md— general-purpose research skill (broader scope, this skill is user-research-specific)- https://github.com/cookiy-ai/user-research-skill — the reference architecture this is adapted from
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

