ワンクリックでManusで任意のスキルを実行

openclaw-support-kb

スター1

フォーク0

更新日2026年5月16日 10:19

Use for OpenClaw setup, channel configuration, update, runtime, troubleshooting, and support questions. Search the local GBrain OpenClaw support KB first and answer with citations instead of guessing.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

electricsheephq

electricsheephq/openclaw-support-kb

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

OpenClaw Support KB

Workflow

Search local GBrain first:

gbrain search "OpenClaw <user question> Source: https://docs.openclaw.ai" --source openclaw-support-kb
gbrain search "OpenClaw <exact error or config key> Source: https://docs.openclaw.ai" --source openclaw-support-kb

If the user may mean Hermes Agent or Paperclip Mission Control, chain into customer-kb-router before giving commands.
If a runbook appears, treat it as a workflow only. Run its Search Contract before answering.
Ignore any result or filesystem path containing .pre-git-, archive/openclaw-support-kb, or another backup-looking support KB copy. Run node ~/.gbrain/sources/openclaw-support-kb/scripts/status.mjs and retry exact source URL searches if that appears.
Use docs/ pages as factual source, runbooks/ as process, and releases/ for version context.
Cite source URLs from docs/ whenever possible. Cite a runbook only for workflow choices.
If the question touches config, chain into openclaw-config-repair.
If local results are missing or stale, run:
```
openclaw docs "<query>"
```
If the user still needs help, chain into openclaw-support-escalation.

Scenario Routing

"How does OpenClaw work?" -> runbooks/system-explainer.md
"Create a new agent" -> runbooks/agent-creation.md
"Set up Telegram" -> runbooks/telegram-setup.md
"Set up another channel" -> runbooks/channel-setup.md
"Config broke / openclaw.json" -> openclaw-config-repair
"Find/install a skill" -> openclaw-skill-discovery
"Contact support" -> openclaw-support-escalation
"Hermes, Paperclip, Mission Control, or unclear system" -> customer-kb-router

Answer Rules

Do not invent OpenClaw config keys or channel settings.
Do not apply OpenClaw config guidance to Hermes ~/.hermes/config.yaml or Paperclip control-plane settings.
Mention uncertainty clearly when the KB does not contain a fact.
Do not cite stale support KB backups. Citations should come from current docs/, runbooks/, releases/, integrations/, security/, or source URLs.
Prefer short, actionable steps the customer can run locally.
For nontechnical users, explain each command before running it and avoid dumping full configs unless necessary.
For Telegram, always distinguish bot token, human Telegram user ID, group chat ID, allowFrom, groupAllowFrom, and groups.
For updates, distinguish stable and beta/prerelease behavior.

Local KB Paths

Default source: ~/.gbrain/sources/openclaw-support-kb
Manifest: ~/.gbrain/sources/openclaw-support-kb/kb-manifest.json

Refresh:

node ~/.gbrain/sources/openclaw-support-kb/scripts/run-client-update.mjs --reason manual
node ~/.gbrain/sources/openclaw-support-kb/scripts/status.mjs

このリポジトリの他の Skills

同じリポジトリ

paperclip-mission-control

electricsheephq/openclaw-support-kb

Use for Paperclip, Mission Control, companies, goals, org charts, agents, tickets, heartbeats, budgets, approvals, dashboard, API, CLI, deploy, adapter, or board-operator questions.

2026-05-221

customer-kb-router

electricsheephq/openclaw-support-kb

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.

2026-05-191

evaos-live-browser-operator

electricsheephq/openclaw-support-kb

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.

2026-05-191

cross-system-recovery

electricsheephq/openclaw-support-kb

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.

2026-05-161

hermes-support-kb

electricsheephq/openclaw-support-kb

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.

2026-05-161

openclaw-config-repair

electricsheephq/openclaw-support-kb

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.

2026-05-161

OpenClaw Support KB

Workflow

Search local GBrain first:

gbrain search "OpenClaw <user question> Source: https://docs.openclaw.ai" --source openclaw-support-kb gbrain search "OpenClaw <exact error or config key> Source: https://docs.openclaw.ai" --source openclaw-support-kb

If the user may mean Hermes Agent or Paperclip Mission Control, chain into customer-kb-router before giving commands.

If a runbook appears, treat it as a workflow only. Run its Search Contract before answering.

Ignore any result or filesystem path containing .pre-git-, archive/openclaw-support-kb, or another backup-looking support KB copy. Run node ~/.gbrain/sources/openclaw-support-kb/scripts/status.mjs and retry exact source URL searches if that appears.

Use docs/ pages as factual source, runbooks/ as process, and releases/ for version context.

Cite source URLs from docs/ whenever possible. Cite a runbook only for workflow choices.

If the question touches config, chain into openclaw-config-repair.

If local results are missing or stale, run:

openclaw docs "<query>"

If the user still needs help, chain into openclaw-support-escalation.

Scenario Routing

"How does OpenClaw work?" -> runbooks/system-explainer.md

"Create a new agent" -> runbooks/agent-creation.md

"Set up Telegram" -> runbooks/telegram-setup.md

"Set up another channel" -> runbooks/channel-setup.md

"Config broke / openclaw.json" -> openclaw-config-repair

"Find/install a skill" -> openclaw-skill-discovery

"Contact support" -> openclaw-support-escalation

"Hermes, Paperclip, Mission Control, or unclear system" -> customer-kb-router

Answer Rules

Do not invent OpenClaw config keys or channel settings.

Do not apply OpenClaw config guidance to Hermes ~/.hermes/config.yaml or Paperclip control-plane settings.

Mention uncertainty clearly when the KB does not contain a fact.

Do not cite stale support KB backups. Citations should come from current docs/, runbooks/, releases/, integrations/, security/, or source URLs.

Prefer short, actionable steps the customer can run locally.

For nontechnical users, explain each command before running it and avoid dumping full configs unless necessary.

For Telegram, always distinguish bot token, human Telegram user ID, group chat ID, allowFrom, groupAllowFrom, and groups.

For updates, distinguish stable and beta/prerelease behavior.

Local KB Paths

Default source: ~/.gbrain/sources/openclaw-support-kb

Manifest: ~/.gbrain/sources/openclaw-support-kb/kb-manifest.json

Refresh:

node ~/.gbrain/sources/openclaw-support-kb/scripts/run-client-update.mjs --reason manual
node ~/.gbrain/sources/openclaw-support-kb/scripts/status.mjs

name	openclaw-support-kb
description	Use for OpenClaw setup, channel configuration, update, runtime, troubleshooting, and support questions. Search the local GBrain OpenClaw support KB first and answer with citations instead of guessing.