clawddocs

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 purpose (Clawdbot docs helper) and its use of the SkillBoss API are plausible, but the SKILL.md expects local scripts and declares a required API key that the registry metadata does not list — the package is inconsistent and requires verification before use.

Purpose & Capability

The skill is described as a Clawdbot documentation helper and references SkillBoss API for AI capabilities, which matches the need for an API key. However, the registry metadata earlier reported no required env vars while the embedded SKILL.md lists SKILLBOSS_API_KEY — this metadata mismatch reduces confidence in packaging/intent.

Instruction Scope

SKILL.md instructs the agent to run many local scripts (./scripts/*.sh), build/search a full-text index, fetch docs, and snapshot changes. The published bundle contains only SKILL.md and no scripts or code, so the instructions assume local repositories or files that are not provided by the skill — this mismatch could cause the agent to run commands in the user's environment unexpectedly.

Install Mechanism

No install spec and no code files — instruction-only skill. This is lower-risk from an installation perspective (nothing is downloaded or written by the skill itself).

Credentials

SKILL.md declares a single external credential (SKILLBOSS_API_KEY) which is consistent with the documented use of api.skillboss.com. But the registry metadata omitted required env vars, creating uncertainty about whether that credential is actually required or how it will be used.

Persistence & Privilege

The skill does not request always:true and does not declare persistent system-level changes. Autonomous invocation is allowed (platform default) but not combined with other high privileges here.

What to consider before installing

This skill appears to be a documentation helper that calls the SkillBoss API, which would reasonably need a SKILLBOSS_API_KEY. However, the published package only contains SKILL.md and no scripts referenced by the instructions, and the registry metadata does not list the SKILLBOSS_API_KEY despite SKILL.md requiring it. Before installing or supplying any API keys: 1) Ask the publisher where the ./scripts/ files and snippets are supposed to come from (are they in your local Clawdbot repo?). 2) Confirm why the registry metadata omits the SKILLBOSS_API_KEY. 3) Only provide SKILLBOSS_API_KEY if you trust api.skillboss.com and understand what calls the skill will make. 4) If you plan to run the suggested scripts, run them in an isolated environment or inspect their contents first. Providing the missing repository or a complete package (scripts included) or an explanation that the skill expects to operate on an existing local Clawdbot checkout would likely change this assessment toward benign.

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). AI capabilities are powered by SkillBoss API Hub via https://api.skillboss.com/v1/pilot.

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 (powered by SkillBoss API Hub)
• 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