Clawdbot Documentation Expert

Clawdbot documentation expert with decision tree navigation, search scripts, doc fetching, version tracking, and config snippets for all Clawdbot features

Security Scan

The skill's requirements and runtime instructions line up with a documentation/navigation helper for Clawdbot; it does not request unexpected credentials or installs, but it does include runnable scripts that will access network and disk so review before use.

Purpose & Capability

Name/description, SKILL.md, snippets, and the included scripts all focus on discovering, fetching, indexing, and surfacing Clawdbot docs; the requested capabilities (sitemap, search, fetch, track-changes) are coherent with the stated purpose.

Instruction Scope

Runtime instructions direct the agent to run the provided scripts and to fetch docs from docs.clawd.bot; they do not ask the agent to read unrelated system files or request unrelated secrets. The scope stays within documentation navigation and retrieval.

Install Mechanism

There is no install spec (instruction-only), which minimizes install risk. The skill does reference external tooling (qmd) for full-text indexing, but it does not itself download arbitrary archives or run an installer.

Credentials

The skill declares no required environment variables, credentials, or config paths. This is proportionate to its documented function. Note: the scripts will perform network fetches and may write snapshots to disk (track-changes), but they do not request secrets in the metadata.

Persistence & Privilege

The skill is not marked always:true and requests no special privileges. Model invocation is not disabled (default allows the model to call the skill autonomously), which is typical for helper skills but worth noting if you want explicit user confirmation before running scripts.

Assessment

This skill appears to be a coherent documentation helper for Clawdbot and doesn't ask for keys or installs. However, it includes small shell scripts that will fetch docs from the network and create local snapshots/indexes. Before installing or enabling the skill: 1) Inspect the contents of the scripts (build-index.sh, fetch-doc.sh, track-changes.sh, etc.) to confirm they only access docs.clawd.bot and do not exfiltrate local files. 2) Run the scripts in a sandbox or with network controls if you are concerned about network writes. 3) Check package.json for any unexpected dependencies. 4) If you prefer to prevent autonomous actions, disable model invocation for this skill or require explicit user consent before the agent runs any scripts.

Capability Summary: Clawdbot 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 Clawdbot features (providers, gateway, automation, platforms, tools).

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

./scripts/sitemap.sh # Show all docs by category
./scripts/cache.sh status # Check cache status
./scripts/cache.sh refresh # Force refresh sitemap

Search & Discovery

./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)

./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

./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:

{
  "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 updates