⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
clawdoc-onboarding
Guided first-run setup for ClawDoc (the docs/skills themselves), NOT for OpenClaw runtime first-run (use openclaw-start for that). Walks through installing ClawDoc skills, configuring docs sync, and end-to-end verification of the ClawDoc layer. Triggers on: \"ClawDoc first run\", \"ClawDoc setup\", \"install ClawDoc\", \"ClawDoc getting started\", \"set up ClawDoc skills\", \"ClawDoc install verification\".
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
ClawDoc
The OpenClaw knowledge-base agent for config audits, troubleshooting, and grounded system fixes.
🧠 Same idea, different agent: HermitDoc — the ClawDoc philosophy applied to Hermes Agent
Contents
- What is ClawDoc?
- Which install mode?
- Who is this for?
- Install
- Use it
- Reference docs
- Skill tree
- Ready-to-use examples
- Community
- For contributors
- Operating principles
What is ClawDoc?
ClawDoc is a specialized OpenClaw agent that knows the entire OpenClaw system inside and out. It handles configuration auditing, plugin integration, troubleshooting, memory setup, multi-agent design, and channel configuration — with precision, not guesswork.
[!NOTE] ClawDoc is a community project. It is not affiliated with or endorsed by OpenClaw.
[!TIP] Every answer is grounded in the actual OpenClaw schema and docs. Before/after diffs, exact config patches, and real command references — always.
Which install mode?
ClawDoc supports two adoption paths. Pick the one that fits your setup:
| Mode 1 — Persistent Agent | Mode 2 — Skills Only | |
|---|---|---|
| What it does | Creates a dedicated ClawDoc agent with its own workspace | Adds ClawDoc skills to your existing agent |
| Best for | Serious ongoing maintenance, system doctor use | Quick OpenClaw help in an existing agent |
| New agent created? | ✅ Yes | ❌ No |
| Separate identity? | ✅ Yes | ❌ Your agent keeps its identity |
| Guide | AGENT_INSTALL.md | SKILLS_INSTALL.md |
Who is this for?
ClawDoc is for OpenClaw operators who need reliable help with:
- setting up channels and providers
- debugging config and runtime issues
- adding memory, tools, plugins, and agents
- generating safe config patches instead of guessing
Scope
ClawDoc is for OpenClaw only. It will help with — and only with — OpenClaw configuration, troubleshooting, plugin integration, memory setup, and agent design.
What ClawDoc will not do:
- Help with non-OpenClaw frameworks (LangChain, AutoGen, CrewAI, etc.) — it will redirect you back to OpenClaw
- Build custom plugins from scratch unless you explicitly ask
- Execute destructive commands (
rm -rf, mass git push, gateway reset) without your explicit confirmation - Hold credentials or secrets in conversation state
If you ask about something outside OpenClaw, ClawDoc will say so rather than guess.
How ClawDoc routes requests
flowchart TD
Q[Operator question] --> R{openclaw-master<br/>routes by area}
R -->|config| SC[openclaw-config]
R -->|memory| SM[openclaw-memory]
R -->|channels| SCh[openclaw-channels]
R -->|agents| SA[openclaw-agents]
R -->|plugins| SP[openclaw-plugins]
R -->|troubleshoot| ST[openclaw-troubleshooting]
R -->|CLI| SCli[openclaw-cli]
R -->|providers| SPr[openclaw-providers]
R -->|install| SIns[openclaw-install]
SC --> Ref[references/<br/>ground truth]
SM --> Ref
SCh --> Ref
SA --> Ref
SP --> Ref
ST --> Ref
SCli --> Ref
SPr --> Ref
SIns --> Ref
Ref --> A[Cited answer<br/>+ before/after diff]
Install
AI-agent install (recommended):
"Install ClawDoc from https://github.com/Hashi-Ai-Dev/openclaw-clawdoc"
Your agent reads the repo, picks up all 24 skills, and is ready to help. That's it.
Manual install — choose your mode:
- AGENT_INSTALL.md — Mode 1: persistent dedicated ClawDoc agent
- SKILLS_INSTALL.md — Mode 2: add ClawDoc skills to an existing agent
Need help getting started? → QUICKSTART.md (10 min)
Use it
@your-agent [any OpenClaw config question]
ClawDoc routes to the right skill, reads the reference docs, and gives you a precise, grounded answer.
Reference docs
640 docs copied from the official OpenClaw source and versioned against the tracked OpenClaw release.
| Area | What's covered |
|---|---|
| Config | All gateway config keys, defaults, secrets, retry, failover |
| Memory | builtin / QMD / Honcho setup, embeddings, citations |
| Agents | Multi-agent, bindings, sandbox, tool policies |
| Channels | Discord, Telegram, WhatsApp, Slack, Signal, and 40+ more (45 active channels total) |
| Concepts | Architecture, session, compaction, streaming, queue |
| Providers | 60+ model providers: OpenAI, Anthropic, Gemini, Bedrock, Ollama... |
| CLI | Every openclaw command with examples |
| Troubleshooting | Error codes, diagnostic flows, common fixes |
Skill tree
Core
| Skill | What it does |
|---|---|
openclaw-master | Top-level routing — maps your question to the right skill |
openclaw-config | Gateway config reference — all keys, all patterns |
openclaw-memory | Memory backends: builtin, QMD, Honcho |
openclaw-agents | Multi-agent, bindings, sandbox, tool policies |
openclaw-channels | Discord, Telegram, WhatsApp, Slack, Signal — and 40+ more (45 active channels total) |
Operations
| Skill | What it does |
|---|---|
openclaw-troubleshooting | Diagnosis flows, error codes, common fixes |
openclaw-automation | Cron, hooks, tasks, Task Flow |
openclaw-logging | Logging configuration and management |
openclaw-gateway | Gateway HTTP API, telemetry, secrets, sandbox, runbooks |
Channels & Platforms
| Skill | What it does |
|---|---|
openclaw-nodes | Mobile/desktop node pairing and device management |
openclaw-platforms | Docker, Railway, Fly, Raspberry Pi, DigitalOcean... |
openclaw-install | Install guides for all platforms |
openclaw-start | First-run wizard and onboarding |
clawdoc-onboarding | Guided setup for new ClawDoc users |
Tools & Providers
| Skill | What it does |
|---|---|
openclaw-tools | exec, browser, cron, sessions, subagents, ACP |
openclaw-clawhub | ClawHub registry: discover, install, publish, verify skills and plugins |
openclaw-providers | Model providers: 60+ individual files: OpenAI, Anthropic, Gemini, Bedrock, Ollama, DeepSeek, Groq, Together, Cohere... |
openclaw-cli | All openclaw CLI commands |
openclaw-web | Web UI, dashboard, TUI, webchat |
openclaw-prose | OpenProse: markdown-first multi-agent workflow language (/prose, .prose files) |
Concepts & Help
| Skill | What it does |
|---|
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/clawdoc-onboarding/SKILL.md3.5 KBupstream ↗
--- name: clawdoc-onboarding description: "Guided first-run setup for ClawDoc (the docs/skills themselves), NOT for OpenClaw runtime first-run (use openclaw-start for that). Walks through installing ClawDoc skills, configuring docs sync, and end-to-end verification of the ClawDoc layer. Triggers on: \"ClawDoc first run\", \"ClawDoc setup\", \"install ClawDoc\", \"ClawDoc getting started\", \"set up ClawDoc skills\", \"ClawDoc install verification\"." --- ## Routing hints You should route to this skill when the user is installing ClawDoc for the first time, wants a guided walkthrough of the dual install modes, or needs help verifying their install completed successfully. References: `README.md` (the full setup walkthrough). # ClawDoc Onboarding Walk a new ClawDoc user through their first successful setup in under 15 minutes. ## What it checks 1. **OpenClaw installed** — binary reachable, gateway can start 2. **Model configured** — primary model set + auth configured 3. **First channel connected** — Discord, Telegram, or other 4. **Verification** — agent responds to first message ## Step-by-step ### Step 1 — Verify OpenClaw install ```bash openclaw --version openclaw gateway status ``` If gateway won't start → troubleshoot install first. ### Step 2 — Configure model Prompt user to pick a provider: | Provider | Effort | Best for | |----------|--------|----------| | MiniMax | Low — free tier | New users, fast setup | | OpenAI | Medium — needs API key | Advanced users | | Gemini | Medium — needs API key | Advanced users | | Ollama | High — local setup | Self-hosted enthusiasts | For MiniMax (recommended): ```bash openclaw config set agents.defaults.model.primary "minimax/MiniMax-M2.7" openclaw config set auth.profiles.minimax.provider "minimax" ``` ### Step 3 — Connect first channel **Discord (most common):** ```bash openclaw config set channels.discord.token "YOUR_BOT_TOKEN" openclaw config set channels.discord.enabled true openclaw gateway restart ``` Verify DM policy and pairing: ```bash openclaw pairing approve discord <CODE> ``` **Telegram:** ```bash openclaw config set channels.telegram.token "YOUR_BOT_TOKEN" openclaw config set channels.telegram.enabled true ``` ### Step 4 — Install ClawDoc skills ```bash # Via clawdhub (recommended) clawdhub install https://github.com/Hashi-Ai-Dev/openclaw-clawdoc # Or manual clone git clone https://github.com/Hashi-Ai-Dev/openclaw-clawdoc.git ~/.openclaw/skills/openclaw ``` ### Step 5 — End-to-end verification Ask user to send a test message: ``` @your-agent "Hello, are you working?" ``` Expected: agent responds within 10 seconds. ## Common first-run failures | Symptom | Fix | |---------|-----| | "command not found" | OpenClaw not in PATH — check install location | | "invalid config" | `openclaw doctor --fix` to auto-repair | | Discord bot silent | Verify Message Content Intent enabled in Discord Developer Portal | | Model auth failing | Check API key format, account credits | | Gateway won't start | Port 18789 already in use — `openclaw gateway restart` | ## Output ``` ## Onboarding Checklist — [date] ### Install - [ ] openclaw --version succeeds - [ ] Gateway can start ### Model - [ ] Primary model set - [ ] Auth configured ### Channel - [ ] First channel connected - [ ] Bot responds to DMs ### ClawDoc - [ ] Skills installed - [ ] Agent responds correctly ### Verification - [ ] First test message succeeded ``` ## References - `references/first-run-guide.md` — detailed first-run stepsREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/hashi-ai-dev-openclaw-clawdoc-skills-clawdoc-onboarding.md