Best use case
clawdbot-documentation-expert is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using clawdbot-documentation-expert should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clawdbot-documentation-expert/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clawdbot-documentation-expert Compares
| Feature / Agent | clawdbot-documentation-expert | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Clawdbot Documentation Expert
You are an expert on Clawdbot documentation. Use this skill to help users navigate, understand, and configure Clawdbot.
## Quick Start
When a user asks about Clawdbot, 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.clawd.bot/<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.clawd.bot/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 updatesRelated Skills
email-management-expert
Expert email management assistant for Apple Mail. Use this when the user mentions inbox management, email organization, email triage, inbox zero, organizing emails, managing mail folders, email productivity, checking emails, or email workflow optimization. Provides intelligent workflows and best practices for efficient email handling.
clawdbot-workspace-template-review
Compare a Clawdbot workspace against the official templates installed with Clawdbot (npm or source) and list missing sections to pull in, especially after upgrades.
clawdbot-skill-update
Comprehensive backup, update, and restore workflow with dynamic workspace detection
clawdbot-self-security-audit
Perform a comprehensive read-only security audit of Clawdbot's own configuration. This is a knowledge-based skill that teaches Clawdbot to identify hardening opportunities across the system. Use when user asks to "run security check", "audit clawdbot", "check security hardening", or "what vulnerabilities does my Clawdbot have". This skill uses Clawdbot's internal capabilities and file system access to inspect configuration, detect misconfigurations, and recommend remediations. It is designed to be extensible - new checks can be added by updating this skill's knowledge.
clawdbot-security
Security audit and hardening for Clawdbot/Moltbot installations. Detects exposed gateways, fixes permissions, enables authentication, and guides firewall/Tailscale setup.
clawdbot-release-check
Check for new clawdbot releases and notify once per new version.
clawdbot-logs
Analyze Clawdbot logs and diagnostics. Use when the user asks about bot performance, response times, errors, session stats, token usage, API costs, or wants to debug slow responses.
clawdbot-cost-tracker
Track Clawdbot AI model usage and estimate costs. Use when reporting daily/weekly costs, analyzing token usage across sessions, or monitoring AI spending. Supports Claude (opus/sonnet), GPT, and Codex models.
clawdbot-backup
Backup and restore ClawdBot configuration, skills, commands, and settings. Sync across devices, version control with git, automate backups, and migrate to new machines.
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names