Automation
Skill
/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
Claude Code
$ npx -y skills add 0xranx/golembot --skill escalation --agent claude-code
Codex
$ npx skills add 0xranx/golembot --skill escalation -a codex -y
Cursor
$ npx skills add 0xranx/golembot --skill escalation -a cursor -y
Gemini CLI
$ npx skills add 0xranx/golembot --skill escalation -a gemini-cli -y
GitHub Copilot
$ npx skills add 0xranx/golembot --skill escalation -a github-copilot -y
OpenCode
$ npx skills add 0xranx/golembot --skill escalation -a opencode -y
Windsurf
$ npx skills add 0xranx/golembot --skill escalation -a windsurf -y
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
Stats
325
Stars
48
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withgolembot
Any Agent × Any Provider × Anywhere. Connect Cursor, Claude Code, OpenCode, or Codex to Slack, Telegram, Discord, Feishu, DingTalk, WeCom, WeChat — with any LLM provider.
32613 skills
Stars on GitHub
Momentum
- stars in total
- 326
Other skills on golembot.
More skills from other plugins.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
@browser-useInstall Skillagent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…
@vercel-labs-2Install Skill
Questions about escalation.
- Which coding agents can use escalation?
- escalation installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.