Clawddocs 1

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 files, scripts, and runtime instructions match its stated purpose as a documentation helper; nothing requests unrelated credentials or installs unexpected components.

Purpose & Capability

Name/description describe a documentation/navigation helper and the bundle contains sitemap/search/fetch/track scripts and config snippets that align with that purpose. No unrelated binaries, credentials, or config paths are required.

Instruction Scope

SKILL.md instructs the agent to run the included scripts and to cite docs.clawd.bot. The scripts are simple stubs that only echo actions. One minor inconsistency: the full-text index section states 'requires qmd' but the skill does not declare qmd as a required binary; if the real build-index implementation is present upstream it would need that dependency.

Install Mechanism

No install spec is provided (instruction-only). The repository contains small shell scripts and a markdown snippet file; nothing is downloaded or installed by the skill itself.

Credentials

The skill declares no required environment variables, which is appropriate. The included config snippets show placeholders like ${DISCORD_TOKEN} and ${TELEGRAM_TOKEN} — these are example placeholders for user configs, not secrets requested by the skill. Still, the skill does not explicitly document external binaries (qmd) mentioned in the instructions.

Persistence & Privilege

always is false and the skill does not request persistent system privileges or modify other skills. Autonomous invocation is allowed (platform default) but is not combined with broad credentials or other risky behavior here.

Assessment

This skill appears coherent and matches its documentation-help purpose. Before installing, 1) verify the skill source (no homepage is provided), 2) inspect the scripts yourself — they are simple echo stubs here but real versions might perform network calls to docs.clawd.bot or require the 'qmd' tool, 3) understand that config snippets contain placeholders (e.g., ${DISCORD_TOKEN}) — those are examples, not requests from the skill, and 4) if you plan to run build-index or other non-stubbed scripts, confirm any required binaries and inspect network behavior and credential usage first.

Clawdbot Documentation Expert

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