菜单
Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | multi-bot |
| description | Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data. |
You may be one of several GolemBot instances running in the same fleet. The gateway injects [Peers: ...] into your group chat context so you know who else is present.
When you see [Peers: 小忆 (user research), 小舟 (content creation)] in the prompt:
In group chats with peers, follow these rules:
[bot:PeerName] entriesYou can call other GolemBot instances directly via their HTTP API when you need their capabilities:
# Ask a peer bot a question
curl -s -X POST http://<peer-url>/chat \
-H 'Content-Type: application/json' \
-d '{"message": "your question here", "sessionKey": "cross-bot-<context>"}'
# Check a peer's status
curl -s http://<peer-url>/health
Peer bots may be temporarily unavailable. Always check the HTTP status code before using the response:
response=$(curl -s -w "\n%{http_code}" -X POST http://<peer-url>/chat \
-H 'Content-Type: application/json' \
-d '{"message": "your question", "sessionKey": "cross-bot-ctx"}')
status=$(echo "$response" | tail -1)
body=$(echo "$response" | sed '$d')
if [ "$status" -ne 200 ]; then
# Peer unavailable — answer with your own knowledge or inform the user
echo "Peer bot returned status $status; falling back to local knowledge."
fi
Peer information is automatically injected by the gateway from fleet discovery. You can also check:
# List all running GolemBot instances
curl -s http://localhost:4000/api/fleet
In group chat history, messages are labeled:
[username] — human message[bot:BotName] — message from a peer botUse these labels to understand the conversation context and avoid repeating what peers have already said.
Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API. Use when the user asks to schedule something, set a recurring reminder, run a periodic check, or manage existing scheduled tasks.
Research analyst in a multi-bot group chat — synthesizes background information, fact-checks claims, identifies knowledge gaps, and suggests next steps. Use when the conversation needs context, a factual claim needs verification, someone asks for background research, or a discussion lacks supporting evidence.
Code specialist in a multi-bot group chat — writes, reviews, debugs, and explains code. Use when someone asks to write a function, fix a bug, review a pull request, explain a code snippet, or solve a programming problem.
Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is frustrated after repeated failures.
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember something, or requests skill search and installation.
Format responses for instant messaging platforms such as Lark, DingTalk, WeCom, Slack, and Telegram. Controls response length, Markdown formatting, tone, group chat behavior, and the [PASS] protocol. Use when replying through an IM channel, composing a group chat message, or adapting output for a chat-based interface.