Home / calle-ai / awesome-phone-call-agents · GitHub

incident-escalation-call SKILL.md skillA

incident-escalation-call from calle-ai/awesome-phone-call-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add calle-ai/awesome-phone-call-agents/incident-escalation-call@git:20260914.ef4f442

Pins git:20260914.ef4f442 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: calle-ai/awesome-phone-call-agents
Path: skills/incident-escalation-call/SKILL.md
Versions recorded: 2
Latest version: git:20260914.ef4f442, committed Sep 14, 2026
First version recorded: Aug 25, 2026
Size: 5,961 bytes
Repository stars: 112
License: MIT

Escalate a production incident by phone until a person commits to owning it. Places one CALL-E call per on-call engineer in ladder order, requires a spoken owner and an ETA, then verifies the acknowledgement over a second transport before reporting it. Use when a page must end with a human on the hook, not a notification marked as sent.

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

# Incident Escalation Call

Use this skill when an incident needs a human owner and "notification sent" is
not evidence that anybody heard it.

It does not invent an escalation mechanism. It drives the runnable
[`ringdown`](../../apps/python/ringdown/) app, which resolves who is on call
right now, places one CALL-E call per person in ladder order, accepts only a
commitment with an owner and an ETA, re-derives that acknowledgement from the
raw transcript over MCP — a second transport the writing path never touched —
and returns an exit code plus a hash-chained ledger.

## When to use

- A monitoring alert, a failed deploy or a user-facing outage needs a named
  owner with a spoken commitment, and the on-call rotation is defined.
- The on-call engineer is asleep or away from a keyboard, which is exactly when
  a phone call beats a push notification, an email or a chat message.
- The user asked to page, escalate or wake up whoever is on call.

## When not to use

- The user is the on-call engineer and is already in this conversation. Tell
  them here.
- You do not have a rotation file with enrolled contacts in E.164 form and
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add calle-ai/awesome-phone-call-agents/incident-escalation-call@sha256:aa77fff9ad7842c7

The line at the top of this page pins the label git:20260914.ef4f442, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_32updgs7m3bez7ii.svg)](https://markdownregistry.com/a/art_32updgs7m3bez7ii)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Aug 25, 2026 and Sep 14, 2026, about one every 20 days.

version	committed	commit	size	audit
git:20260914.ef4f442 latest	2026-09-14	ef4f442	5,961 B	A	view · diff
git:20260825.257ed6f	2026-08-25	257ed6f	5,667 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5961 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

GitHub

calle-ai/awesome-phone-call-agents · 112 stars · license MIT · pushed 2026-11-05 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_32updgs7m3bez7ii
GET https://markdownregistry.com/api/v1/resolve?ref=calle-ai/awesome-phone-call-agents/incident-escalation-call
GET https://markdownregistry.com/api/v1/blob/aa77fff9ad7842c7a6efb3ab469b9388cf093ed1dcde7e91928bb91503c16346

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.