メニュー
Use when a user or agent needs to inspect, change, repair, validate, or troubleshoot OpenClaw config, openclaw.json, channel config, SecretRefs, plugins.entries config, or startup failures caused by invalid config.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use for Paperclip, Mission Control, companies, goals, org charts, agents, tickets, heartbeats, budgets, approvals, dashboard, API, CLI, deploy, adapter, or board-operator questions.
Use when a customer question may involve OpenClaw, Hermes Agent, Paperclip Mission Control, Composio integrations, cross-agent repair, system setup, config, messaging, or support and the target system must be identified before answering.
Use for evaOS Live Browser, KasmVNC, VNC, visible Chromium, CDP, screenshots, authenticated browser handoff, Arbostar UI, WPForms production lead tests, or browser-based customer tool operation.
Use when OpenClaw, Hermes Agent, or Paperclip must diagnose or repair another system, when the acting agent and broken target are different, or when docs from multiple systems might conflict.
Use for Hermes Agent setup, gateway, Telegram/messaging, config.yaml, skills, memory, sessions, MCP, cron, provider, update, or troubleshooting questions. Search the local Hermes namespace before using OpenClaw or Paperclip docs.
Use when the user wants to find, evaluate, install, update, or improve OpenClaw skills or small-business integrations. Search the local VoltAgent skills snapshot, ClawHub/OpenClaw skill search, and Composio integration path; pin candidate sources and run Snyk agent-scan before skill install.
| name | openclaw-config-repair |
| description | Use when a user or agent needs to inspect, change, repair, validate, or troubleshoot OpenClaw config, openclaw.json, channel config, SecretRefs, plugins.entries config, or startup failures caused by invalid config. |
Use this skill only for OpenClaw config. If the target is Hermes Agent or Paperclip Mission Control, switch to customer-kb-router and the matching target skill.
openclaw config file
openclaw config validate --json
gbrain search "OpenClaw <config path or error>" --source openclaw-support-kb
gbrain search "OpenClaw config schema patch dry-run validate rejected clobbered <intent>" --source openclaw-support-kb
runbooks/config-repair.md for the workflow, then inspect schema before proposing a key:
openclaw config schema > /tmp/openclaw.schema.json
openclaw config set <path> <value> --dry-run
openclaw config patch --file <patch.json5> --dry-run
openclaw config patch --file <patch.json5>
openclaw config validate
plugins.entries.<id>.config fails validation, compare the live plugin manifest schema against the config block before changing unrelated settings..rejected.* or .clobbered.* beside the active config and copy back only intended keys.