| name | muggle-status |
| model | haiku |
| description | Check the health of the user's Muggle AI installation and diagnose why it's misbehaving — MCP server connectivity, tool loading, login/auth validity, overall setup. Engage on muggle status and on any diagnostic question about Muggle itself: is muggle working or healthy, why does muggle keep failing or timing out, are the muggle MCP tools loading, is my muggle login still valid. Prefer this over answering from memory whenever the user is unsure Muggle itself is functioning. Boundary: diagnosing is muggle-status; fixing a broken install is muggle-repair. Not for the health of the user's own app, CI, or infra. |
Muggle Test Status
Telemetry first step: see _shared/telemetry-emit.md. Use skillName: "muggle-status".
Run a full health check and report results.
Preferences
Gates run per preference-gates/README.md.
| Preference | Step | Decision it gates |
|---|
checkForUpdates | Check 4 | Check for newer Muggle Test version |
Checks
-
Electron app — read ~/.muggle-ai/electron-app/ to find the installed version directory. Read .install-metadata.json to get version and checksum. Verify the binary exists at the expected path. On macOS, check code signing with spctl --assess --verbose.
-
MCP server — call muggle-local-check-status to verify the server is responsive. Report auth state (authenticated, email, token expiry).
-
Authentication — call muggle-remote-auth-status. Report whether credentials are valid and when they expire.
-
CLI version — gate checkForUpdates (per preference-gates/README.md):
always → run the check below.never → render the row as [skip] check disabled by preference.ask → run Picker 1 from preference-gates/checkForUpdates.md via AskUserQuestion; map the answer back to one of the actions above.
When the check runs: capture installed (muggle --version) and latest (npm view @muggleai/works version). Compare with sort -V; flag as out-of-date only when latest is strictly greater.
Output
Muggle AI — Status
Electron app [pass/fail] version, binary status
MCP server [pass/fail] responsive, auth state
Authentication [pass/fail] user, expiry
CLI version [pass/warn] installed → latest
[All systems operational / Issues found — run /muggle:muggle-repair to fix.]
Use pass/fail indicators for each check. If any check fails, tell the user to run /muggle:muggle-repair. If the CLI version check warns (installed < latest), tell the user to run /muggle:muggle-upgrade.
