Agent skill · operations · jeremylongshore
deepgram-incident-runbook
Execute Deepgram incident response procedures for production issues.
Why this skill is useful
Adds an executable triage script and incident response procedures specifically for Deepgram outages that are not publicly documented.
What it needs
Requires curl installed locally. Requires deepgram account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Deepgram Incident Runbook Prerequisites An incident ID, commander, affected service/environment, escalation route, and authorized redacted diagnostic access. A data/consent owner and documented safe mitigation or rollback action. Examples For elevated transcription errors, declare scope, capture aggregate health and redacted correlation IDs, stabilize with the documented circuit-breaker/rollback, and verify recovery against the SLO. Escalate provider or data-impact incidents through the approved path; do not attach customer audio, transcripts, or credentials to the incident channel. Overview Standardized incident response for Deepgram-related production issues. Includes automated triage script, severity classification (SEV1-SEV4), immediate mitigation actions, fallback activation, and post-incident review template. Quick Reference Resource URL ---------- ----- Deepgram Status https://status.deepgram.com Deepgram Console https://console.deepgram.com Support Email support@deepgram.com Community https://github.com/orgs/deepgram/discussions Severity Classification Level Definition Response Time Example ------- ------------ --------------- --------- SEV1 Complete outage, all transcriptions failing Immediate 100% 5xx errors SEV2 Major degradation, >50% error rate < 15 min Specific model failing SEV3 Minor degradation, elevated latency < 1 hour P95 > 30s SEV4 Single feature affected, cosmetic < 24 hours Diarization inaccurate Instructions Step 1: Automated Triage (First 5 Minutes) Step 2: SEV1 Response (Complete Outage) Step 3: SEV2 Response (Partial Degradation) Step 4: SEV3/SEV4 Mitigation Step 5: Post-Incident Review Template Step 6: Escalation Matrix Level Contact When ------- --------- ------ L1 On-call engineer Alert fires L2 Team lead 15 min without resolution L3 Deepgram support (support@deepgram.com) Confirmed Deepgram-side issue L4 Engineering director SEV1 > 1 hour Output Automated triage script (bash, runs in <30s) SEV1 fallback service with request queue and r …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/deepgram-incident-runbook--c4431e