supabase-incident-runbook
Execute Supabase incident response procedures with triage, mitigation, and postmortem. Use when responding to Supabase-related outages, investigating errors, or running post-incident reviews for Supabase integration failures. Trigger with phrases like "supabase incident", "supabase outage", "supabase down", "supabase on-call", "supabase emergency", "supabase broken".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- supabase-incident-runbook
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Execute Supabase incident response procedures with triage, mitigation, and postmortem. Use when responding to Supabase-related outages, investigating errors, or running post-incident reviews for Supabase integration failures. Trigger with phrases like "supabase incident", "supabase outage", "supabase down", "supabase on-call", "supabase emergency", "supabase broken".
- allowed-tools
- Read, Grep, Bash(kubectl:*), Bash(curl:*)
- compatible-with
- claude-code, codex, openclaw
02 资源文件 3
- 参考文档references/errors.md331 B
- 参考文档references/examples.md142 B
- 参考文档references/immediate-actions-by-error-type.md1008 B
03 SKILL.md 正文
Supabase Incident Runbook
Prerequisites
- Access to Supabase dashboard and status page
- kubectl access to production cluster
- Prometheus/Grafana access
- Communication channels (Slack, PagerDuty)
Instructions
Incident response for Supabase integrations requires distinguishing quickly between platform-side outages (check status.supabase.com) and issues in your own integration code or infrastructure. Misattributing a platform outage as an internal bug wastes critical time during an incident. Always verify the Supabase status page before investing engineering effort in local remediation.
Step 1: Quick Triage
Run the triage commands to identify the issue source. Check Supabase status page, verify your API credentials have not expired, and run a minimal health check query against your Supabase instance. Compare error rates against your baseline metrics to understand the scope and onset time.
Step 2: Follow Decision Tree
Determine if the issue is Supabase-side or internal. Platform outages require monitoring the status page and communicating degraded service to users. Internal issues require examining your application logs, recent deployments, and configuration changes for the root cause.
Step 3: Execute Immediate Actions
Apply the appropriate remediation for the error type. For connection failures, enable circuit breakers and fallback responses. For data inconsistencies, pause write operations to prevent further corruption while you investigate.
Step 4: Communicate Status
Update internal and external stakeholders. Provide clear, jargon-free status updates at regular intervals. Avoid speculation about root cause until confirmed by investigation.
Output
- Issue identified and categorized as platform-side or internal
- Remediation applied with evidence of restored service
- Stakeholders notified with timeline and impact summary
- Evidence collected for postmortem including timeline and root cause
Error Handling
See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
Examples
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Resources
Overview
Execute Supabase incident response procedures with triage, mitigation, and postmortem.
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.