Agent skill · operations · jeremylongshore
sentry-incident-runbook
Execute incident response procedures using Sentry error monitoring.
Why this skill is useful
Provides a structured incident response framework with specific Sentry API commands and severity classification criteria that the AI wouldn't reliably generate on its own.
What it needs
Requires sentry account access. About 8k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Incident Runbook Overview Structured incident response framework built on Sentry's error monitoring platform. Covers the full lifecycle from alert detection through severity classification, root cause investigation using Sentry's breadcrumbs and stack traces, Discover queries for impact analysis, stakeholder communication, resolution via the Sentry API, and postmortem documentation with Sentry data exports. Prerequisites Sentry account with project-level access and auth token (SENTRYAUTHTOKEN) Organization slug (SENTRYORG) and project slug (SENTRYPROJECT) configured @sentry/node (v8+) or equivalent SDK installed in the application Alert rules configured for critical error thresholds Notification channels connected (Slack integration or PagerDuty) Instructions Step 1 — Classify Severity Assign a severity level based on error frequency and user impact. This determines response time and escalation path. Severity Error Criteria User Impact Response Time Escalation ---------- --------------- ------------- --------------- ------------ P0 — Critical Crash-free rate below 95% or unhandled exception spike >500/min Core flow blocked for all users, data loss risk 15 minutes PagerDuty page to on-call engineer P1 — Major New issue affecting >100 unique users per hour Key feature degraded, no workaround 1 hour Slack #incidents channel, tag team lead P2 — Minor New issue affecting <100 unique users per hour Feature degraded but workaround exists Same business day Slack #alerts-production P3 — Low Edge case, cosmetic error, staging-only issue Minimal or no user-facing impact Next sprint Add to backlog, assign owner Decision logic for classification: Step 2 — Triage and Investigate Execute this checklist within the first 15 minutes of a P0/P1 alert. Initial triage (Sentry UI): 1. Open the Sentry issue link from the alert notification 2. Check the error frequency graph — determine if the rate is spiking, steady, or declining 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-incident-runbook