skill-doctor

# Environment Doctor ## Overview Run environment diagnostics across 14 check categories. Doctor 2.0 identifies misconfigured providers, stale loaded or cached plugin versions, invalid plugin assembly, unwritable state, non-terminal run records, orphan process evidence, broken hooks, and other issues that prevent Claude Octopus from working correctly. **Core principle:** Detect problems before they surface in workflows. --- ## When to Use **Use this skill when:** - Something isn't working and you're not sure why - After installing or updating the plugin - Before a demo or important workflow run - Checking if providers are properly authenticated - Verifying scheduler, hooks, or skills are correctly configured **Do NOT use for:** - First-time setup (use `/octo:setup` — it guides configuration) - Project workflow status (use `/octo:status`) - Debugging application code (use `/octo:debug`) --- ## The Process ### Step 1: Resolve Plugin Root and Run Full Diagnostics Use this resolver before running Octopus scripts. Do not assume `~/.claude-octopus/plugin` exists; Windows Git Bash installs may not support the stable symlink. Run this as a single Bash call. ```bash OCTO_PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-}" if [[ -z "$OCTO_PLUGIN_ROOT" || ! -x "$OCTO_PLUGIN_ROOT/scripts/orchestrate.sh" ]]; then OCTO_PLUGIN_ROOT="${HOME}/.claude-octopus/plugin" fi if [[ ! -x "$OCTO_PLUGIN_ROOT/scripts/orchestrate.sh" ]] && command -v octopus >/dev/null 2>&1; then OCTO_BIN="$(command -v ...