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.
Design a support/incident escalation tree — who handles what, when it escalates, and to whom.
Install Escalation Tree
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-tree --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/escalation-tree .claude/skills/escalation-tree && rm -rf skills-srcUse ~/.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/
Install the "escalation-tree" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-tree into .claude/skills/escalation-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-tree", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-treeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-tree --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/escalation-tree .agents/skills/escalation-tree && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "escalation-tree" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-tree into .agents/skills/escalation-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-tree", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-tree --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/escalation-tree .cursor/skills/escalation-tree && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "escalation-tree" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-tree into .cursor/skills/escalation-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-tree", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/escalation-tree--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-tree --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/escalation-tree .gemini/skills/escalation-tree && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "escalation-tree" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-tree into .gemini/skills/escalation-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-tree", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills escalation-treeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/escalation-tree .github/skills/escalation-tree && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "escalation-tree" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-tree into .github/skills/escalation-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-tree", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-tree --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/escalation-tree .opencode/skills/escalation-tree && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "escalation-tree" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-tree into .opencode/skills/escalation-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-tree", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
escalation-tree- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 474 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design a support/incident escalation tree — who handles what, when it escalates, and to whom.
- Asked to design an escalation path
- SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- An escalation matrix
What it does
Escalation Tree is an agent skill from mohitagw15856/pm-claude-skills. Design a support/incident escalation tree — who handles what, when it escalates, and to whom. Use when asked to design an escalation path, an escalation matrix, support tiers, an on-call escalation policy, or to fix 'tickets bounce around / nothing gets escalated in time'. Produces an escalation tree — tiers & ownership, severity definitions, time-based triggers, routing rules, contacts/roles, and the customer-communication cadence per level.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Incident response. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to design an escalation path
- An escalation matrix
- An on-call escalation policy
- Fix tickets bounce around / nothing gets escalated in time
Example prompts
- “tickets bounce around / nothing gets escalated in time”
- “/escalation-tree”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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 Tree loads about 1k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 474 words of instructions outside code blocks.
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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 474 words, ~1,001 tokens.
Download SKILL.mdSave it as
.claude/skills/escalation-tree/SKILL.md (or your agent's skills folder).- name
- escalation-tree
- description
- Design a support/incident escalation tree — who handles what, when it escalates, and to whom. Use when asked to design an escalation path, an escalation matrix, support tiers, an on-call escalation policy, or to fix 'tickets bounce around / nothing gets escalated in time'. Produces an escalation tree — tiers & ownership, severity definitions, time-based triggers, routing rules, contacts/roles, and the customer-communication cadence per level.
Escalation Tree Skill
Escalation goes wrong two ways: things sit too long before someone senior is pulled in, or everything gets escalated and senior people drown. A clear escalation tree fixes both — it defines the tiers, the severity that sets the path, the time triggers that force escalation, and who owns each step. This skill designs that, so the right person is on the right issue at the right time.
Required Inputs
Ask for these only if they aren't already provided:
- The context — customer support, incident/on-call, or both.
- The tiers/teams available — tier-1/2/3, engineering on-call, management, exec.
- Severity meaning — what counts as critical vs. high vs. normal in your context.
- Constraints — hours of coverage, SLAs/contractual response times, key roles.
Output Format
Escalation Tree: [support / incident]
1. Severity levels — define each (SEV1/P1 … or Critical/High/Normal/Low) with concrete criteria — what qualifies, blast radius, and the response & resolution targets per level. Ambiguous severity is why escalation fails.
2. The tiers — who owns what:
| Tier | Owns | Can resolve | Escalates when |
|---|---|---|---|
| Tier 1 | first response, known issues | runbook items | unresolved in [time] or sev ≥ [x] |
| Tier 2 | deeper diagnosis | most issues | needs code/infra change |
| Eng on-call | code/infra | the system | — |
3. The tree (routing) — by severity, the path and the time triggers:
SEV1 → page eng on-call immediately + notify manager; if unacked in 5 min → secondary; if 15 min → eng lead. Normal → tier-1; if unresolved in 1 business day → tier-2.
Show the branch logic clearly (who, after how long, to whom).
4. Contacts & roles — by role (not just names — names change): who fills each, primary/secondary, and how they're reached per severity (page vs. Slack vs. ticket).
5. Customer communication — the update cadence per severity (e.g. SEV1: status-page + update every 30 min; normal: reply within SLA). Who owns the customer comms vs. the fix.
6. After — for high-sev, the handoff to a postmortem (pair with incident-postmortem).
Show full SKILL.md (168 more words)Show less
Quality Checks
- Severity levels have concrete qualifying criteria + response/resolution targets
- Each tier's ownership and "escalate when" condition is explicit
- Escalation triggers are time-boxed (after N minutes/days), not "when needed"
- Routing is defined by role with primary/secondary and the contact method per severity
- Customer-communication cadence is specified per level, with an owner
- High-severity paths hand off to a postmortem
Anti-Patterns
- Do not leave severity fuzzy — if "critical" is subjective, everything becomes critical (or nothing does)
- Do not write "escalate when needed" — time-box it so issues don't rot waiting on judgement
- Do not route to named people only — use roles with primary/secondary; people leave and go on holiday
- Do not forget customer comms in the tree — internal escalation without customer updates still feels like neglect
- Do not over-escalate everything — tiers exist so seniors see only what truly needs them
Based On
Support & incident-management practice — severity matrices, tiered ownership, time-based escalation, on-call routing.
Example Trigger Phrases
- "Design an escalation path."
- "Support tiers."
- "Fix tickets bounce around / nothing gets escalated in time."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/escalation-tree of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Escalation Tree 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Escalation Tree this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| Nix Config Debugryan4yin/nix-config | 2.1k | — | ~1.2k | Automated safety check: Pass | MIT | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 415 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Learningskortix-ai/suna | 20k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Oncallpigweed-project/pigweed | 548 | — | ~963 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Nix Config Debug
ryan4yin/nix-config
A skill your agent uses when something here is broken or stops working: an eval or build error, a failed activation, a dead or restarting unit, a mihomo or DNS outage, an unreachable host or MicroVM…
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.
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.
Oncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
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.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Escalation Tree
What does Escalation Tree do?
Design a support/incident escalation tree — who handles what, when it escalates, and to whom. Escalation Tree is an agent skill from mohitagw15856/pm-claude-skills. Design a support/incident escalation tree — who handles what, when it escalates, and to whom.
When should I use Escalation Tree?
Escalation Tree fits situations like: asked to design an escalation path; an escalation matrix; an on-call escalation policy; fix tickets bounce around / nothing gets escalated in time.
How do I install Escalation Tree in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree -a claude-code`. Or copy the skill folder (skills/escalation-tree in mohitagw15856/pm-claude-skills) into .claude/skills/escalation-tree in your project. Claude Code loads it when a task matches its description.
How do I install Escalation Tree in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill escalation-tree -a codex`. Or copy the skill folder (skills/escalation-tree in mohitagw15856/pm-claude-skills) into .agents/skills/escalation-tree in your project. Codex loads it when a task matches its description.
Can I use Escalation Tree 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 mohitagw15856/pm-claude-skills --skill escalation-tree -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-tree, .gemini/skills/escalation-tree, .github/skills/escalation-tree and .opencode/skills/escalation-tree in your project.
What does Escalation Tree need to run?
SKILL.md names no scripts, command-line tools or credentials: Escalation Tree is instructions for the agent only.
Does Escalation Tree 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 Tree 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 Tree use?
Escalation Tree 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 Tree use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Escalation Tree?
Skills that share tags, products or a category with Escalation Tree: Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), Nix Config Debug (ryan4yin/nix-config, 2.1k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars) and Learnings (kortix-ai/suna, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Escalation Tree?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.