How do I install the Claw Guru skill?

Run npx skillmds@latest add johnalbertini14-glitch/claw-guru in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claw Guru safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claw Guru?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claw Guru free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claw Guru?

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claw Guru by johnalbertini14-glitch

Name: Claw Guru
Rating: 4.2 (5 reviews)
Author: johnalbertini14-glitch

Claw Guru

OpenClaw expert — use for ANY OpenClaw question or problem including: config errors, gateway crashes, gateway not starting, slash commands, channel routing, multi-agent setup, heartbeat, cron jobs, channel setup, Discord/Telegram/Slack/iMessage integration, pairing, auth, nodes, version upgrades, skills, sandboxing, model providers, webhooks, hooks, "openclaw not working", "gateway crashed", "command not found", session issues, memory, browser tool, CLI usage, installation, permissions, tool policy, remote access, and any other OpenClaw topic.

File contents

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

Backup: cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak
Edit the config
Validate JSON: cat ~/.openclaw/openclaw.json | python3 -m json.tool > /dev/null
Restart: openclaw gateway restart
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.

---name: claw-gurudescription: OpenClaw expert — use for ANY OpenClaw question or problem including: config errors, gateway crashes, gateway not starting, slash commands, channel routing, multi-agent setup, heartbeat, cron jobs, channel setup, Discord/Telegram/Slack/iMessage integration, pairing, auth, nodes, version upgrades, skills, sandboxing, model providers, webhooks, hooks, "openclaw not working", "gateway crashed", "command not found", session issues, memory, browser tool, CLI usage, installation, permissions, tool policy, remote access, and any other OpenClaw topic.--- # 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 ```bash 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 ```bash 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.

Frequently asked questions