vercel-incident-runbook
Execute Vercel incident response procedures with triage, mitigation, and postmortem.Use when responding to Vercel-related outages, investigating errors,or running post-incident reviews for Vercel integration failures.Trigger with phrases like "vercel incident", "vercel outage","vercel down", "vercel on-call", "vercel emergency", "vercel broken".
When & Why to Use This Skill
The Vercel Incident Runbook skill is a specialized tool designed for DevOps and SRE teams to streamline the management of Vercel-related outages and integration failures. It provides a structured, automated framework for rapid triage, mitigation, and postmortem analysis, leveraging integrated tools like kubectl and curl to reduce Mean Time to Recovery (MTTR) and ensure high availability for web applications.
Use Cases
- 1. Real-time Outage Mitigation: Quickly identify whether a service disruption originates from Vercel's infrastructure or internal configurations using automated triage commands.
- 2. On-call Emergency Support: Assist on-call engineers by providing a standardized decision tree and remediation steps to handle 'vercel down' or 'vercel broken' scenarios efficiently.
- 3. Post-Incident Analysis: Automatically gather evidence and logs from Vercel and production clusters to generate comprehensive postmortem reports and prevent future integration failures.
| name | vercel-incident-runbook |
|---|---|
| description | | |
| allowed-tools | Read, Grep, Bash(kubectl:*), Bash(curl:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Vercel Incident Runbook
Prerequisites
- Access to Vercel dashboard and status page
- kubectl access to production cluster
- Prometheus/Grafana access
- Communication channels (Slack, PagerDuty)
Instructions
Step 1: Quick Triage
Run the triage commands to identify the issue source.
Step 2: Follow Decision Tree
Determine if the issue is Vercel-side or internal.
Step 3: Execute Immediate Actions
Apply the appropriate remediation for the error type.
Step 4: Communicate Status
Update internal and external stakeholders.
Output
- Issue identified and categorized
- Remediation applied
- Stakeholders notified
- Evidence collected for postmortem
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.