escalation-summary SKILL.md skillA
escalation-summary from skillmedev/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add skillmedev/skills/escalation-summary@git:20261005.bea4ea5Pins git:20261005.bea4ea5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- skillmedev/skills
- Path
skills/escalation-summary/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261005.bea4ea5, committed Oct 5, 2026
- First version recorded
- Jul 5, 2026
- Size
- 6,529 bytes
- Repository stars
- 19
- License
- MIT
Writes a tight escalation summary to engineering or management with a one-line headline, quantified customer impact, repro steps, prior attempts, and a single clear ask. Use when someone says "I need to escalate this ticket", "write this up for engineering", "this bug needs eng eyes", or a support issue must leave the queue for specialist action. Do NOT use for replying to the customer - use support-ticket-reply instead; do NOT use for assigning incident severity and coordinating an active…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Escalation Summary Engineers and managers receive escalations all day; a well-built summary gets a response, a vague one gets queued behind everything else. The costly mistake this skill prevents is the partial escalation - sent early with "details to follow" - which burns the escalation team's first look and resets the clock on the customer. Write as if the reader has zero context and thirty seconds: if the first line does not tell them what is broken, for whom, and since when, the rest never gets read. ## Operating procedure Order matters: qualify before gathering, gather before writing - an escalation written before the evidence exists gets bounced back for the missing pieces. 1. Qualify the escalation. Confirm the issue is genuinely outside support's scope to resolve. If a documented workaround or known fix exists, apply it instead of escalating. 2. Gather the inputs below completely. Do not start writing until everything is in hand. 3. Assign severity using the definitions below and put the label in the subject line or ticket title. …
Read the whole file at its exact version.
How to install
mdr add skillmedev/skills/escalation-summary@sha256:e1eaf5cf99e2ef5eThe line at the top of this page pins the label git:20261005.bea4ea5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cf6ooojpdroz7a4x)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 5, 2026 and Oct 5, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.bea4ea5 latest | 2026-10-05 | bea4ea5 | 6,529 B | A | view · diff |
| git:20260705.a28c4ce | 2026-07-05 | a28c4ce | 6,489 B | A | view · diff |
| git:20260705.acb5571 | 2026-07-05 | acb5571 | 6,535 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6529 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
skillmedev/skills · 19 stars · license MIT · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cf6ooojpdroz7a4x GET https://markdownregistry.com/api/v1/resolve?ref=skillmedev/skills/escalation-summary GET https://markdownregistry.com/api/v1/blob/e1eaf5cf99e2ef5ed5326c5c5dbfcef41943dc762c9bde976419d2d8d647aaa8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from skillmedev/skills
Every file in skillmedev/skills