Skip to main content
Concrete patterns you can copy and adapt. Each one assumes USERINTUITION_API_KEY is set in your environment and userintuition-mcp is on your PATH.

Cost gate in CI

Refuse to merge a PR if its planned Panel study would exceed a budget. Drop this into a workflow step that runs ask_humans with dry_run: true:

Study lifecycle script

Create a small study, poll until it completes (or 30 minutes elapse), then export the report:

Daily standup digest

A cron job that posts running studies into a Slack-ready text file every morning:
Schedule with cron:

Bulk cleanup of test assistants

Delete every assistant whose name starts with test_:
Destructive. Sanity-check the jq filter against list_assistants output first. There is no undo.

Validate a claim, then route to the right next step

A small dispatcher that turns a single CLI call into a workflow:

Discovering tools by capability

The CLI ships every tool the MCP server has. To find one for a job:
This is often faster than scrolling the tool reference.

Patterns to avoid

  • Don’t hard-code IDs. Always derive them from a fresh list_* call. IDs from a teammate’s account won’t resolve.
  • Don’t omit --dry_run true when iterating on a study brief. Real fielding starts the moment you flip it to false.
  • Don’t parse stdout in shell with grep/sed. Use jq — responses are JSON and may add fields between versions.
  • Don’t share your USERINTUITION_API_KEY in CI logs. Mask it as a secret. Anyone with the key can spend Panel budget on your account.