> ## 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.

# Monitor fielding

> Use when the user wants a read-only status snapshot of User Intuition studies or interviews.

Use when the user wants a read-only status snapshot of User Intuition studies or interviews.

[Fetch raw SKILL.md](https://raw.githubusercontent.com/user-intuition/skills/2a18ba4a8f54b0ac3de2ec8a92602ec03043d699/plugins/user-intuition-research/skills/monitor-fielding/SKILL.md) · [Source](https://github.com/user-intuition/skills/blob/2a18ba4a8f54b0ac3de2ec8a92602ec03043d699/plugins/user-intuition-research/skills/monitor-fielding/SKILL.md) · [All skills](/skills/library)

Requires an authenticated [User Intuition MCP connection](/mcp-server/quickstart). Install the raw file as `monitor-fielding/SKILL.md` inside your agent client's supported skills directory. The raw file is the installable artifact; this page is its documentation wrapper.

SHA-256: `b1ebc1a67fede393d63abf87bdd9600e10883895dee6d346ea92008dae32be18`

## Instructions

```markdown theme={null}
---
name: monitor-fielding
description: Use when the user wants a read-only status snapshot of User Intuition studies or interviews.
---

When the user asks for fielding status:

1. Record the snapshot time. Call `list_studies`, paginating when necessary. Use response totals rather than counting only the current page.
2. For each study in scope, call `list_interviews` with its `study_id`. Use `status` and `quality` filters when the user asks for a breakdown.
3. Present a compact table with study name, recruiting method, `fielding_status`, interview count, quality distribution, and the snapshot time. Keep `provisioning_status` separate: provisioned means interviews can run, not that recruitment started.
4. For BYOP, report `fielding_status: unavailable` as such and use participant/interview facts instead of inventing a study-level recruitment state. Flag no completions or a high Fair/Poor share as observations, not diagnoses. Zero completions alone is not proof that recruitment is stalled.
5. Keep the workflow read-only. Offer `pause_study`, `resume_study`, `stop_study`, or report generation as follow-ups, but do not mutate unless the user explicitly asks.
```


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