From claude-claw
Answers OpenClaw questions on configuration, troubleshooting, setup, architecture, features, channels, gateway, automation, models, and design decisions using clawdocs and openclaw CLIs.
npx claudepluginhub gupsammy/claudest --plugin claude-clawThis skill is limited to using the following tools:
Answer OpenClaw questions, suggest optimal configuration, diagnose issues, and guide design decisions. Two backends: `clawdocs` CLI for documentation, `openclaw` CLI for live state inspection.
Navigates Clawdbot documentation for setup, gateway configuration, provider integration, troubleshooting, automation, and deployment using decision trees and bash scripts.
Guides installation, configuration, troubleshooting, security hardening, and management of OpenClaw AI gateway for 23+ messaging platforms like Slack, Telegram, Discord.
Provides structured reference for OpenClaw platform on plugin system, extensions, configuration, boot/provisioning, channels, models, CLI. Use for building plugins, configuring instances, provisioning gateways, debugging issues.
Share bugs, ideas, or general feedback.
Answer OpenClaw questions, suggest optimal configuration, diagnose issues, and guide design decisions. Two backends: clawdocs CLI for documentation, openclaw CLI for live state inspection.
| Command | Use When |
|---|---|
clawdocs fetch "<topic>" --no-header -q | Topic known, need full page content |
clawdocs search "<query>" --slugs-only | Need to find relevant doc slugs |
clawdocs get <slug> --no-header -q | Exact slug known (e.g., channels/telegram) |
clawdocs list --prefix <section>/ | Need to enumerate a doc section |
| Command | Use When |
|---|---|
openclaw status | Check channel health, recent sessions |
openclaw doctor --non-interactive | Run health checks without prompts |
openclaw config get <dot.path> | Read a specific config value |
openclaw health | Check gateway health |
If openclaw commands fail (not installed, gateway not running), proceed with docs-only advice. Do not treat this as an error.
Parse $ARGUMENTS or the user's conversational question. Classify into:
If ambiguous, ask one clarifying question via AskUserQuestion. Do not over-interview — default to the most likely interpretation.
If the question involves the user's current setup, gather live state:
openclaw status 2>/dev/null
openclaw doctor --non-interactive 2>/dev/null
Load topic routing to identify relevant doc sections:
@${CLAUDE_PLUGIN_ROOT}/skills/claw-advisor/references/topic-routing.md
Proceed when the question is classified and live state (if relevant) is gathered.
Focused — single fetch, possibly one follow-up:
clawdocs fetch "<topic>" --no-header -q
If the result doesn't fully answer the question, search for adjacent docs:
clawdocs search "<refined query>" --slugs-only
Then fetch the best 1-2 additional slugs via clawdocs get.
Broad — identify 2-4 relevant topic areas from topic-routing.md. Spawn parallel subagents, one per area:
Task(subagent_type="general-purpose", prompt="Run `clawdocs fetch <topic> --no-header -q` via Bash and summarize: key config options, requirements, gotchas, and exact CLI commands for: <specific aspect>")
Run up to 4 subagents in parallel. Each returns a focused summary. Reconvene results in Phase 3.
Troubleshooting — always consult three sources:
clawdocs fetch "<domain>" --no-header -qclawdocs get "<domain>/troubleshooting" --no-header -qclawdocs get "help/troubleshooting" --no-header -qCross-reference with openclaw doctor --non-interactive output if available. If doctor reports fixable issues, surface the exact fix command (openclaw doctor --fix).
Design — for each option, fetch the primary doc page and any comparison or overview page (e.g., providers/index). Identify: requirements, limitations, and config complexity. Stop when each option has enough data to compare on the same dimensions.
If official docs don't cover the issue, use WebSearch for community solutions or GitHub issues as a fallback.
Proceed when all relevant docs are fetched and summarized.
Combine all research into a structured response:
openclaw config get/set), values, and CLI commands. Use code blocks.clawdocs get <slug>If docs and live state conflict, note the discrepancy and recommend openclaw <cmd> --help as ground truth.
Skill is complete when the structured response is delivered.
--no-header -q on all clawdocs calls to suppress chrome and stderr diagnosticsopenclaw config get/set