AgentSkillsCN

vercel-incident-runbook

按照分类、缓解与事后分析的流程，执行 Vercel 事件响应程序。 在应对 Vercel 相关的停机事件、调查错误，或就 Vercel 集成失败展开事后复盘时使用。 可使用诸如“Vercel 事件”、“Vercel 停机”、“Vercel 下线”、“Vercel 值班”、“Vercel 紧急情况”、“Vercel 故障”等短语来触发相关操作。

SKILL.md
--- frontmatter
name: vercel-incident-runbook
description: |
  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".
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.

Resources