From anchored
Diagnoses Anchored installation, MCP registration, and database health by running the anchored doctor command and summarizing results with fix instructions.
How this command is triggered — by the user, by Claude, or both
Slash command
/anchored:doctorThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
!`anchored doctor` Read the checklist and tell the user clearly: what's healthy, what's broken, and the exact command to fix each broken item. Don't just dump the raw output — summarize and highlight any `[ ]` lines.
!anchored doctor
Read the checklist and tell the user clearly: what's healthy, what's broken, and the exact command to fix each broken item. Don't just dump the raw output — summarize and highlight any [ ] lines.
npx claudepluginhub jholhewres/anchored --plugin anchored3plugins reuse this command
First indexed May 5, 2026
/preflightDiagnoses a Cortex environment by running the MCP doctor script, then explains each failing check and lists repair commands in dependency order.
/doctorRuns Schrute health checks and diagnostics via node script and MCP status tool. Reports pass/warn/fail results, engine status including mode/sessions/uptime, issues, and remediation steps.
/doctorDiagnose /gr plugin setup, MCP wiring, and API connectivity with optional quick or full mode.
/doctorPerforms comprehensive health diagnostics on an OrchestKit installation, validating manifest integrity, hooks, skills, agents, MCP servers, and more. Reports issues with severity levels and auto-remediation suggestions.
/lcm-doctorRuns lossless-claude diagnostics checking daemon, hooks, MCP server, and summarizer health. Displays status tables, adds Fix section for failures, and health summary.
/healthRuns mcp-memory doctor command via resolvers to check package version, installed payload, chatlog DB row count, and per-agent hook states; prints full output with one-line interpretation.