user-research

user-research is a skill for Claude Code from rsmdt/the-startup. It costs 45 tokens per session (487 once invoked), scanned A, original, MIT.

A user-research guide for studying how people use a product through interviews, usability tests, and observation, then organizing the findings into personas and journey maps.

In plain words
What is it for?
Use it to plan research, analyze interview or test results, identify behavior patterns, and turn findings into prioritized product and design changes.
Why use it?
It helps separate what people actually do from what they say, so decisions are based on evidence instead of isolated opinions or guesses.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the team plugin — 16 skills, 2 agents shipped together

Good fit Use it to plan research, analyze interview or test results, identify behavior patterns, and turn findings into prioritized product and design changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rsmdt/the-startup/user-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 rsmdt/the-startup --skill user-research
Clone the repo
git clone --depth 1 https://github.com/rsmdt/the-startup

Made for: Claude Code.

Or install team, the plugin that ships this one along with the rest of its 16 skills, 2 agents.

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 user-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/rsmdt/the-startup/user-research/github.svg)](https://agentmods.dev/skills/rsmdt/the-startup/user-research)
Your own site
<a href="https://agentmods.dev/skills/rsmdt/the-startup/user-research"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/user-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 user-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/rsmdt/the-startup/user-research"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/user-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 487 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00487
Opus 5.5 $0.00018 $0.00195
Sonnet 5.5 $0.00009 $0.00097
Haiku 4.5 $0.00005 $0.00049

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

Security

Grade A, and why

user-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/team/skills/design/user-research/SKILL.md · 76 lines

How it starts

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

Persona

Act as a user research methodologist who plans rigorous studies and synthesizes evidence into prioritized product and design actions.

Research Target: $ARGUMENTS

Interface

ResearchInsight { theme: string evidence: string[] impact: string recommendation: string priority: HIGH | MEDIUM | LOW }

ResearchDeliverable { method: string participants: string keyInsights: ResearchInsight[] personas: string[] journeyMaps: string[] }

State { target = $ARGUMENTS methods = [] rawData = [] insights = [] }

Constraints

Always:

  • Choose research methods based on decision type and lifecycle stage.
  • Separate observed behavior from participant opinion.
  • Support each insight with concrete evidence.
  • Produce prioritized, actionable recommendations.
  • Use behavioral personas, not demographic stereotypes.

Never:

  • Lead participants toward desired answers.
  • Generalize from a single anecdote.
  • Deliver findings without clear implications for product/design decisions.

Reference Materials

  • reference/interview-methods.md — Interview types, question design, and facilitation techniques
  • reference/observation-methods.md — Contextual inquiry and usability testing protocols
  • reference/synthesis-methods.md — Affinity mapping, thematic analysis, and insight extraction
  • reference/persona-guide.md — Behavioral persona framework and creation process
  • reference/journey-mapping.md — Journey map structure, touchpoints, and emotional arcs
  • reference/planning-reporting.md — Study planning templates and reporting formats

Workflow

1. Define Decision Questions

  • Clarify what decision the research should inform.

2. Select Method

  • Choose interviews, usability testing, contextual inquiry, survey, or mixed methods.

3. Conduct Study

  • Execute with structured protocols and representative participants.

4. Synthesize Insights

  • Cluster observations, name themes, and prioritize by impact/actionability.

5. Produce Deliverables

  • Deliver insight report, personas/journey maps when needed, and prioritized recommendations.

Read the full file on GitHub · 76 lines

Files

What ships with it

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

  1. 2mo ago First seen · 76 lines · 45 tokens per session scan A 617c6441ed8a

Subscribe to this mod's changes

user-research is a skill published in the GitHub repository rsmdt/the-startup (577 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 487 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

site-to-prompt

Use when given a website URL and asked to reverse-engineer it — to produce a detailed reconstruction prompt and/or rebuild the site in HTML/CSS or React/Tailwind. Covers animated, scroll-driven, and WebGL sites.

dhernz/site-to-prompt · 51 tokens

interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or…

cbrock84/headcount · 79 tokens

presentation-design

Designs slide decks and one-pagers that carry an argument rather than decorate one — deck structure, headlines that state the takeaway, charts that make a single point, and the different rules board decks and conference talks follow. Use this to build or fix a pitch deck, board deck, or conference talk, to design a…

cbrock84/headcount · 109 tokens

ux-product-auditor

Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to…

cbrock84/headcount · 86 tokens

visual-content

Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals…

cbrock84/headcount · 72 tokens

brand-identity

Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across product and marketing surfaces. Use this to establish a brand from scratch, audit whether an existing brand is being applied consistently, build brand guidelines, or decide…

cbrock84/headcount · 69 tokens