菜单
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.
用 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 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 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 | customer-kb-router |
| description | 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. |
Identify the target system before giving commands or config advice. If the user says "the agent", "bot", "gateway", "config", "Telegram", or "dashboard" without naming the system, ask one short clarifying question or run read-only discovery first.
Search local GBrain with the target system marker:
gbrain search "OpenClaw <question or exact error> Source: https://docs.openclaw.ai" --source openclaw-support-kb
gbrain search "Hermes Agent <question or exact error> Local KB namespace: hermes-agent" --source openclaw-support-kb
gbrain search "Paperclip Mission Control <question or exact error> Local KB namespace: paperclip-mission-control" --source openclaw-support-kb
gbrain search "Composio <app or workflow> Source: https://docs.composio.dev" --source openclaw-support-kb
gbrain search "evaOS Live Browser KasmVNC CDP screenshot authenticated browser handoff" --source openclaw-support-kb
If --source is unsupported, rerun the same search without it and reject stale .pre-git- citations.
| Target | Config/data surface | Commands/docs to prefer |
|---|---|---|
| OpenClaw | openclaw.json, ~/.openclaw, workspace AGENTS.md | openclaw ..., docs/, runbooks/ |
| Hermes Agent | ~/.hermes/config.yaml, ~/.hermes/.env, ~/.hermes/skills | hermes ..., systems/hermes/ |
| Paperclip Mission Control | Paperclip database, env/deploy config, companies, agents, tickets | systems/paperclip/, Paperclip CLI/API docs |
| evaOS Live Browser | KasmVNC, visible Chromium, loopback CDP, screenshots | evaos-live-browser, evaos-browser-control, runbooks/evaos-live-browser-agent-kit.md |
| Composio | Integration/MCP/OAuth app connection | integrations/composio/, OpenClaw MCP docs |
When one runtime is fixing another, search the broken target first and the acting runtime second:
Stop before applying config when the cited docs are for a different system, the target system is ambiguous, or the next step would replace a config file instead of making a validated narrow change.