New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Escalation Management

by cbrock84 in cbrock84/headcount

Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure.

MITAuto-check passedDevOps & Cloud

Install Escalation Management

skills CLI
$ npx skills add cbrock84/headcount --skill escalation-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount escalation-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/customer-experience/skills/escalation-management .claude/skills/escalation-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
escalation-management
GitHub stars
2k
Token cost
~930 tokens
SKILL.md length
518 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure.

  • Tasks that involve Incident response
  • SKILL.md covers Assess severity from the…, Running one, Executive escalation and Recovery, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Escalation Management is an agent skill from cbrock84/headcount. Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure. Use this when a customer issue is escalating or has gone to leadership, during a customer-affecting outage, when a major account is at risk, when a relationship needs repairing after a failure, or to design the escalation path itself.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in DevOps & Cloud, covering Incident response. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve Incident response

Example prompts

  • “Use the escalation-management skill to handle customer situations that have exceeded normal support — severity assessment, incident communication…”
  • “/escalation-management”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Escalation Management loads about 930 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 518 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~930
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 518 words, ~930 tokens.

Download SKILL.mdSave it as .claude/skills/escalation-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
escalation-management
description
Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure. Use this when a customer issue is escalating or has gone to leadership, during a customer-affecting outage, when a major account is at risk, when a relationship needs repairing after a failure, or to design the escalation path itself.

Escalation management

An escalation is a signal that the normal path failed. Handling it well matters; the more useful question afterward is why it was needed.

Assess severity from the customer's position

Severity is what it costs them, not how alarming it looks internally. A cosmetic bug blocking a regulated filing is severe. A total outage of a feature nobody uses is not.

Ask: what can they not do, how many people, is there a workaround, and is there a deadline attached. That last one converts a medium into a critical more often than anything technical.

Running one

Own it visibly. One named person, introduced to the customer, who does not disappear. Escalations get worse when ownership is ambiguous — the customer starts re-explaining, which is its own insult.

Communicate on a stated cadence, and hold it even when there is nothing new. "No update yet, next update at three" preserves trust; silence destroys it faster than bad news does. Customers escalate again because they heard nothing, far more often than because of the underlying issue.

Separate acknowledgment from explanation. Acknowledge the impact immediately, in their terms. Explanation comes when you actually know. Leading with a cause you have not confirmed means retracting it later, and the retraction is what they remember.

Do not over-promise to end the conversation. Every commitment made under pressure to a frustrated customer is a commitment someone has to keep, and failing a recovery promise ends the relationship.

Executive escalation

When a customer reaches your leadership, the relationship is already damaged — the escalation is the symptom.

Brief the executive properly before the call: what happened, what we have done, what we are committing to, and what not to promise. An executive walking in uninformed makes commitments the delivering team learns about afterward.

Show full SKILL.md (222 more words)Show less

Recovery

Recovery is not an apology. It is: acknowledge specifically what failed, say what changed so it cannot recur, and demonstrate it over time. Credits and discounts are compensation, not recovery — they close the ledger without addressing the trust.

The strongest recovery move is showing them the fix shipped.

Afterward

Every escalation gets a short review: what made the normal path fail, was severity assessed correctly, did we communicate on time, and what would have prevented it.

Escalation volume is a health metric for the whole function. Rising escalations mean the normal path is failing more often, and that is the thing to fix.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Escalate without naming an owner. An escalation with no name on it is a broadcast.
  • Commit to a fix date on the customer's call before engineering has said one exists.
  • Let the executive sponsor become the case owner. Sponsors unblock; they do not run the case.
  • Close on the technical fix. It closes when the customer says it is closed.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/customer-experience/skills/escalation-management of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Escalation Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Escalation Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Escalation Management this skillcbrock84/headcount2k—~930Automated safety check: PassMIT
Kubernetes Network Root Cause Analysiskubeshark/kubeshark12k—~5.3kAutomated safety check: PassApache-2.0
UModel Root Cause Analysisalibaba/UnifiedModel415—~1.9kAutomated safety check: PassCustom licence
Learningskortix-ai/suna20k—~1.1kAutomated safety check: PassCustom licence
Oncallpigweed-project/pigweed548—~992Automated safety check: PassApache-2.0
Loop Triage Reportcobusgreyling/loop-engineering11k—~500Automated safety check: PassMIT

Similar skills

  • Kubernetes Network Root Cause Analysis

    kubeshark/kubeshark

    Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.

    12k GitHub stars~5.3k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • UModel Root Cause Analysis

    alibaba/UnifiedModel

    Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.

    415 GitHub stars~1.9k tokensUpdated 16 days ago
    DevOps & CloudAuto-check passed

  • Learnings

    kortix-ai/suna

    The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident.

    20k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Oncall

    pigweed-project/pigweed

    Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).

    548 GitHub stars~992 tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Loop Triage Report

    cobusgreyling/loop-engineering

    Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.

    11k GitHub stars~500 tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Axiom SRE Investigator

    openclaw/clawhub

    Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.

    9.5k GitHub stars~7.1k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo

  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 22 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 22 days ago
    Auto-check passed

  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 22 days ago
    Auto-check passed

  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 22 days ago
    Auto-check passed

  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 22 days ago
    Auto-check passed

  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 22 days ago
    Auto-check passed

Categories

Questions about Escalation Management

What does Escalation Management do?

Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure. Escalation Management is an agent skill from cbrock84/headcount. Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure.

When should I use Escalation Management?

Escalation Management fits situations like: tasks that involve Incident response.

How do I install Escalation Management in Claude Code?

Run `npx skills add cbrock84/headcount --skill escalation-management -a claude-code`. Or copy the skill folder (plugins/customer-experience/skills/escalation-management in cbrock84/headcount) into .claude/skills/escalation-management in your project. Claude Code loads it when a task matches its description.

How do I install Escalation Management in Codex?

Run `npx skills add cbrock84/headcount --skill escalation-management -a codex`. Or copy the skill folder (plugins/customer-experience/skills/escalation-management in cbrock84/headcount) into .agents/skills/escalation-management in your project. Codex loads it when a task matches its description.

Can I use Escalation Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill escalation-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/escalation-management, .gemini/skills/escalation-management, .github/skills/escalation-management and .opencode/skills/escalation-management in your project.

What does Escalation Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Escalation Management is instructions for the agent only.

Does Escalation Management access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Escalation Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Escalation Management use?

Escalation Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Escalation Management use?

About 930 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 236 tokens, read only when the agent opens those files.

What are the alternatives to Escalation Management?

Skills that share tags, products or a category with Escalation Management: Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars), Learnings (kortix-ai/suna, 20k stars) and Oncall (pigweed-project/pigweed, 548 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Escalation Management?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,016 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.