← User IntuitionCONTENT HISTORY

Update to User Intuition

Snapshot Nov 4, 2026 · 00:13 UTC · version 1.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save User Intuition and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user wants a read-only status snapshot of User Intuition studies or interviews.",
  "included_files": [],
  "name": "monitor-fielding",
  "skill_md_contents": "---\nname: monitor-fielding\ndescription: Use when the user wants a read-only status snapshot of User Intuition studies or interviews.\nallowed-tools: Read\n---\n\nWhen the user asks for fielding status:\n\n1. Record the snapshot time. Call `list_studies`, paginating when necessary. Use response totals rather than counting only the current page.\n2. For each study in scope, call `list_interviews` with its `study_id`. Use `status` and `quality` filters when the user asks for a breakdown.\n3. 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.\n4. 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.\n5. 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.\n"
}

SHA-256 of public snapshot: adbbf5042ddc0746154656c90760e5500430ad70c0b0000e53c34662f4416930