> ## Documentation Index
> Fetch the complete documentation index at: https://docs.userintuition.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# User Intuition Skills

> Pre-built agent workflows for using the User Intuition MCP server safely and consistently — drop in, no glue code required.

User Intuition **skills** are short, copy-pasteable instruction files that teach a compatible AI agent *how* to drive the [MCP server](/mcp-server/overview) for a specific research workflow. Connect the hosted OAuth endpoint first when the client supports it; local stdio remains available for clients that need a local process.

Where the MCP server gives an agent the *tools*, a skill gives it the *play*. The skill is the difference between "the agent can call `create_study`" and "the agent knows to ask whether you want Panel or BYOP recruitment, conduct the `customize_study` conversation, verify the saved study, and dry-run panel cost before requesting launch approval."

## When skills help

* **Repeatable workflows.** Creating a study from a brief, screening panel respondents, generating an insights report — anything you do more than twice.
* **Cross-team consistency.** Two PMs on different machines run the same workflow the same way because the skill ships the playbook.
* **Onboarding.** A new teammate installs the skills and immediately runs the team's standard research patterns.

## How skills work

A skill is a Markdown file with YAML frontmatter. The frontmatter tells the agent *when* the skill applies; the body tells it *how* to execute. Example shape:

```markdown theme={null}
---
name: field-a-panel
description: Use when the user wants to recruit respondents from the User Intuition panel for an existing Panel study.
---

When the user wants to field a panel:

1. Verify the study is a provisioned Panel study via `get_study`.
2. Return the complete persisted plan and obtain approval of that exact version.
3. Ask the user to choose one launch country; never infer it.
4. Call `estimate_panel` and show the resolved country, language, cost, and timeline.
5. Wait for explicit approval of the estimate, then launch with its `estimate_id` using the same country.
```

Agents that support skills load the frontmatter at session start, then read the body when the description matches the user's request.

## Installing skills

<Tabs>
  <Tab title="Claude Code (plugin marketplace)">
    One command installs all ten skills, with updates delivered on marketplace refresh:

    ```
    /plugin marketplace add user-intuition/skills
    /plugin install user-intuition-research@user-intuition
    ```

    Source: [github.com/user-intuition/skills](https://github.com/user-intuition/skills).
  </Tab>

  <Tab title="Agent-native">
    The [skills library](/skills/library) is a compact index. Each workflow has a separate documentation page and a raw, installable skill file. Tell your agent:

    > Fetch `https://raw.githubusercontent.com/user-intuition/skills/main/catalog.json`, select the skill matching this task, and fetch its raw `SKILL.md`. Install it in the skills directory supported by this agent client.

    Load only the selected workflow. A docs `.md` export includes explanatory page content; use its raw-file link when installing a skill.
  </Tab>

  <Tab title="Claude Code (single skill)">
    Claude Code discovers skills as one directory per skill with a `SKILL.md` entrypoint — a flat `.claude/skills/<name>.md` file is not discovered. Fetch the raw skill linked from its page in the [library](/skills/library) into `.claude/skills/<name>/SKILL.md` (project-local) or `~/.claude/skills/<name>/SKILL.md` (global):

    ```bash theme={null}
    mkdir -p ~/.claude/skills/field-a-panel
    # paste the skill into ~/.claude/skills/field-a-panel/SKILL.md
    ```

    Claude Code auto-discovers skills on next session start.
  </Tab>

  <Tab title="Cursor">
    Cursor Project Rules live in `.cursor/rules/<name>.mdc` (the `.mdc` extension matters). Translate the skill's frontmatter into rule metadata rather than dropping it — carry the skill's `description` over, and set `alwaysApply: false` so Cursor applies the rule only when the description matches the task:

    ```markdown theme={null}
    ---
    description: Use when the user wants to recruit respondents from the User Intuition panel for an existing Panel study.
    alwaysApply: false
    ---

    <paste the skill body here>
    ```

    ```bash theme={null}
    mkdir -p .cursor/rules
    # save as .cursor/rules/field-a-panel.mdc
    ```
  </Tab>

  <Tab title="Claude Desktop">
    Claude Desktop doesn't natively support skill files yet — paste the body of the skill into a custom **Project** instructions field. The agent will follow it for the duration of that project's chats.
  </Tab>
</Tabs>

## What's in the library

The [skills library](/skills/library) covers the research loop. Existing workflows retain their MCP instructions; retrieval and search discover the released schemas, and illustrative B2/C1 adapters still need release verification:

<CardGroup cols={2}>
  <Card title="create-study-from-brief" href="/skills/create-study-from-brief">
    Turn a research brief into a launch-ready interview study.
  </Card>

  <Card title="design-screeners" href="/skills/design-screeners">
    Recruit exactly the right respondents — panel and custom screeners, done safely.
  </Card>

  <Card title="field-a-panel" href="/skills/field-a-panel">
    Recruit N respondents from the panel, with cost approved before any spend.
  </Card>

  <Card title="invite-your-own-participants" href="/skills/invite-your-own-participants">
    Interview your own customers — invites, share links, and rewards (BYOP).
  </Card>

  <Card title="run-a-concept-test" href="/skills/run-a-concept-test">
    Put a concept, prototype, or landing page in front of participants.
  </Card>

  <Card title="monitor-fielding" href="/skills/monitor-fielding">
    Daily digest of every fielding study — progress, quality, stalls.
  </Card>

  <Card title="analyze-completed-study" href="/skills/analyze-completed-study">
    From transcripts to stakeholder-ready findings, with real quotes only.
  </Card>

  <Card title="curate-interview-quality" href="/skills/curate-interview-quality">
    Review low-quality interviews and delete only the exact interviews the user confirms.
  </Card>
</CardGroup>

## Retrieve and search existing evidence

* [Retrieve study results](/skills/retrieve-study-results): choose the report view needed and follow source references without regenerating analysis.
* [Search research](/skills/search-research): find prior findings and participant responses, inspect coverage, and retrieve sources before citing them.

## Skill vs MCP vs CLI — which goes where

| You want… | Use |
| - | - |
| An agent to *autonomously* run a research workflow from a vague prompt | **Skill** (built on MCP) |
| An agent to call User Intuition tools when you ask, with you in the loop | **MCP** alone |
| To run a tool from a shell script, CI job, or cron | **CLI** |
| To call User Intuition from your own backend code | **REST API** |

Skills sit on top of MCP, while the MCP study-design workflow intentionally routes through the same Customize Plan backend used by the dashboard. The CLI and raw REST API are separate integration surfaces and may expose lower-level fields that MCP does not. Pick the highest level that gets the job done.

## Next steps

<CardGroup cols={2}>
  <Card title="Skills library" icon="book" href="/skills/library">
    Browse and copy ready-to-use skills.
  </Card>

  <Card title="MCP quickstart" icon="rocket" href="/mcp-server/quickstart">
    Skills require an MCP-connected client. Wire one up first.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.