skills.rest
aimentor606
aimentor606COMMUNITY
Explore all skills by this author →
GitHub

escalation

Determine escalation criteria and generate structured escalation briefs for support issues.

Updated Apr 8, 2026
Search Tags:#support#escalation#reproduction-steps#incident-management#ticketing#business-impact#escalation-templates
One-click install
npx skills add https://github.com/aimentor606/aether --skill escalation-aimentor606
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: escalation
Source: https://github.com/aimentor606/aether/tree/main/core/kortix-master/opencode/skills/GENERAL-KNOWLEDGE-WORKER/escalation
Command: npx skills add https://github.com/aimentor606/aether --skill escalation-aimentor606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Support teams struggle to know when to escalate issues and what information receiving teams need to act; this Skill provides a structured approach to decide escalation vs. support resolution and to produce complete, actionable escalation briefs that accelerate time-to-resolution.

Core Features & Use Cases

  • Decision Criteria: Clear rules for when to handle in support and when to escalate (technical, impact, business, time, pattern, security).
  • Structured Escalation Template: A ready-to-use format covering severity, impact, reproduction steps, what's been tried, customer communication, and specific asks.
  • Follow-up & De-escalation Guidance: Recommended follow-up cadence by severity and steps to de-escalate when appropriate.
  • Use Case: Frontline support creates an L2→Engineering escalation with reproduction steps, environment details, and a two-hour deadline for a production outage affecting multiple customers.

Quick Start

Create an escalation brief that summarizes the issue, quantifies impact, lists reproduction steps and evidence, and states the specific action and deadline required.

Frequently Asked Questions about escalation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an escalation brief for a production outage?▼

An escalation brief for a production outage requires structured reproduction steps, quantified business impact, severity level, attempted fixes, and specific asks with deadlines. This ensures receiving engineering teams can act immediately to resolve the incident.

When should I escalate a support ticket instead of resolving it myself?▼

Escalate a support ticket when issues involve technical complexity, broad business impact, security incidents, SLA breaches, or recurring patterns beyond frontline resolution scope. Clear decision criteria prevent unnecessary escalations while ensuring critical bugs receive immediate engineering attention.

What should be included in an incident management escalation template?▼

An incident management escalation template should include severity rating, customer communication status, environment details, evidence, reproduction steps, prior troubleshooting actions, business impact assessment, and specific action requests with deadlines for the receiving team.

How do I assess business impact for a high-value customer complaint?▼

Assess business impact for high-value customer complaints by quantifying affected users, revenue risk, SLA breach severity, and outage scope. Structured impact assessment determines appropriate severity levels and guides follow-up cadence for escalated incidents.

What follow-up cadence should I use after escalating a technical support issue?▼

Follow-up cadence after escalating technical support issues depends on severity level, with higher severity requiring more frequent updates. Recommended cadence guidelines ensure accountability while monitoring progress toward de-escalation or resolution.

Can I use this escalation framework for security incidents and SLA breaches?▼

Yes, this escalation framework supports security incidents, SLA breaches, outages, and high-value customer complaints. It provides severity guidelines and structured templates applicable across customer support, technical support, and product teams handling diverse incident types.

Related Skills

Explore More Product & Management Skills→
kiryteokiryteo
1

escalation

Create structured escalation briefs with impact and reproduction steps.

Community
Advanced
EpiphyticEpiphytic
7

escalation

Structure customer support issues into actionable escalation briefs.

Official
Advanced
propane-aipropane-ai
4

escalation

Structure support escalations with context, reproduction steps, and business impact.

Official
Intermediate
JaviMontanoJaviMontano

metodologia-incident-management

Design incident response processes with severity, escalation, and postmortem templates.

Community
Advanced