Agent skill · marketing growth · jeremylongshore
anth-incident-runbook
Execute incident response procedures for Claude API outages and degradation.
Why this skill is useful
Adds executable scripts for incident response procedures specific to the Claude API that are not publicly documented.
What it needs
Requires curl, python3 installed locally. Requires anthropic account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Anthropic Incident Runbook Severity Classification Severity Condition Response Time ---------- ----------- --------------- P1 API returning 500/529 for all requests Immediate P2 Rate limiting (429) or high latency (>10s p99) 15 minutes P3 Intermittent errors (<5% error rate) 1 hour P4 Degraded quality (not errors) Next business day Immediate Triage (First 5 Minutes) Decision Tree Mitigation Actions Rate Limiting (429) API Outage (500/529) Key Compromise Postmortem Template Error Handling Symptom Likely Cause Quick Fix --------- ------------- ----------- All requests fail 401 Key rotated/expired Check Console for active keys Sudden 429 spike Traffic burst or tier change Check rate limit headers Slow responses (>10s) Large maxtokens or complex prompt Reduce maxtokens, use Haiku Intermittent 500s Upstream API issue Check status.anthropic.com Overview This runbook provides a bounded, evidence-driven response to Claude API outages, throttling, latency, key compromise, and degraded behavior. It separates provider diagnosis from application containment and requires a reversible change for every mitigation. Prerequisites Maintain on-call ownership, escalation contacts, status-page access, a sandbox health probe, circuit-breaker/fallback controls, and a tested rollback path. Keep environment-specific keys in a secret manager with least privilege and documented revocation authority. Do not place credentials in incident chat or tickets. Configure redacted telemetry for status class, request ID, model class, latency, rate-limit headers, aggregate impact, and change history; exclude prompts, completions, PII, tool arguments, and key material. Instructions 1. Declare severity from observed scope, record a correlation ID, and verify the issue with a synthetic sandbox probe before changing production traffic. 2. Check provider status, request IDs, rate-limit metadata, application error/latency aggregates, and recent deploys. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/anth-incident-runbook