When should I use the Escalation skill?

Use this skill when a customer issue requires specialized technical intervention, code changes, infrastructure investigation, or high-level business decisions that go beyond standard support capabilities.

How does it help engineering teams specifically?

It provides engineers with standardized reproduction steps, specific environment details, and quantified impact, significantly reducing the diagnostic time and communication overhead needed to fix bugs.

Does this skill support security incident reporting?

Yes, it includes a dedicated protocol for security escalations that bypasses normal tier progression to ensure immediate containment and notification of the security team.

What is included in a structured escalation brief?

A standard brief includes a severity assessment, impact dimensions (revenue and SLA), detailed reproduction steps, internal actions already attempted, and a specific 'ask' with a deadline.

Support Escalation & Incident Briefs

Name: Support Escalation & Incident Briefs
Author: lilbom32

bylilbom32

0•

협업 도구

Standardizes the customer support escalation process by generating comprehensive briefs with technical context and business impact.

This skill empowers support teams to bridge the gap between customer service and technical departments by providing a structured framework for escalating complex issues. It guides users through determining when an escalation is necessary, categorizing the issue into appropriate tiers—such as Engineering, Product, Security, or Leadership—and generating detailed briefs. By including standardized reproduction steps, environment details, and quantified business impact, it ensures that receiving teams have the exact information needed to prioritize and resolve issues without unnecessary back-and-forth communication.

주요 기능

010 GitHub stars

02Tiered routing logic for Engineering, Product, Security, and Leadership

03Structured escalation brief generation with technical and business context

04Standardized bug reproduction step formatting for engineering clarity

05Defined follow-up cadences and de-escalation protocols

06Quantified business impact assessment (Revenue, SLA, Reputation)

사용 사례

01Drafting an executive summary for high-priority SLA breaches or major account risks

02Converting a complex support ticket into a technical bug report for engineering teams

03Assessing whether a recurring customer pain point warrants a formal product feature request

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lilbom32/ketnoitrithuc escalation

For use in Claude.ai and ChatGPT