Openclaw Guru - Documentation and Support expert

OpenClaw expert — use for ANY OpenClaw question or problem including: config errors, gateway crashes, gateway not starting, slash commands, channel routing,...

Security Scan

The skill's instructions, requirements, and behavior are internally consistent with an OpenClaw troubleshooting helper — it reads OpenClaw logs/config and fetches official docs, so it's coherent but will access local files that may contain secrets.

Purpose & Capability

Name/description describe OpenClaw troubleshooting and the SKILL.md exclusively instructs how to diagnose and fix OpenClaw (doctor, gateway status, logs, config lookup, docs, GitHub issues). The requested operations align with that purpose.

Instruction Scope

Instructions tell the agent to run diagnostic commands and read files under ~/.openclaw and global npm install locations and to fetch docs/GitHub pages. These are appropriate for troubleshooting, but they do grant the agent access to local config and logs (which can contain API keys/secrets). The SKILL.md warns not to rely on memory and to verify against live sources, but it does not explicitly limit exfiltration of any sensitive values found.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — nothing is written to disk or downloaded by the skill itself, which is the lowest-risk install profile.

Credentials

The skill requests no environment variables or credentials, which is proportional. However, runtime instructions access user files (e.g., ~/.openclaw/openclaw.json, ~/.openclaw/logs, global npm dist paths). Accessing those files is coherent for the purpose but could expose secrets; the skill does not require unrelated credentials or environment variables.

Persistence & Privilege

always is false, there is no install or persistent agent modification, and the skill does not request elevated or persistent privileges. The agent may run the prescribed commands when invoked, which is expected.

Assessment

This skill appears to do what it says: a troubleshooting script for OpenClaw. Because it instructs reading local OpenClaw config and logs, those files may contain API keys or other secrets. Before installing or allowing autonomous use: 1) confirm you trust the skill source (unknown here), 2) prefer running suggested commands yourself or in a sandbox/container rather than granting blanket autonomous access, 3) avoid pasting sensitive tokens into the agent, and 4) back up configs before edits (the SKILL.md already advises backups). If you want stronger safety, run the diagnostic commands manually and share only the sanitized output the helper needs.

Claw Guru — OpenClaw Live Support

OpenClaw is an AI-agent gateway that connects LLMs to chat channels, tools, and devices. Never rely on memorized config values — always verify against live sources.

Live Sources (fetch at runtime)

Source	URL
Docs home	https://docs.openclaw.ai
Docs index (machine-readable)	https://docs.openclaw.ai/llms.txt
Config reference	https://docs.openclaw.ai/gateway/configuration-reference.md
Gateway troubleshooting	https://docs.openclaw.ai/gateway/troubleshooting.md
General troubleshooting	https://docs.openclaw.ai/help/troubleshooting.md
FAQ	https://docs.openclaw.ai/help/faq.md
Doctor docs	https://docs.openclaw.ai/gateway/doctor.md
GitHub repo	https://github.com/openclaw/openclaw
GitHub Issues	https://github.com/openclaw/openclaw/issues
Releases / changelog	https://github.com/openclaw/openclaw/releases
Community Discord	https://discord.gg/clawd
ClawHub (skills)	https://clawhub.ai

Start with llms.txt to find the right doc page for any topic.

Agent Workflow

1. Gather diagnostics first

openclaw doctor
openclaw gateway status
tail -50 ~/.openclaw/logs/gateway.log

2. Fetch the relevant doc BEFORE giving advice

Search llms.txt for the topic keyword → fetch that doc page → base your answer on it.

3. Check GitHub Issues for the exact error

Search https://github.com/openclaw/openclaw/issues?q=ERROR_STRING for known issues and fixes.

4. Verify config against the installed dist — never from memory

DIST=$(find $(npm root -g)/openclaw/dist ~/.npm*/openclaw/dist 2>/dev/null | head -1)
# Look up any config key:
grep -o 'KEY_NAME.\{0,200\}' "$DIST"/config-*.js | head -10
# Or check the live config reference doc:
# https://docs.openclaw.ai/gateway/configuration-reference.md

5. Safe change protocol

1. Backup: cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak
2. Edit the config
3. Validate JSON: cat ~/.openclaw/openclaw.json | python3 -m json.tool > /dev/null
4. Restart: openclaw gateway restart
5. Check logs: tail -30 ~/.openclaw/logs/gateway.log

Hard Rule

Never give config values, defaults, or field names from memory. Always verify against the local dist schema or the live config reference doc. OpenClaw ships new versions frequently — stale advice breaks things.