diagnoselisted

# diagnose This skill turns your agent into its own first-line support. Instead of forwarding "something's wrong" messages to a human, the agent inspects the VM, identifies the root cause, and either fixes it or reports a precise diagnosis. ## When to trigger Trigger this skill automatically when: - The user says anything like "something's wrong", "not working", "broken", "help", "can't connect", "error", or "I'm stuck". - Any command or tool returns a non-zero exit code and you don't already know why. - A `StopFailure` or similar hook fires. - An agent you spawned goes silent or returns a `generic` / `timeout` error class. Do **not** trigger the security audit sub-capability automatically — run it only when the user explicitly asks for a security check or audit. ## Standard health check Run these in order. Stop at the first critical failure and attempt a fix before continuing. Report the full picture at the end. ### 1. Auth state ```bash # Check which agent types are authenticated on this host. sudo 5dive doctor --json | jq '.data.checks | map(select(.name | startswith("auth")))' ``` If a type comes back `status: "fail"`, that's why agents of that type can't start. Fix with `auth set` (API key) or guide the user through `auth start` (OAuth): ```bash # API key path — pipe the key, never leave it in the shell history. echo "$KEY" | sudo 5dive agent auth set claude --api-key=- --json ``` ### 2. Recent 5dive-cli errors ```bash # Last 50 error/warning lines from th