Agent skill · Design & Presentation

ux-research

Plan and execute user research including research planning, recruiting, interview design, qualitative synthesis, and translating findings into product decisions. Use this skill whenever the user wants to plan user research, design interviews, recruit participants, conduct discovery, run formative research, or synthesize qualitative findings. Triggers on user research, UX research, user interviews, discovery research, generative research, formative research, qualitative research, user insights, research synthesis, recruitment, interview guide, jobs to be done. Also triggers when product decisio

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill ux-research --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/ux-research/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# UX Research Plan and execute user research that produces decisions, not just decks. Stack-agnostic. Tool-agnostic. This skill is for generative and discovery research. For testing existing designs, use `usability-testing`. For mapping the full customer experience, use `journey-mapping`. --- ## When to use - Starting a new product or major feature without sufficient user understanding - Diagnosing why something isn't working without clear data signals - Generating new opportunity hypotheses - Validating a strategic direction before significant investment - Building empathy across a team that's drifted from users - Translating "we should talk to users" intent into a real plan ## When NOT to use - Testing a specific design or prototype (use `usability-testing`) - Mapping the full journey of an existing experience (use `journey-mapping`) - Quantitative measurement (use `analytics-strategy`) - Conversion testing (use `cro-optimization`) --- ## Required inputs - The research question(s) - what you need to answer - Stakeholder buy-in (who needs the findings, what decisions hinge on them) - Access to users (current customers, prospects, lapsed users, target segments) - Timeline and budge

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 6 phases
  5. 1. Frame the question
  6. 2. Choose the method
  7. 3. Recruit
  8. 4. Conduct
  9. 5. Synthesize
  10. 6. Communicate
  11. Workflow
  12. Failure patterns
  13. Output format
  14. Reference files
Ships with 1 file
  • references/interview-guide-template.md
More from claude-skills
All skills →
About this skill
What does the ux-research skill do?

Plan and execute user research including research planning, recruiting, interview design, qualitative synthesis, and translating findings into product decisions. Use this skill whenever the user wants to plan user research, design interviews, recruit participants, conduct discovery, run formative research, or synthesize qualitative findings. Triggers on user research, UX research, user interviews, discovery research, generative research, formative research, qualitative research, user insights, research synthesis, recruitment, interview guide, jobs to be done. Also triggers when product decisio

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill ux-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going