escalation-manager

escalation-manager is a skill for Claude Code from jonny-1812/corebee-mcp-skills. It costs 55 tokens per session (1,556 once invoked), scanned A, original, MIT.

A support workflow for identifying urgent customer conversations, assigning them to suitable agents, recording escalation notes, and optionally preparing a reply.

In plain words
What is it for?
It helps escalate a known conversation, find available team members, assign work, add notes, draft an acknowledgment, and scan open conversations for issues needing immediate attention.
Why use it?
Critical tickets can be missed or handled without a clear record. This organizes the escalation process and can also review the open inbox for urgent items.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the corebee plugin — 10 skills, 4 commands, 4 agents, 3 hooks, 1 MCP server shipped together

Good fit It helps escalate a known conversation, find available team members, assign work, add notes, draft an acknowledgment, and scan open conversations for issues needing immediate attention.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonny-1812/corebee-mcp-skills/escalation-manager
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jonny-1812/corebee-mcp-skills --skill escalation-manager
Clone the repo
git clone --depth 1 https://github.com/jonny-1812/corebee-mcp-skills

Made for: Claude Code.

Or install corebee, the plugin that ships this one along with the rest of its 10 skills, 4 commands, 4 agents, 3 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for escalation-manager

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/escalation-manager/github.svg)](https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/escalation-manager)
Your own site
<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/escalation-manager"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/escalation-manager/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for escalation-manager

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/escalation-manager"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/escalation-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,556 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.01556
Opus 5 $0.00028 $0.00778
Sonnet 5 $0.00011 $0.00311
Haiku 4.5 $0.00006 $0.00156

Measured 12d ago against content hash 4052d30f7ef1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

escalation-manager scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/escalation-manager/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Escalation Manager

Handle critical customer conversations from detection through resolution — escalate, assign, respond, and de-escalate with full audit trails.

Workflow Modes

Escalate Specific Conversation

Escalate a known conversation by ID, assigning it to the best available agent and logging the escalation.

  1. Fetch the conversation using get_conversation with the provided conversation ID
  2. Fetch team members using list_team_members to find available agents
  3. Evaluate the conversation: read the full thread to understand severity, customer sentiment, and topic
  4. Select the best agent using the agent selection criteria below
  5. Assign the conversation using assign_conversation to the selected agent
  6. Log an escalation note on the contact using add_contact_note with the escalation reason, assigned agent, and timestamp
  7. Optionally draft an immediate acknowledgment response — present it to the user for approval before sending via reply_to_conversation
  8. Present the escalation summary

Scan for Urgent Items

Proactively scan the inbox for conversations that meet escalation criteria and present them for action.

  1. Fetch all open conversations using list_conversations with status: "open"
  2. Fetch team members using list_team_members to check availability
  3. For each open conversation, evaluate against the escalation criteria below
  4. For conversations that meet criteria, use get_conversation to read the full thread and confirm urgency
  5. Present a ranked list of conversations needing escalation, ordered by severity
  6. Ask the user which conversations to escalate
  7. For each confirmed escalation, run the Escalate Specific Conversation workflow

De-escalate

Close a resolved escalation, log the resolution, and optionally notify the customer.

  1. Fetch the conversation using get_conversation to confirm it is resolved
  2. Verify the customer's issue has been addressed by reviewing the thread
  3. Log a de-escalation note on the contact using add_contact_note with resolution details
  4. Optionally draft a closing message for the customer — present for approval before sending
  5. Close the conversation using close_conversation
  6. Present a de-escalation summary with resolution time and outcome

Read the full file on GitHub · 124 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 124 lines · 55 tokens per session scan A 4052d30f7ef1

Subscribe to this mod's changes

escalation-manager is a skill published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,556 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

customer-support

Use when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is technical-writing), a win-back program (retention), or the…

ericrisco/rsc-harness · 90 tokens

deskcrew-support

Run a customer support desk on DeskCrew. Read new tickets, answer from the knowledge base, and file replies for human approval. Use when handling customer support. Agents can also create and run their own bounty board over x402 with no account (the wallet that pays createboard owns it) and pay answering agents 85% on…

webmilmind1/deskcrew-mcp · 72 tokens

deskcrew-bounty-hunter

Earn USDC by answering bounty support tickets on DeskCrew's open board. Read the board free, buy ticket context over x402, draft an answer, submit it, and get paid 85% of the bounty when a human approves. Pays out on Base, Polygon, Avalanche, Sei, or Solana; on Solana the agent needs zero SOL. Since 08-2026 the wallet…

webmilmind1/deskcrew-mcp · 0 tokens

deskcrew-board-owner

Run your own USDC bounty board and pay AI agents to answer your questions. One x402 payment creates the board (no account, the paying wallet owns it), USDC deposits fund tasks, and approving an answer pays the winning agent 85% automatically on Base, Polygon, Avalanche, Sei, or Solana. Use when asked to delegate work…

webmilmind1/deskcrew-mcp · 93 tokens

Zendesk Automation

Automate customer support workflows with Zendesk ticket management, routing, and analytics.

claude-office-skills/skills · 19 tokens

customer-support-integration

Connect your helpdesk (Gorgias, Zendesk, Intercom) to your store so support agents see full order history and customer details without switching tools.

finsilabs/awesome-ecommerce-skills · 36 tokens