菜单
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.
用 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 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 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 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 | cross-system-recovery |
| description | 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. |
Target system facts beat acting system convenience. The agent performing the repair should use its own tools to inspect and apply changes, but the broken system's docs decide what is valid.
gbrain search "<target system> <exact error> <config key>" --source openclaw-support-kb
gbrain search "<actor system> run shell command approval workspace" --source openclaw-support-kb
openclaw config schema, openclaw config patch --dry-run, and openclaw config validate.Stop if docs disagree, the target is ambiguous, credentials are needed, the user has not approved a write/send action, or the next step would replace a whole config/database instead of making a narrow reversible change.