MCPInstall

research

by openaiProductivity & Automation

Run fast, source-grounded UX research on the highest-signal problems users are experiencing with a user-specified digital product. Use when the user asks to research user pain, UX friction, onboarding issues, docs/help problems, developer experience friction, support pain, product workflow issues, or current user complaints for a named product.

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

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/openai/role-specific-plugins --skill 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 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.

Research

Run a fresh UX research scan for the product the user specifies.

Focus on current, evidence-backed user problems. Prioritize logged-in product experience, self-serve flows, onboarding, docs/help, developer experience, support friction, and product workflows.

Critical Overrides

  • Refer to the Plugin router $index before proceeding.
  • Follow $critical-overrides.

User Context

Before starting, load $user-context and run its preflight script when local shell access is available.

Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets as grounding material when relevant.

Do not inspect every saved reference. Inspect only what the current task needs.

Contract

  • Restate the product, audience, time horizon, and research scope before scanning.
  • Use public sources by default. Use internal sources when the connectors are available and the user request allows it.
  • Cite sources wherever available.
  • Separate observed evidence from inference.
  • Do not overclaim from anecdotes.
  • Do not return a dump of complaints. Tell a clear product story.
  • Say clearly when source access is missing or weak.

Workflow

  1. Restate the research scope.

  2. Search public sources:

  • Reddit
  • X/Twitter
  • Hacker News
  • Stack Overflow
  • GitHub issues/discussions
  • forums, blogs, reviews, YouTube comments, and developer communities where relevant
  1. Search internal sources when available:
  • Slack
  • Gong
  • Notion
  • Google Drive/docs
  • Linear/Jira/GitHub
  • support or CRM notes if available

  1. Cluster evidence into the highest-signal UX problems.

  2. Separate:

  • product UI/workflow friction
  • docs/help friction
  • onboarding friction
  • account, billing, permissions, or setup friction
  • developer/API/SDK friction
  • reliability/performance issues
  • feature requests

  1. Rank problems by severity, frequency, confidence, and product leverage.

  2. Tell a clear product story.

Output

Default to an in-chat research brief unless the user asks for another format.

Include:

  • Executive read: the core story in 5-7 sentences.
  • Ranked UX problems: for each problem, include the problem, user goal, surface, what breaks, evidence, severity, frequency signal, confidence, and recommended product move.
  • Source map: what was searched, what each source contributed, and where signal was weak.
  • Opportunity map: group recommendations into fix this week, fix this quarter, and needs deeper research.

Rules

  • Use citations wherever available.
  • Do not overclaim from anecdotes.
  • Separate loud complaints from frequent problems.
  • Separate UX friction from missing features.
  • Separate reliability/performance issues from UX workflow issues.
  • Mark internal-only evidence separately from public evidence.
  • Keep the brief sharp, specific, and easy to consume.

FAQ

What does the research skill do?

Run fast, source-grounded UX research on the highest-signal problems users are experiencing with a user-specified digital product. Use when the user asks to research user pain, UX friction, onboarding issues, docs/help problems, developer experience friction, support pain, product workflow issues, or current user complaints for a named product.

How do I install research?

Run npx skills add https://github.com/openai/role-specific-plugins --skill 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/research/ (personal) or .claude/skills/research/ (project).

Which AI agents can use 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 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 research?

It is published by openai in openai/role-specific-plugins. It has 63 recorded installs.

More from openai/role-specific-plugins

View all →

image-to-code

openai/role-specific-plugins

Implement a selected image, screenshot, mockup, or Image Gen reference as a faithful, responsive frontend.

Media & Creative184 installs

analyze-data-quality

openai/role-specific-plugins

Open the skill to read its SKILL.md instructions.

AI & Agents106 installs

visualize-data

openai/role-specific-plugins

Design, build, revise, or QA quantitative charts and figures. Use when an analytical answer needs visual judgment, whether for an inline answer, report, dashboard, notebook, or artifact.

Data & Databases100 installs

validate-data

openai/role-specific-plugins

Validate whether an analysis is accurate, well-supported, and ready to share or use for a decision. Use when reviewing methodology, calculations, comparisons, visuals, caveats, or conclusions.

AI & Agents98 installs

build-dashboard

openai/role-specific-plugins

Open the skill to read its SKILL.md instructions.

Data & Databases91 installs

product-business-analysis

openai/role-specific-plugins

Open the skill to read its SKILL.md instructions.

Business & Finance81 installs

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。

Productivity & Automation815.7K installs

lark-base

open.feishu.cn

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

Productivity & Automation815K installs

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）。

Productivity & Automation815K installs

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.

Productivity & Automation814.8K installs

lark-im

open.feishu.cn

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

Productivity & Automation814.1K installs