workbench-doctor

Workbench Doctor

Run the updater in check mode first. It only reads the installed-plugin registry and runs the Codex gateway health check when that plugin is installed:

node "${CLAUDE_PLUGIN_ROOT}/bin/update-toolshed.js" --check

Then run the same read-only session health audit used at startup:

node -e "const { audit } = require(process.env.CLAUDE_PLUGIN_ROOT + '/hooks/session-start-freshness.js'); const result = audit(); console.log(JSON.stringify({ problems: result.problems, boards: result.mappings }, null, 2));"

Then read the consent/config record and report the managed observability health. This command is read-only and uses the configured ports/container:

node "${CLAUDE_PLUGIN_ROOT}/lib/observability/ensure.js" --health

If it reports configured: false, observability was never consented to and needs no repair. If it reports enabled: false, say it is deliberately disabled. For an enabled record, report observer health, Collector listening state, selected sink, configured ports, and dashboard/Docker state. Treat a listening observer with a failed /health response as unhealthy, and a configured dashboard without Docker as optional/unavailable rather than a pipeline failure.

When the observer is healthy, run the local report too:

node "${CLAUDE_PLUGIN_ROOT}/bin/token-usage-report.js" --format json

From the JSON report, call out outbox queue depth/capacity, drops, schema drops, telemetry conflicts, sessions missing SessionEnd, and the newest event/source. The SessionStart ensure hook repairs stopped managed processes on the next startup/resume; if immediate repair is requested, rerun /init-workspace and keep the current observability choices.

Report all results together. Explain each concrete problem and give the smallest next step. This skill does not update, install, uninstall, reload, or edit anything. If freshness is proven stale, tell the user to run /update-toolshed, then /reload-plugins or restart before retrying the blocked work.