clawddocs — Claude Code skill for OpenClaw docs
Find OpenClaw guidance, configuration examples, and recently changed docs with clawddocs. Use it while setting up a provider, troubleshooting, or deploying OpenClaw.
MIT ★ 239 updated 2026-08-30
npx skills add jdrhyne/agent-skills --skill clawddocs -a claude-codeWhat clawddocs does
clawddocs routes OpenClaw questions to relevant documentation areas, from provider setup and gateway configuration to troubleshooting and deployment. Its scripts search by keyword, fetch individual pages, and list recent changes. Configuration examples are available in snippets/common-configs.md.
The skill can also save documentation snapshots and show changes since a chosen date. Full-text indexing and semantic search rely on qmd, so those commands won’t work without it. For a Discord setup question, the skill can locate the provider guide and surface the requireMention setting.
What it helps with
- find setup instructions for an OpenClaw provider
- locate troubleshooting guidance for a failing feature
- get an OpenClaw gateway configuration example
- see which documentation pages changed recently
- compare saved documentation snapshots
Example prompts for the agent
- Show me how to make my OpenClaw Discord bot respond only when mentioned.
- Find the OpenClaw gateway configuration guide and suggest a relevant example.
- Which OpenClaw documentation pages changed since 2026-01-01?
How to install clawddocs
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill clawddocs -a claude-code2Manually: put the files in place
~/.claude/skills/clawddocs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/clawddocs/
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill clawddocs -a codex2Manually: put the files in place
.agents/skills/clawddocs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill clawddocs -a cursor2Manually: put the files in place
.cursor/skills/clawddocs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jdrhyne/agent-skills clawdbot/clawddocs/SKILL.md2Manually: put the files in place
.github/skills/clawddocs/SKILL.md1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill clawddocs -a gemini-cli2Platform CLI
gemini skills install https://github.com/jdrhyne/agent-skills --path clawdbot/clawddocsManually: put the files in place
.devin/skills/clawddocs/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about clawddocs
How do I install clawddocs in Claude Code?
Run npx skills add jdrhyne/agent-skills --skill clawddocs -a claude-code. The skill file is at ~/.claude/skills/clawddocs/SKILL.md.
What does clawddocs do?
It helps Claude Code find and explain OpenClaw documentation, including setup guides and configuration examples. It can also report recent page changes and save snapshots.
Does clawddocs need qmd?
Full-text indexing and semantic search use qmd. Keyword search and fetching an individual page are handled by separate scripts.
Source text
SKILL.md · MIT
---
name: clawddocs
description: OpenClaw documentation expert with decision tree navigation, search scripts, doc fetching, version tracking, and config snippets for all OpenClaw features
---
# OpenClaw Documentation Expert
**Capability Summary:** OpenClaw documentation expert skill with decision tree navigation, search scripts (sitemap, keyword, full-text index via qmd), doc fetching, version tracking, and config snippets for all OpenClaw features (providers, gateway, automation, platforms, tools).
You are an expert on OpenClaw documentation. Use this skill to help users navigate, understand, and configure OpenClaw.
## Quick Start
"When a user asks about OpenClaw, first identify what they need:"
### 🎯 Decision Tree
- **"How do I set up X?"** → Check `providers/` or `start/`
- Discord, Telegram, WhatsApp, etc. → `providers/<name>`
- First time? → `start/getting-started`, `start/setup`
- **"Why isn't X working?"** → Check troubleshooting
- General issues → `debugging`, `gateway/troubleshooting`
- Provider-specific → `providers/troubleshooting`
- Browser tool → `tools/browser-linux-troubleshooting`
- **"How do I configure X?"** → Check `gateway/` or `concepts/`
- Main config → `gateway/configuration`, `gateway/configuration-examples`
- Specific features → relevant `concepts/` page
- **"What is X?"** → Check `concepts/`
- Architecture, sessions, queues, models, etc.
- **"How do I automate X?"** → Check `automation/`
- Scheduled tasks → `automation/cron-jobs`
- Webhooks → `automation/webhook`
- Gmail → `automation/gmail-pubsub`
- **"How do I install/deploy?"** → Check `install/` or `platforms/`
- Docker → `install/docker`
- Linux server → `platforms/linux`
- macOS app → `platforms/macos`
## Available Scripts
All scripts are in `./scripts/`:
### Core
```bash
./scripts/sitemap.sh # Show all docs by category
./scripts/cache.sh status # Check cache status
./scripts/cache.sh refresh # Force refresh sitemap
```
### Search & Discovery
```bash
./scripts/search.sh discord # Find docs by keyword
./scripts/recent.sh 7 # Docs updated in last N days
./scripts/fetch-doc.sh gateway/configuration # Get specific doc
```
### Full-Text Index (requires qmd)
```bash
./scripts/build-index.sh fetch # Download all docs
./scripts/build-index.sh build # Build search index
./scripts/build-index.sh search "webhook retry" # Semantic search
```
### Version Tracking
```bash
./scripts/track-changes.sh snapshot # Save current state
./scripts/track-changes.sh list # Show snapshots
./scripts/track-changes.sh since 2026-01-01 # Show changes
```
## Documentation Categories
### 🚀 Getting Started (`/start/`)
First-time setup, onboarding, FAQ, wizard
### 🔧 Gateway & Operations (`/gateway/`)
Configuration, security, health, logging, tailscale, troubleshooting
### 💬 Providers (`/providers/`)
Discord, Telegram, WhatsApp, Slack, Signal, iMessage, MS Teams
### 🧠 Core Concepts (`/concepts/`)
Agent, sessions, messages, models, queues, streaming, system-prompt
### 🛠️ Tools (`/tools/`)
Bash, browser, skills, reactions, subagents, thinking
### ⚡ Automation (`/automation/`)
Cron jobs, webhooks, polling, Gmail pub/sub
### 💻 CLI (`/cli/`)
Gateway, message, sandbox, update commands
### 📱 Platforms (`/platforms/`)
macOS, Linux, Windows, iOS, Android, Hetzner
### 📡 Nodes (`/nodes/`)
Camera, audio, images, location, voice
### 🌐 Web (`/web/`)
Webchat, dashboard, control UI
### 📦 Install (`/install/`)
Docker, Ansible, Bun, Nix, updating
### 📚 Reference (`/reference/`)
Templates, RPC, device models
## Config Snippets
See `./snippets/common-configs.md` for ready-to-use configuration patterns:
- Provider setup (Discord, Telegram, WhatsApp, etc.)
- Gateway configuration
- Agent defaults
- Retry settings
- Cron jobs
- Skills configuration
## Workflow
1. **Identify the need** using the decision tree above
2. **Search** "if unsure: `./scripts/search.sh <keyword>`"
3. **Fetch the doc**: `./scripts/fetch-doc.sh <path>` or use browser
4. **Reference snippets** for config examples
5. **Cite the source URL** when answering
## Tips
- Always use cached sitemap when possible (1-hour TTL)
- For complex questions, search the full-text index
- Check `recent.sh` to see what's been updated
- Offer specific config snippets from `snippets/`
- Link to docs: `https://docs.openclaw.ai/<path>`
## Example Interactions
**User:** "How do I make my bot only respond when mentioned in Discord?"
**You:**
1. Fetch `providers/discord` doc
2. Find the `requireMention` setting
3. Provide the config snippet:
```json
{
"discord": {
"guilds": {
"*": {
"requireMention": true
}
}
}
}
```
4. Link: https://docs.openclaw.ai/providers/discord
**User:** "What's new in the docs?"
**You:**
1. Run `./scripts/recent.sh 7`
2. Summarize recently updated pages
3. Offer to dive into any specific updates
© jdrhyne · MIT · jdrhyne/agent-skills