user-research

user-research is a skill for Claude Code from yonatangross/orchestkit. It costs 44 tokens per session (1,419 once invoked), scanned A, original, MIT.

A collection of user-research methods for understanding people's needs and experiences. It covers personas, customer journey maps, interviews, usability tests, surveys, A/B tests, card sorting, and Jobs-to-be-Done, a way to describe what users are trying to accomplish.

In plain words
What is it for?
Use it to create personas, plan interviews and usability sessions, map customer journeys, organise card-sorting studies, and define user needs.
Why use it?
It helps replace guesses about users with structured evidence. It also helps choose a research method that fits the question, such as interviews for discovery or usability tests for finding design problems.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter; mentions Claude Code.

Part of the ork plugin — 111 skills, 38 commands, 36 agents, 32 hooks shipped together

Good fit Use it to create personas, plan interviews and usability sessions, map customer journeys, organise card-sorting studies, and define user needs.

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

Made for: Claude Code.

Or install ork, the plugin that ships this one along with the rest of its 111 skills, 38 commands, 36 agents, 32 hooks.

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/yonatangross/orchestkit/user-research/github.svg)](https://agentmods.dev/skills/yonatangross/orchestkit/user-research)
Your own site
<a href="https://agentmods.dev/skills/yonatangross/orchestkit/user-research"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/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/yonatangross/orchestkit/user-research"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/user-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,419 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.00044 $0.01419
Opus 5.5 $0.00018 $0.00568
Sonnet 5.5 $0.00009 $0.00284
Haiku 4.5 $0.00004 $0.00142

Measured 1mo ago against content hash 9f4fe5a88038, 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 1mo 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/ork/skills/user-research/SKILL.md · 182 lines

How it starts

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

User Research

Frameworks for building deep user understanding through structured research methods. Covers personas, journey mapping, interviews, usability testing, and Jobs-to-be-Done.

Research Method Selection

Choose the right method for your question:

Method When to Use Sample Size Time Output
User Interviews Early discovery, deep understanding 5-8 2-3 weeks Qualitative insights
Usability Testing Validate designs, find issues 5-10 1-2 weeks Actionable fixes
Surveys Quantify attitudes, preferences 100+ 1-2 weeks Statistical data
Card Sorting Information architecture 15-30 1 week IA recommendations
A/B Testing Compare alternatives 1000+ 2-4 weeks Statistical winner

Rule of thumb: Start with interviews (5-8 participants) to discover unknowns. Switch to surveys once you have hypotheses to validate.

Persona Quick Reference

Personas are fictional composites built from research synthesis. Keep to 3-5 max.

## Persona: [Name]

### Demographics
- Age: [Range]
- Role: [Job title]
- Company: [Type/size]
- Tech savviness: [Low/Medium/High]

### Quote
> "[Characteristic statement that captures their mindset]"

### Goals
1. [Primary goal - what success looks like]
2. [Secondary goal]

### Pain Points
1. [Frustration with current state]
2. [Obstacle they face]

### Key Insight
[The most important thing to remember about this persona]

Incorrect — vague persona without goals:

Persona: Sarah, Age 35, Marketing Manager. Likes social media and coffee.

Correct — actionable persona with goals and pain points:

Persona: DevOps Dana
Quote: "I don't have time for tools that create more work than they save."
Goals: Reduce deployment failures, give devs self-service capabilities
Pain Points: Alert fatigue from false positives, context-switching between 10+ tools
Key Insight: Evaluates tools by "time saved vs. time invested" — needs immediate value.

Read the full file on GitHub · 182 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. 1mo ago First seen · 182 lines · 44 tokens per session scan A 9f4fe5a88038

Subscribe to this mod's changes

user-research is a skill published in the GitHub repository yonatangross/orchestkit (298 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,419 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-09-05.

Related

Other skills, from other repositories