菜单
Use when OpenClaw support should be contacted, including escalation to @evaOS_support_bot or support@electricsheephq.com. Draft and redact first; ask the user before sending. Prefer GOG for email when available.
用 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 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.
| name | openclaw-support-escalation |
| description | Use when OpenClaw support should be contacted, including escalation to @evaOS_support_bot or support@electricsheephq.com. Draft and redact first; ask the user before sending. Prefer GOG for email when available. |
Before drafting, search local KB for the exact issue and read runbooks/self-diagnostics.md.
Create a concise support draft with:
Helper:
node ~/.gbrain/sources/openclaw-support-kb/scripts/support-escalation.mjs draft \
--issue "<short issue>" \
--doc "docs/<source-page>.md" \
--search-query "OpenClaw <feature> troubleshooting repair" \
--command-tried "openclaw config validate --json" \
--diagnostics <redacted-or-raw-diagnostics-file> \
--out /tmp/openclaw-support-draft.md
The helper redacts common token/password shapes and prints sha256=<draft hash>.
Still review the draft manually.
Before any send:
Use the helper only. It uses GOG internally because OpenClaw onboarding teaches
agents to use it, but support escalation must not call raw gog gmail send.
node ~/.gbrain/sources/openclaw-support-kb/scripts/support-escalation.mjs approval-context \
--channel email \
--draft <approved-draft.md> \
--recipient support@electricsheephq.com \
--subject "[OpenClaw Support] <short issue>" \
--account <explicit-account>
node ~/.gbrain/sources/openclaw-support-kb/scripts/support-escalation.mjs send-email \
--draft <approved-draft.md> \
--subject "[OpenClaw Support] <short issue>" \
--account <explicit-account> \
--approved-recipient support@electricsheephq.com \
--approved-draft-sha <sha256-from-reviewed-draft> \
--approved-context-sha <approved-context-sha>
Use the helper only. It uses OpenClaw Telegram messaging internally for
@evaOS_support_bot, but support escalation must not call raw
openclaw message send.
node ~/.gbrain/sources/openclaw-support-kb/scripts/support-escalation.mjs approval-context \
--channel Telegram \
--draft <approved-draft.md> \
--recipient @evaOS_support_bot
node ~/.gbrain/sources/openclaw-support-kb/scripts/support-escalation.mjs send-telegram \
--draft <approved-draft.md> \
--approved-recipient @evaOS_support_bot \
--approved-draft-sha <sha256-from-reviewed-draft> \
--approved-context-sha <approved-context-sha>
If neither GOG nor Telegram is configured, show the approved draft and tell the user to contact support@electricsheephq.com or @evaOS_support_bot.