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.
User personas, customer journey maps, interview guides, usability testing, and card sorting.
$ npx skills add yonatangross/orchestkit --skill user-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yonatangross/orchestkit user-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "user-research" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/user-research into .claude/skills/user-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yonatangross/orchestkit/tree/main/src/skills/user-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yonatangross/orchestkit --skill user-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yonatangross/orchestkit user-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/skills/user-research .agents/skills/user-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "user-research" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/user-research into .agents/skills/user-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yonatangross/orchestkit --skill user-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yonatangross/orchestkit user-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/skills/user-research .cursor/skills/user-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "user-research" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/user-research into .cursor/skills/user-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yonatangross/orchestkit.git --path src/skills/user-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yonatangross/orchestkit --skill user-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yonatangross/orchestkit user-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/skills/user-research .gemini/skills/user-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "user-research" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/user-research into .gemini/skills/user-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yonatangross/orchestkit user-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yonatangross/orchestkit --skill user-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/skills/user-research .github/skills/user-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "user-research" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/user-research into .github/skills/user-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yonatangross/orchestkit --skill user-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yonatangross/orchestkit user-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/skills/user-research .opencode/skills/user-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "user-research" agent skill from https://github.com/yonatangross/orchestkit/tree/main/src/skills/user-research into .opencode/skills/user-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
user-researchUser 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. 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.
Read from SKILL.md and the folder at commit 02bbf9a. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWebFetchWebSearchFrom allowed-tools in the SKILL.md frontmatter.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Claude Code 2.1.277+.
From compatibility in the SKILL.md frontmatter.
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.
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.
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.
The full file from yonatangross/orchestkit at commit 02bbf9a, republished under its MIT licence (© yonatangross). 338 words, ~1,551 tokens.
.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.Frameworks for building deep user understanding through structured research methods. Covers personas, journey mapping, interviews, usability testing, and Jobs-to-be-Done.
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.
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.Maps the end-to-end experience for a specific persona and scenario.
## 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
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:
| Dimension | Description |
|---|---|
| Functional | Practical task to accomplish |
| Emotional | How the user wants to feel |
| Social | How the user wants to be perceived |
Opportunity Score: Importance + (Importance - Satisfaction) — scores > 10 indicate high-opportunity areas.
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 |
+-------------------------+-------------------------------+| Do | Don't |
|---|---|
| Ask open-ended questions | Ask leading questions |
| Ask "why" and "how" | Accept surface answers |
| Follow interesting threads | Stick rigidly to script |
| Take verbatim notes | Paraphrase or interpret |
Standard interview arc: Warm-up (5 min) → Context setting (10 min) → Deep dive (25 min) → Wrap-up (5 min)
Read these files for detailed guidance:
ork:write-prd — Translate research insights into structured product requirementsork: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
SKILL.md and 8 other files (references) in src/skills/user-research of yonatangross/orchestkit.
Open the folder on GitHubat commit 02bbf9a
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| User Research this skillyonatangross/orchestkit | 290 | — | ~1.6k | Automated safety check: Pass | MIT | |
| User Story Mappingdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.8k | Automated safety check: Pass | Custom licence | |
| Super Product Ownersyahiidkamil/Software-Engineer-AI-Agent-Atlas | 401 | — | ~7.9k | Automated safety check: Pass | None | |
| Customer Journey Mapping Workshopdeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~4.7k | Automated safety check: Pass | Custom licence | |
| Design Sprintwondelai/skills | 2.4k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Discovery Researchandreaskelm/pm-brain | 234 | — | ~1.2k | Automated safety check: Pass | Custom licence |
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
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 →…
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.
wondelai/skills
Run a structured 5-day process to prototype, test, and validate product ideas with real users.
andreaskelm/pm-brain
Support discovery and research workflows using PM Brain’s discovery frameworks (research interviews, continuous discovery, JTBD, segmentation, opportunity assessment, idea validation…
menkesu/awesome-pm-skills
Designs customer interviews and turns the transcripts into decisions.
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.
yonatangross/orchestkit
ADR templates in the Nygard format with context, decision, consequences, and alternatives.
yonatangross/orchestkit
Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.
yonatangross/orchestkit
Structured review processes, conventional comments, language-specific checklists, and feedback templates.
yonatangross/orchestkit
Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.
yonatangross/orchestkit
Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.
Categories
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.
User Research fits situations like: building user understanding; mapping customer experiences; planning user research sessions; defining Jobs-to-Be-Done.
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.
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.
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.
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+..
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.
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.
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.
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.
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.
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.