Setup Doctor

Diagnose OpenClaw setup in one command. Auto-detects issues with Node, npm, gateway, config, and workspace. Quick mode (~10s) or Full mode. Multi-language. C...

Security Scan

The skill's requirements, instructions, and included script are consistent with a local OpenClaw diagnostic tool; no unexplained network access, credentials, or unusual install mechanics were requested.

Purpose & Capability

The skill claims to diagnose OpenClaw/node/npm/gateway and its filesystems checks align with that purpose. It requests no credentials, no config paths, and includes a small local diagnostic script that inspects typical OpenClaw locations under the user's home directory — all proportional to a setup-diagnostic tool.

Instruction Scope

SKILL.md instructs the agent to run quick-check shell commands (node --version, npm --version, openclaw gateway status) via the agent's exec facility — this is expected for a diagnostic skill but means the agent will execute external binaries. The SKILL.md repeatedly states it will not read file contents; the included script only checks existence/access and does not read file contents. Minor mismatch: SKILL.md's Workspace Audit claims to report file sizes for specific files, but the included diagnose.js does not enumerate per-file sizes — an implementation gap rather than malicious behavior. Also: auto-detection triggers may cause the agent to run quick checks when users report problems; this is reasonable but the user should be aware of automatic invocation.

Install Mechanism

This is instruction-only (no install spec). A small local script is included but there is no download/install mechanism that would fetch remote code. Low install risk.

Credentials

The skill declares no required environment variables or secrets and the code accesses only local filesystem and process metadata (home directory, process.execPath, etc.). That access is proportionate to discovering host-side OpenClaw/Node/npm configuration. There are no network calls or child_process usage in the script.

Persistence & Privilege

always:false and no install actions that modify other skills or global agent config. The skill can be invoked autonomously per platform defaults; combined with its limited local-checks scope this is not excessive. Fix mode promises explicit confirmation before changes — users should confirm that in practice.

Assessment

This skill appears to do what it says: local checks for Node/npm/OpenClaw and filesystem presence. Things to consider before installing: 1) The agent will run shell commands (node/npm/openclaw) to perform quick checks — ensure you trust running those binaries in your environment. 2) Auto-detection rules can cause the agent to run the quick check when you mention errors; if you prefer manual control, avoid enabling automatic invocation or confirm prompts. 3) The included script is local and does not perform network calls or read file contents, but there are small implementation bugs (e.g., minor path-handling issues) — expect possible noisy warnings rather than silent malicious behavior. 4) Always review and explicitly approve any “fix it” action the skill proposes before allowing it to execute changes.

Setup Doctor v3.0

Install: clawhub install setup-doctor

Diagnose OpenClaw setup issues. Like brew doctor — one command, clear results.

Language

Detect from user's message language. Default: English.

Auto-Detection

Run automatically when:

• User mentions setup issues, errors, or "doesn't work"
• Gateway fails to start or connect
• A command returns an unexpected error
• User says "doctor check", "diagnose", "hvorfor fungerer ikke"

Quick Check (default, ~10s)

node --version
npm --version
openclaw gateway status 2>&1

Report:

Setup Doctor — Quick Check
  Node.js:    ✅ v24.11.1
  npm:        ✅ 10.9.2
  Gateway:    ✅ Running (up 4h)

Issues: none

If issues found, include one-line fix:

  Gateway:    ❌ Not running → Fix: openclaw gateway start

Full Check (opt-in)

Trigger: "doctor full", "full diagnose"

Includes Quick Check PLUS:

• Config: File exists
• Workspace: Directory exists, key files present (SOUL.md, AGENTS.md, etc.)
• Platform: Windows (long paths, PowerShell policy), macOS (Homebrew PATH), Linux (systemd)
• Common pitfalls: Known version conflicts, deprecated patterns

Fix Mode

Trigger: "fix it", "fix det"

1. Show exactly what will change
2. Get user confirmation
3. Apply fix
4. Re-run check to verify

Never fix without confirmation.

Workspace Audit

Trigger: "workspace audit"

Report file existence and size only — never read contents:

Workspace Audit:
  SOUL.md      ✅ 1.2 KB
  AGENTS.md    ✅ 2.8 KB
  MEMORY.md    ✅ 3.1 KB
  HEARTBEAT.md ✅ 0.4 KB
  TOOLS.md     ✅ 0.3 KB

Quick Commands

User says	Action
"doctor check" / "kjor doctor"	Quick Check
"doctor full"	Full Check
"fix it"	Auto-fix with confirmation
"workspace audit"	File existence check

HEARTBEAT Integration

User can add to HEARTBEAT.md:

## Setup Check
- If gateway errors detected: run doctor quick check

Guidelines for Agent

1. Auto-detect issues — run quick check when user reports problems
2. Keep it fast — quick check in ~10 seconds
3. One-line fixes — clear, copy-pasteable solutions
4. Never read file contents — existence and size only
5. Never fix without asking — show what changes, get confirmation
6. Match user language in reports

What This Skill Does NOT Do

• Does NOT read file contents (existence/size only)
• Does NOT access credentials without explicit approval
• Does NOT modify config automatically
• Does NOT modify HEARTBEAT.md or MEMORY.md

More by TommoT2

• context-brief — Persistent context survival across sessions
• tommo-skill-guard — Security scanner for installed skills
• locale-dates — Format dates/times per locale

Install the full suite:

clawhub install setup-doctor context-brief tommo-skill-guard locale-dates