Skip to content

Agent Operating Guide

/coach-readiness-check

Verify a tenant is set up properly, admin users, required item types, MCP reachability, OAuth clients, and storage, reporting each gap with a specific remediation.

The pre-launch checklist for a new tenant. The skill runs a sequence of structural checks, an admin user exists, the schema has the item types your installed plugins need, the MCP server answers, OAuth clients are configured, the storage bucket is set, and reports any gaps. Each check is binary: pass or fail, with a specific remediation on every failure. There are no warnings and no auto-fixes; it’s read-only, so it tells you what to close and you close it.

Before launching a tenant, and again after every major schema change to catch drift. Run it whenever you want a single answer to “is this tenant ready?”

Flag Required Notes
--scope basic|with-plugins|full No How deep to check. Default with-plugins. basic is minimum-viable tenant setup; with-plugins adds the item types installed plugins require; full adds optional best-practices (a user per role, built search indexes, a non-default brand color and logo).

/coach-readiness-check runs the with-plugins checks and prints a report: pass and fail counts up top, then one card per failure with the check name, what it observed, and how to fix it (a specific skill to run, UI steps, or opening a ticket for anything the plugin can’t fix). A fully-configured tenant gets a single line: “Tenant is ready for launch.”

  • Read-only by design: it never auto-fixes anything, it only reports. Re-run it after schema changes to catch drift.
  • Every failure carries a concrete next step: the exact skill to run, the UI navigation, or a ticket via /coach-ticket-open for gaps the plugin can’t close.
  • It feeds the onboarding-checklist live artifact, which shows the rolling status of these checks over time.