メニュー
Use when the user asks about OpenClaw documentation sources, how to access crawled docs, where to find official documentation, how the documentation sync system works, or when referencing OpenClaw product docs for any task.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit one or more OpenClaw agents, analyse what they require (complexity, tool use, context window, volume, autonomy, sensitivity), and recommend the best-fit OpenRouter models by pricing tier with ready-to-paste openclaw.json config snippets. Use when the user says "what model should I use", "recommend a model for my agent", "audit my agent models", "find a cheaper model", "openrouter model suggestions", "which model fits my agent", or invokes /openclaw-model-advisor.
Create, optimize, and maintain OpenClaw agent workspace files — SOUL.md, IDENTITY.md, AGENTS.md, MEMORY.md, and GOALS.md. Use this skill whenever the user mentions OpenClaw agent setup, agent personality, agent identity, agent workspace files, SOUL.md, IDENTITY.md, AGENTS.md, MEMORY.md, GOALS.md, agent persona, "set up my agent", "configure my agent", "make my agent", or wants to scan/optimize/audit an existing OpenClaw workspace. Also trigger when the user wants to create a new agent from scratch, refine an agent's personality, add goals or memory structure, or review workspace files for consistency. This skill conducts targeted interviews, generates production-ready markdown files, and can scan existing workspaces to optimize them.
Diagnose and fix OpenClaw agent and gateway problems — heartbeats not firing, cron jobs failing, agents not responding, wrong routing, model errors, workspace issues, channel connection failures, and openclaw.json config errors. Use this skill when the user reports: agent not responding, heartbeat stopped, cron job not running, wrong agent getting messages, model errors, gateway won't start, channel disconnected, agent sending to wrong place, memory not writing, session errors, openclaw doctor errors, or any "something isn't working" situation with OpenClaw. This skill reads the openclaw.json config, interprets error patterns, walks through diagnostic steps, identifies the root cause, and produces the exact commands or file changes needed to fix it.
Brainstorm, design, and document OpenClaw agents and multi-agent teams. Use this skill whenever the user wants to plan what agents to build, figure out what agents they need, design agent capabilities and permissions, plan a multi-agent architecture, decide how agents should work together, or create documentation for their agent team. Also trigger when the user says things like "what agents do I need", "help me plan my agents", "I want to set up multiple agents", "document my agent", "agent permissions", "agent roles", "agent team", or asks about agent capabilities, responsibilities, tool access, or inter-agent communication. This skill produces a comprehensive Agent Team Documentation package (markdown + optional .docx) covering every agent's role, persona, permissions, tools, boundaries, and team interaction rules.
Surgically update existing OpenClaw agent workspace files based on conversational change requests — without rewriting the soul, persona, or hard limits. Use this skill when the user says things like "update the agent", "tell NEXUS about the new client", "HUNTER's ICP has changed", "add this to APEX's memory", "RPS paid their invoice", "change SENTINEL's heartbeat", "update the goals", "the client list changed", "add a new cron job", "remove the stale goal", "SCRIBE needs to know about ISO 14001 scope change", or any request to change, add, remove, or refresh content in an existing agent's workspace files. Also trigger when business state changes (new client, lost client, invoice paid, tender outcome, staff change, new service, pricing update) that should be reflected in agent memory. This skill identifies which files and sections need changing, shows exactly what will change before touching anything, makes surgical edits that preserve the persona soul, and outputs ready-to-apply file patches.
Run the complete IBS OpenClaw client onboarding process — from scoping a new client's agent requirements, through designing their agent architecture, building their workspace files and openclaw.json, to producing a professional handover package. Use this skill when IBS is onboarding a new client onto OpenClaw, productising the agent deployment service, creating a client's first agent setup, or when the user says things like "onboard this client", "set up OpenClaw for a new client", "create an agent for our client", "deploy agents for [company]", or "build the OpenClaw setup for [client name]". This skill runs the full IBS OpenClaw product workflow: client interview, needs assessment, architecture design, workspace generation, openclaw.json configuration, deploy script, and professional handover documentation.
| name | openclaw-docs |
| description | Use when the user asks about OpenClaw documentation sources, how to access crawled docs, where to find official documentation, how the documentation sync system works, or when referencing OpenClaw product docs for any task. |
The plugin maintains a local cache of official OpenClaw documentation from two upstream sources. This enables all skills and agents to reference authoritative, up-to-date product docs.
The official documentation site. Provides a machine-readable index at:
https://docs.openclaw.ai/llms.txt
This llms.txt file lists ~431 pages using Markdown link syntax:
- [Cron Jobs](https://docs.openclaw.ai/automation/cron-jobs)
- [Telegram Setup](https://docs.openclaw.ai/channels/telegram)
Categories: automation, channels, cli, concepts, gateway, install, platforms, plugins, providers, reference, security, start, tools, web
Source code and docs at https://github.com/openclaw/openclaw/tree/main/docs.
Raw content available at:
https://raw.githubusercontent.com/openclaw/openclaw/main/docs/<path>
Useful for: release notes, contribution guides, source-level documentation not on the docs site.
plugins/openclaw/
docs/ # Committed (metadata only)
docs-manifest.json # Tracks fetched pages, timestamps, hashes
INDEX.md # Categorized index with fetch status
FETCH-CONFIG.md # Source URLs, priority tiers, staleness rules
.crawled/ # Gitignored (regenerable content)
docs.openclaw.ai/ # Fetched from docs site
automation/
cron-jobs.md
webhooks.md
channels/
telegram.md
whatsapp.md
cli/
commands.md
...
github/ # Fetched from GitHub
docs/
start/
cli/
Why two tiers? The docs/ directory is committed to git so marketplace installs know what documentation exists. The .crawled/ directory is gitignored because it contains regenerable content that can be re-fetched with /oc-docs sync.
To read a cached documentation page:
Read .crawled/docs.openclaw.ai/<category>/<filename>.md
Examples:
Read .crawled/docs.openclaw.ai/automation/cron-jobs.mdRead .crawled/docs.openclaw.ai/channels/telegram.mdRead .crawled/docs.openclaw.ai/cli/commands.mdTo find what's available:
docs/INDEX.md for a categorized listingdocs/docs-manifest.json for detailed metadata| Tier | Categories | Pages | When Fetched |
|---|---|---|---|
| 1 | automation, channels, cli, concepts, gateway, security | ~148 | Default /oc-docs sync |
| 2 | install, providers, tools, platforms, reference, start | ~124 | --full or --category |
| 3 | web, plugins, root pages | ~13 | On explicit request only |
If .crawled/ doesn't exist or has no content, suggest the user run:
/oc-docs sync
This fetches Tier 1 documentation (~148 core pages). For all pages:
/oc-docs sync --full
When a skill needs authoritative OpenClaw documentation:
.crawled/docs.openclaw.ai/<category>/references/ content.crawled/ is entirely empty, suggest /oc-docs sync before proceedingThis ensures skills provide the most current information while gracefully degrading when docs haven't been synced.