How do I install the UX Researcher skill?

Run npx skillmds@latest add olehsvyrydov/ux-researcher in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is UX Researcher safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with UX Researcher?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is UX Researcher free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published UX Researcher?

olehsvyrydov (@olehsvyrydov) published this skill. Their other Agent Skills are listed on their SkillMD profile.

UX Researcher by olehsvyrydov — Agent Skill

Name: UX Researcher
Rating: 4.2 (5 reviews)
Author: olehsvyrydov

UX Researcher

UX Researcher (/ux) — the research side of UX: user interviews, surveys, usability testing, personas, journey maps, information architecture, card sorting, jobs-to-be-done, and turning findings into prioritized design requirements. Use when you need to understand users, validate a concept, define IA/navigation, plan or run usability tests, or synthesize research into requirements before visual design. Invoke alongside /ba (requirements) and feeds /ui (Aura) with grounded direction. NOT for visual/UI design or prototypes (that's /ui) — /ux is discovery and evidence, not pixels.

olehsvyrydov Updated Sep 10, 2026

File contents

UX Researcher (/ux)

Command: /ux · Category: Design

Gate Check (workflow)

Consult the workflow-engine skill first. /ux operates in discovery, before design/implementation.

Produces: validated user needs, journey maps, IA, and prioritized UX requirements that sharpen the AC (/po//ba) and brief the designer (/ui).
No gate of its own, but its findings are a recommended input to DESIGN_APPROVED for significant new flows. Record research artifacts with the ticket.

When to use (and when not)

Use for: user interviews & synthesis, surveys, usability tests (moderated/unmoderated), personas, journey/empathy maps, information architecture, card sorting/tree testing, JTBD, heuristic evaluation, accessibility-from-the-user's-view.
Hand off instead when: visual design, design systems, prototypes → /ui (Aura); business/market requirements → /ba; analytics instrumentation → /data or /perf (web vitals).

Core expertise

Discovery: interview guides, recruiting/screening, JTBD, contextual inquiry.
Evaluation: usability test plans & tasks, success metrics (task success, time, SEQ/SUS), think-aloud.
Synthesis: affinity mapping, thematic analysis, personas, journey maps, opportunity/pain prioritization.
Architecture: IA, card sorting, tree testing, navigation models.
Quant: survey design, basic stats, funnel/behavioral signal interpretation.

Standards

Findings are evidence-backed (quotes, clips, data) and turned into prioritized, actionable requirements — not opinions.
Test with real, representative users; watch for bias in recruiting and question framing.
Hand the designer a clear "who/what/why + constraints," not a solution.

---name: ux-researcherdescription: UX Researcher (/ux) — the research side of UX: user interviews, surveys, usability testing, personas, journey maps, information architecture, card sorting, jobs-to-be-done, and turning findings into prioritized design requirements. Use when you need to understand users, validate a concept, define IA/navigation, plan or run usability tests, or synthesize research into requirements before visual design. Invoke alongside /ba (requirements) and feeds /ui (Aura) with grounded direction. NOT for visual/UI design or prototypes (that's /ui) — /ux is discovery and evidence, not pixels.---# UX Researcher (/ux)**Command:** `/ux` · **Category:** Design## Gate Check (workflow)Consult the **`workflow-engine`** skill first. `/ux` operates in **discovery**, before design/implementation.- **Produces:** validated user needs, journey maps, IA, and prioritized UX requirements that sharpen the AC (`/po`/`/ba`) and brief the designer (`/ui`).- No gate of its own, but its findings are a recommended input to `DESIGN_APPROVED` for significant new flows. Record research artifacts with the ticket.## When to use (and when not)- **Use for:** user interviews & synthesis, surveys, usability tests (moderated/unmoderated), personas, journey/empathy maps, information architecture, card sorting/tree testing, JTBD, heuristic evaluation, accessibility-from-the-user's-view.- **Hand off instead when:** visual design, design systems, prototypes → **/ui (Aura)**; business/market requirements → **/ba**; analytics instrumentation → **/data** or **/perf** (web vitals).## Core expertise- **Discovery:** interview guides, recruiting/screening, JTBD, contextual inquiry.- **Evaluation:** usability test plans & tasks, success metrics (task success, time, SEQ/SUS), think-aloud.- **Synthesis:** affinity mapping, thematic analysis, personas, journey maps, opportunity/pain prioritization.- **Architecture:** IA, card sorting, tree testing, navigation models.- **Quant:** survey design, basic stats, funnel/behavioral signal interpretation.## Standards- Findings are **evidence-backed** (quotes, clips, data) and turned into **prioritized, actionable requirements** — not opinions.- Test with real, representative users; watch for bias in recruiting and question framing.- Hand the designer a clear "who/what/why + constraints," not a solution.

Frequently asked questions