Agent skill

User Research

by yonatangross in yonatangross/orchestkit

User personas, customer journey maps, interview guides, usability testing, and card sorting.

MITAuto-check passedProduct & Project Management

Install User Research

skills CLI
$ npx skills add yonatangross/orchestkit --skill user-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yonatangross/orchestkit user-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/user-research .claude/skills/user-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
user-research
GitHub stars
290
Token cost
~1.6k tokens
SKILL.md length
338 words
Files
9 (incl. references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

User personas, customer journey maps, interview guides, usability testing, and card sorting.

  • Building user understanding
  • SKILL.md covers Research Method Selection, Persona Quick Reference, Journey Map Structure and JTBD Framework, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Mapping customer experiences

What it does

User Research is an agent skill from yonatangross/orchestkit. User personas, customer journey maps, interview guides, usability testing, and card sorting. Use when building user understanding, mapping customer experiences, planning user research sessions, or defining Jobs-to-Be-Done.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/interview-guide-template.md`, `references/journey-map-workshop.md` and `references/user-story-workshop-guide.md`). Compatibility notes: Claude Code 2.1.277+.

It sits in Product & Project Management, covering User research, User stories and Customer journey mapping. The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.

When your agent uses it

  • Building user understanding
  • Mapping customer experiences
  • Planning user research sessions
  • Defining Jobs-to-Be-Done

Example prompts

  • “/user-research”

Requirements

  • Compatibility (from SKILL.md): Claude Code 2.1.277+.
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, WebSearch

What it can do on your machine

Read from SKILL.md and the folder at commit 02bbf9a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • WebSearch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Claude Code 2.1.277+.

    From compatibility in the SKILL.md frontmatter.

Context cost

User Research loads about 1.6k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 338 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yonatangross/orchestkit at commit 02bbf9a, republished under its MIT licence (© yonatangross). 338 words, ~1,551 tokens.

Download SKILL.mdSave it as .claude/skills/user-research/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
user-research
description
User personas, customer journey maps, interview guides, usability testing, and card sorting. Use when building user understanding, mapping customer experiences, planning user research sessions, or defining Jobs-to-Be-Done.
allowed-tools
Read, Glob, Grep, WebFetch, WebSearch
compatibility
Claude Code 2.1.277+.
license
MIT
user-invocable
false
disable-model-invocation
false
metadata.owner-agent
product-strategist
metadata.category
document-asset-creation
metadata.version
1.0.0
metadata.author
OrchestKit
metadata.complexity
medium
metadata.tags
persona, journey-map, user-interview, usability, jtbd, card-sort, empathy-map, research

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:

MethodWhen to UseSample SizeTimeOutput
User InterviewsEarly discovery, deep understanding5-82-3 weeksQualitative insights
Usability TestingValidate designs, find issues5-101-2 weeksActionable fixes
SurveysQuantify attitudes, preferences100+1-2 weeksStatistical data
Card SortingInformation architecture15-301 weekIA recommendations
A/B TestingCompare alternatives1000+2-4 weeksStatistical 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.

markdown
## 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:

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

Correct — actionable persona with goals and pain points:

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

Journey Map Structure

Maps the end-to-end experience for a specific persona and scenario.

markdown
## Journey Map: [Journey Name]

### Persona + Scenario
[Which persona | What they're trying to accomplish]

### Stages: Aware → Consider → Purchase → Onboard → Use → Retain

For each stage:
- **Touchpoints:** [Channel/interaction point]
- **Actions:** [What user does]
- **Emotions:** [Satisfied / Neutral / Frustrated]
- **Pain Points:** [Friction]
- **Opportunities:** [How we improve]

Common B2B SaaS stages: Awareness → Evaluation → Purchase → Onboarding → Adoption → Expansion → Advocacy/Churn

JTBD Framework

People don't buy products — they hire them to do specific jobs.

JTBD Statement Format:

When [situation], I want to [motivation], so I can [expected outcome].

Example:

When I'm preparing for a board review, I want to quickly see revenue trends,
so I can answer questions confidently without scrambling for data.

Job Dimensions:

DimensionDescription
FunctionalPractical task to accomplish
EmotionalHow the user wants to feel
SocialHow the user wants to be perceived

Opportunity Score: Importance + (Importance - Satisfaction) — scores > 10 indicate high-opportunity areas.

Empathy Map

Quick tool for building shared understanding in workshops:

+-------------------------+-------------------------------+
|         SAYS            |            THINKS             |
| Direct quotes           | Worries and concerns          |
| Questions asked         | Aspirations                   |
+-------------------------+-------------------------------+
|         DOES            |            FEELS              |
| Observable actions      | Emotional state               |
| Workarounds             | Frustrations and delights     |
+-------------------------+-------------------------------+
|         PAINS           |            GAINS              |
| Fears and obstacles     | Wants and needs               |
+-------------------------+-------------------------------+

Interview Best Practices

DoDon't
Ask open-ended questionsAsk leading questions
Ask "why" and "how"Accept surface answers
Follow interesting threadsStick rigidly to script
Take verbatim notesParaphrase or interpret

Standard interview arc: Warm-up (5 min) → Context setting (10 min) → Deep dive (25 min) → Wrap-up (5 min)

Rules (Load On-Demand)

Read these files for detailed guidance:

References

  • ork:write-prd — Translate research insights into structured product requirements
  • ork:product-frameworks — Full PM framework suite (business cases, prioritization, metrics, OKRs)

Version: 1.0.0

© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in src/skills/user-research of yonatangross/orchestkit.

  • SKILL.md
  • references/interview-guide-template.md
  • references/journey-map-workshop.md
  • references/user-story-workshop-guide.md
  • rules/_sections.md
  • rules/research-journey-mapping.md
  • rules/research-personas.md
  • rules/research-user-interviews.md
  • test-cases.json

Open the folder on GitHubat commit 02bbf9a

Compare with similar skills

User Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

User Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
User Research this skillyonatangross/orchestkit290—~1.6kAutomated safety check: PassMIT
User Story Mappingdeanpeters/Product-Manager-Skills7.2k2 repos~2.8kAutomated safety check: PassCustom licence
Super Product Ownersyahiidkamil/Software-Engineer-AI-Agent-Atlas401—~7.9kAutomated safety check: PassNone
Customer Journey Mapping Workshopdeanpeters/Product-Manager-Skills7.2k1 repos~4.7kAutomated safety check: PassCustom licence
Design Sprintwondelai/skills2.4k—~3.8kAutomated safety check: PassMIT
Discovery Researchandreaskelm/pm-brain234—~1.2kAutomated safety check: PassCustom licence

Similar skills

  • User Story Mapping

    deanpeters/Product-Manager-Skills

    Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.

    7.2k GitHub starsUsed in 2 repos~2.8k tokens
    Product & Project ManagementAuto-check passed
  • Super Product Owner

    syahiidkamil/Software-Engineer-AI-Agent-Atlas

    Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs →…

    401 GitHub stars~7.9k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed
  • Customer Journey Mapping Workshop

    deanpeters/Product-Manager-Skills

    Walks a product manager through a customer journey map one question at a time, from persona and scenario to pain points and opportunities.

    7.2k GitHub starsUsed in 1 repo~4.7k tokens
    Product & Project ManagementAuto-check passed
  • Design Sprint

    wondelai/skills

    Run a structured 5-day process to prototype, test, and validate product ideas with real users.

    2.4k GitHub stars~3.8k tokensUpdated 28 days ago
    Product & Project ManagementAuto-check passed
  • Discovery Research

    andreaskelm/pm-brain

    Support discovery and research workflows using PM Brain’s discovery frameworks (research interviews, continuous discovery, JTBD, segmentation, opportunity assessment, idea validation…

    234 GitHub stars~1.2k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed
  • Customer Interviews

    menkesu/awesome-pm-skills

    Designs customer interviews and turns the transcripts into decisions.

    433 GitHub stars~4.4k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

More from yonatangross/orchestkit

All 108 skills in this repo
  • API Design

    yonatangross/orchestkit

    API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.

    290 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Architecture Decision Record

    yonatangross/orchestkit

    ADR templates in the Nygard format with context, decision, consequences, and alternatives.

    290 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Audit Full

    yonatangross/orchestkit

    Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.

    290 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes
  • Code Review Playbook

    yonatangross/orchestkit

    Structured review processes, conventional comments, language-specific checklists, and feedback templates.

    290 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    290 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes
  • Explore

    yonatangross/orchestkit

    Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.

    290 GitHub stars~3.9k tokensUpdated today
    Auto-check: notes

Questions about User Research

What does User Research do?

User personas, customer journey maps, interview guides, usability testing, and card sorting. User Research is an agent skill from yonatangross/orchestkit. User personas, customer journey maps, interview guides, usability testing, and card sorting.

When should I use User Research?

User Research fits situations like: building user understanding; mapping customer experiences; planning user research sessions; defining Jobs-to-Be-Done.

How do I install User Research in Claude Code?

Run `npx skills add yonatangross/orchestkit --skill user-research -a claude-code`. Or copy the skill folder (src/skills/user-research in yonatangross/orchestkit) into .claude/skills/user-research in your project. Claude Code loads it when a task matches its description.

How do I install User Research in Codex?

Run `npx skills add yonatangross/orchestkit --skill user-research -a codex`. Or copy the skill folder (src/skills/user-research in yonatangross/orchestkit) into .agents/skills/user-research in your project. Codex loads it when a task matches its description.

Can I use User Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yonatangross/orchestkit --skill user-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/user-research, .gemini/skills/user-research, .github/skills/user-research and .opencode/skills/user-research in your project.

What does User Research need to run?

SKILL.md names no scripts, command-line tools or credentials: User Research is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, WebSearch. Compatibility (from SKILL.md): Claude Code 2.1.277+..

Does User Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is User Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does User Research use?

User Research is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does User Research use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.3k tokens, read only when the agent opens those files.

What are the alternatives to User Research?

Skills that share tags, products or a category with User Research: User Story Mapping (deanpeters/Product-Manager-Skills, 7.2k stars), Super Product Owner (syahiidkamil/Software-Engineer-AI-Agent-Atlas, 401 stars), Customer Journey Mapping Workshop (deanpeters/Product-Manager-Skills, 7.2k stars) and Design Sprint (wondelai/skills, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains User Research?

yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 290 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.

Source: yonatangross/orchestkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.