escalation
Guide support teams on when and how to escalate issues effectively with structured briefs
Best use case
escalation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guide support teams on when and how to escalate issues effectively with structured briefs
Teams using escalation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/escalation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How escalation Compares
| Feature / Agent | escalation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guide support teams on when and how to escalate issues effectively with structured briefs
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Escalation Skill Summary This guide teaches support teams when and how to escalate issues effectively. Here are the key takeaways: ## Escalation Triggers Escalate when issues involve confirmed bugs, production outages, data integrity risks, security concerns, or high-value customers at risk. Technical escalations include: bug confirmed and needs a code fix, infrastructure investigation needed, data corruption or loss. ## Tier Structure Issues flow through escalation levels (L1 -> L2 -> Engineering/Product) based on complexity and impact. Security concerns bypass normal progression and go immediately to the security team. ## Critical Success Factor: Reproduction Steps Good reproduction steps are the single most valuable thing in a bug escalation. Effective steps start from a clean state, use specific values, document the environment, and include exact error messages. ## Quantifying Impact Strong escalations measure impact across breadth (how many customers), depth (severity), duration, revenue at risk, reputation risk, and contractual obligations. This prevents vague escalations from being deprioritized. ## Post-Escalation Ownership Support maintains customer relationship responsibility after escalating. Follow-up frequency depends on severity: critical issues get updates every 2-4 hours; high-severity issues every 4-8 hours; medium issues every 1-2 business days.
Related Skills
canned-responses-escalation-triggers-all-categories
Sub-skill of canned-responses: Universal Escalation Triggers (Apply to All Categories) (+2).
test-oversized-skill
A test fixture skill that exceeds 200 lines with multiple H2/H3 sections for split testing.
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
agent-os-framework
Generate standardized .agent-os directory structure with product documentation, mission, tech-stack, roadmap, and decision records. Enables AI-native workflows.
OrcaFlex Specialist Skill
```yaml
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
domain-knowledge-sweep
Systematic multi-source research of an engineering domain. Spawns parent issue → 6 research subissues (Standards, Academic, Industry, LinkedIn-marketing, Code-audit, Synthesis) → gap implementation subissues. Replaces LinkedIn-only extraction with defensible comprehensive sourcing.
subagent-write-verification
Independently verify subagent-claimed file writes with filesystem and git checks before treating the artifact as real, before committing it, and before referencing the path in downstream prompts.
git-operation-serialization-preflight
Before any commit, stash, merge, reset, rebase, or checkout in a multi-agent or shared-checkout environment, run a bounded preflight to detect active git writers and stale index/config locks, then serialize the mutating step under a single-writer guarantee.
public-knowledge-graph-governance
Maintain public-safe knowledge graph artifacts for llm-wiki and similar markdown knowledge bases. Use when changing graph generators, validators, schema docs, weekly freshness checks, or public/private source-scope boundaries.
llm-wiki-weekly-freshness
Class-level governance workflow for keeping llm-wiki-style markdown knowledge bases current, public-safe, graph/index-valid, and useful for code development. Use when reviewing llm-wiki architecture/content, scanning new LLM concepts, maintaining public knowledge graphs, producing an issue roadmap, or running recurring freshness cadence.