/nio-doctor — validate config + connectivity.

Invoke: /nio-doctor (Claude Code) · $nio-doctor or natural language (Codex) · or via the umbrella /nio doctor on any platform (incl. OpenClaw / Hermes). See Focused skills.

doctor

Validate the current configuration end-to-end. Doctor catches issues before they cause silent failures during real tool calls. No arguments.

What doctor does:

1. Configuration — re-runs Zod schema validation against the on-disk ~/.nio/config.yaml.
2. External analysers — for every enabled entry, builds the same ExternalAnalyser the orchestrator uses (auth strategy, custom headers) and issues a real GET against the configured URL. On success, prints the parsed score; on failure, prints HTTP status / response body preview / hint. This catches typos, missing query params, auth failures, AND response-contract violations like the endpoint returning a different shape.
3. LLM analyser — flags guard.llm_analyser.enabled=true paired with an empty api_key.

Doctor does not probe collector.endpoint reachability — its config correctness is covered by the schema check above, and bare HTTP probes would skip the routing headers (e.g. x-event-pipeline-id) that gateways often require, producing misleading 401/403 reports. Export failures surface at runtime via collector / otlp_export_failed.

Output is a markdown checklist with ✓ / ✗ / · per check and an inline hint: line pointing at the specific config path to fix. Doctor's own probes use a scoped diagnostic collector that's discarded after the command returns, so repeated doctor runs do not pollute /nio report.

See the Diagnostics page for a full example output and a walkthrough.