/escalation
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
$ npx -y skills add 0xranx/golembot --skill escalation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/escalation
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
escalation.SKILL.mdname: escalation
description: "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."
Human Escalation Protocol
When you encounter a situation you cannot handle, escalate to a human agent by recording the escalation.
When to Escalate
- You cannot confidently answer the user's question
- The user explicitly asks to speak to a human
- The request involves sensitive operations (financial, legal, security)
- You detect a safety concern
- The user is frustrated after multiple failed attempts
How to Escalate
1. Inform the user that their request is being escalated 2. Write an escalation record to `.golem/escalations.jsonl` (one JSON object per line):
echo '{"ts":"2026-03-15T10:00:00Z","sessionKey":"feishu:chat123:user456","reason":"User requested human support for billing issue","context":"User asked about refund policy, I could not find the answer","status":"open"}' >> .golem/escalations.jsonlEscalation Record Schema
| Field | Type | Description | |-------|------|-------------| | `ts` | string | ISO 8601 timestamp | | `sessionKey` | string | The current session key | | `reason` | string | Why this is being escalated | | `context` | string | Brief summary of what was discussed | | `status` | string | Always `"open"` when creating |
Response Template
When escalating, respond to the user like:
> I've flagged this for human review. A team member will follow up on your request about [topic]. In the meantime, is there anything else I can help with?
Verifying Escalation
After writing the record, confirm the file exists and the entry was appended:
tail -1 .golem/escalations.jsonl
Read more
name: escalation description: "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."
Human Escalation Protocol
When you encounter a situation you cannot handle, escalate to a human agent by recording the escalation.
When to Escalate
- You cannot confidently answer the user's question
- The user explicitly asks to speak to a human
- The request involves sensitive operations (financial, legal, security)
- You detect a safety concern
- The user is frustrated after multiple failed attempts
How to Escalate
1. Inform the user that their request is being escalated 2. Write an escalation record to `.golem/escalations.jsonl` (one JSON object per line):
echo '{"ts":"2026-03-15T10:00:00Z","sessionKey":"feishu:chat123:user456","reason":"User requested human support for billing issue","context":"User asked about refund policy, I could not find the answer","status":"open"}' >> .golem/escalations.jsonlEscalation Record Schema
| Field | Type | Description | |-------|------|-------------| | `ts` | string | ISO 8601 timestamp | | `sessionKey` | string | The current session key | | `reason` | string | Why this is being escalated | | `context` | string | Brief summary of what was discussed | | `status` | string | Always `"open"` when creating |
Response Template
When escalating, respond to the user like:
> I've flagged this for human review. A team member will follow up on your request about [topic]. In the meantime, is there anything else I can help with?
Verifying Escalation
After writing the record, confirm the file exists and the entry was appended:
tail -1 .golem/escalations.jsonl
Any Agent × Any Provider × Anywhere. Connect Cursor, Claude Code, OpenCode, or Codex to Slack, Telegram, Discord, Feishu, DingTalk, WeCom, WeChat — with any LLM provider.
Repo: 0xranx/golembot
Other skills on golembot.
- /general
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
Open skill - /im-adapter
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
Open skill - /kb-guide
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be
Open skill - /message-push
Send proactive messages to IM groups or individual users via the gateway Send API. Use when the user says to send, post, notify, forward, or tell someone a message on Feishu, Slack, Telegram, Discord, DingTalk, or WeCom.
Open skill - /multi-bot
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.
Open skill - /task-manager
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.
Open skill