MCPInstall

user-discovery-research

Master user research methodologies, customer interviews, persona development, and journey mapping. Understand customer problems deeply before building.

Installs
55
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/pluginagentmarketplace/custom-plugin-product-manager --skill user-discovery-research
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads user-discovery-research automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

User Discovery & Research Skill

Become an expert at understanding customers deeply. Master interview techniques, extract meaningful insights, create accurate personas, and map customer journeys.

Interview Mastery

30-60 Minute Interview Structure

Opening (5 min) - Build rapport

  • "Thanks for time. I want to understand your experience with [topic]."
  • Warm conversation (not a interrogation)
  • Note-taking permission, recording permission

Context (10 min) - Background

  • "Tell me about your role..."
  • "What does a typical day look like?"
  • "What tools do you use?"
  • "Who do you work with?"

Deep Dive (15-20 min) - Core problem

  • "Walk me through how you currently [solve X]..."
  • "Tell me about the last time [problem] happened..."
  • "What frustrates you most about [current solution]?"
  • "How often does [issue] occur?"

Impact Questions (5-10 min) - Consequence

  • "What's the impact when [problem] happens?"
  • "How much time do you spend on [workaround]?"
  • "What's the cost if [issue] isn't resolved?"

Exploration (5-10 min) - Future state

  • "What would make your life easier?"
  • "Describe your ideal [solution]..."
  • "What would you be willing to pay to solve [problem]?"

Closing (3-5 min) - Wrap up

  • "Is there anything else important?"
  • "Can I follow up?"
  • "Can you introduce me to others?"

Interview Techniques

The Socratic Method

  • Ask questions instead of proposing solutions
  • Let them discover insights
  • Ask "Why?" 5 times to get root cause
  • Example:
    • Q: "Why do you use spreadsheets?"
    • A: "It's what we have"
    • Q: "Why not use a database?"
    • A: "Don't have budget"
    • Q: "Why no budget?"
    • A: "ROI wasn't clear"
    • → Real problem: ROI uncertainty

Listen 70%, Talk 30%

  • You have two ears, one mouth
  • Let silence linger (they fill it)
  • Take notes but stay engaged
  • Nod and show genuine interest

Avoid Leading Questions

  • ❌ "Don't you think mobile is important?"
  • ✅ "What devices do you primarily use?"
  • ❌ "Wouldn't X solve your problem?"
  • ✅ "What would an ideal solution look like?"

Look for Emotions

  • Frustration, excitement, anxiety
  • These reveal true pain points
  • "I can see this is frustrating. Tell me more..."

Interview Logistics

Recruitment:

  • Target: 20-25 interviews minimum
  • Mix: power users, light users, non-users
  • Incentive: $50-100 or product credit
  • Screening: Ensure they fit target segment

Recording & Notes:

  • Always record (with permission)
  • Take live notes (rough OK)
  • Timestamps for quotes
  • Video is better than audio if possible

Debrief Immediately:

  • Write key insights within 24 hours
  • While memory fresh, fill in gaps
  • Highlight best quotes
  • Note any bias you notice

Synthesis & Analysis

Affinity Mapping

Process:

  1. Write every quote/insight on sticky note
  2. Group similar insights
  3. Find themes
  4. Rank by frequency/impact
  5. Extract top 10-15 themes

Example themes:

  • Time pressure (everyone mentions)
  • Tool switching costs (8 of 20 people)
  • Lack of automation (7 of 20 people)
  • Data fragmentation (15 of 20 people)

Persona Development

5 Element Persona:

  1. Demographics

    • Role, company size, industry
    • Education, experience level
    • Geographic location
    • Company revenue/growth stage
  2. Goals & Motivations

    • What's their job-to-be-done?
    • How is success measured?
    • What drives them?
    • What keeps them up at night?
  3. Challenges & Pain Points

    • Top 3 problems (research-backed)
    • Current workarounds
    • Cost of problem (time, money, stress)
    • What they've tried
  4. Current Solutions

    • What tools do they use?
    • How do they work together?
    • What's missing?
    • Tech stack
  5. Quote & Story

    • Real, powerful quote
    • Day-in-the-life scenario
    • Decision journey story

Persona Document Format:

  • 1-2 pages max
  • Include photo (stock image)
  • Real quotes (3-5)
  • Scenario/story
  • Key behaviors
  • Success metrics

Journey Mapping

Current State Journey (As-Is)

Stages:

  1. Awareness - Realizes problem exists
  2. Consideration - Researches solutions
  3. Purchase - Buys solution
  4. Onboarding - Learns to use
  5. Usage - Day-to-day work
  6. Support - Gets help
  7. Renewal - Continues or leaves

For Each Stage Map:

Actions - What customer does

  • Searches online
  • Talks to colleagues
  • Evaluates options
  • etc.

Emotions - How they feel

  • Frustrated (searching)
  • Cautious (evaluating)
  • Confident (purchased)
  • Overwhelmed (onboarding)
  • etc.

Touchpoints - Interactions

  • Website
  • Sales calls
  • Email
  • Product UI
  • Support chat
  • etc.

Pain Points - Frustrations

  • Hard to find info
  • Slow response times
  • Confusing UI
  • etc.

Opportunities - Where you can help

  • Better documentation
  • Faster support
  • Simpler onboarding
  • etc.

Research Methods

Quantitative

Surveys

  • Reach: 100+ people
  • Speed: 2-3 days
  • Depth: Medium
  • Best for: Validation, scale

Net Promoter Score (NPS)

  • "How likely to recommend?" (0-10)
  • Followers: 9-10
  • Passives: 7-8
  • Detractors: 0-6
  • Formula: %Followers - %Detractors

Qualitative

Interviews

  • Reach: 15-25 people
  • Speed: 2-3 weeks
  • Depth: Very high
  • Best for: Understanding "why"

Focus Groups

  • Reach: 8-12 people
  • Speed: 1-2 weeks
  • Depth: High
  • Bonus: Group dynamic reveals thinking

Observations

  • Reach: 3-5 people
  • Speed: 2-3 days
  • Depth: Very high
  • Best for: Seeing vs. hearing

Mixed Methods

Combine research methods:

  • Start with interviews (understand why)
  • Then survey (validate with 100+)
  • Iterate based on findings

Key Insights Extraction

Five Key Metrics

  1. Problem Severity

    • How badly does it hurt?
    • Frequency of problem
    • Impact magnitude
    • Urgency to solve
  2. Current Solution Satisfaction

    • Is current approach acceptable?
    • What's missing?
    • Workarounds needed?
    • Would switch if better option?
  3. Willingness to Pay

    • What would they pay for solution?
    • Price sensitivity?
    • ROI expectations?
  4. Decision Making

    • Who decides?
    • Who influences?
    • Budget process?
    • Timeline?
  5. Switching Costs

    • What prevents switching?
    • Integration challenges?
    • Learning curve acceptable?
    • Migration effort?

Top 5 Questions to Answer

From your research:

  1. What's the #1 problem?
  2. Who has the problem most acutely?
  3. How do they solve it today?
  4. What would ideal solution look like?
  5. Would they pay for it, and how much?

Troubleshooting

Yaygın Hatalar & Çözümler

HataOlası SebepÇözüm
Düşük interview katılımıYanlış incentive$50-100 gift card
Yüzeysel insightsLeading questions"Why?" 5x sor
Conflicting feedbackMixed segmentsSegment-based analysis
Persona genericInsufficient data+10 interview

Debug Checklist

[ ] Sample size yeterli mi? (min 15-20)
[ ] Questions leading değil mi?
[ ] Recording consent alındı mı?
[ ] Synthesis 24h içinde yapıldı mı?
[ ] Bias check yapıldı mı?

Recovery Procedures

  1. Low Participation → Adjust incentive or channel
  2. Conflicting Data → Segment by user type
  3. Interviewer Bias → Add second interviewer

Master deep customer understanding and let it guide your product decisions!

FAQ

What does the user-discovery-research skill do?

Master user research methodologies, customer interviews, persona development, and journey mapping. Understand customer problems deeply before building.

How do I install user-discovery-research?

Run npx skills add https://github.com/pluginagentmarketplace/custom-plugin-product-manager --skill user-discovery-research in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/user-discovery-research/ (personal) or .claude/skills/user-discovery-research/ (project).

Which AI agents can use user-discovery-research?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is user-discovery-research safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains user-discovery-research?

It is published by pluginagentmarketplace in pluginagentmarketplace/custom-plugin-product-manager. It has 55 recorded installs.

More from pluginagentmarketplace/custom-plugin-product-manager

View all →

requirements-specification

pluginagentmarketplace/custom-plugin-product-manager

Master requirements gathering, user story writing, acceptance criteria definition, and scope management. Transform insights into clear, actionable specifications.

Docs & Writing236 installs

leadership-stakeholder-management

pluginagentmarketplace/custom-plugin-product-manager

Master stakeholder management, executive communication, cross-functional alignment, and product advocacy. Lead effectively across your organization.

42 installs

product-strategy

pluginagentmarketplace/custom-plugin-product-manager

Master product strategy, market analysis, competitive positioning, and long-term product vision. Define business models and craft go-to-market strategies that drive success.

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。