webflow-incident-runbook
Execute Webflow incident response \u2014 triage by HTTP status (401/403/429/500),\n\ circuit breaker activation, cached fallback, Webflow status page checks,\ncommunication\ \ templates, and postmortem process.\nTrigger with phrases like \"webflow incident\"\ , \"webflow outage\",\n\"webflow down\", \"webflow on-call\", \"webflow emergency\"\ , \"webflow broken\".\n"
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill webflow-incident-runbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Webflow Incident Runbook ## Overview Rapid incident response procedures for Webflow Data API v2 integration failures. Covers triage, immediate remediation by error type, graceful degradation, stakeholder communication, and postmortem. ## Prerequisites - Access to Webflow dashboard and status page - Application logs and metrics access - Communication channels (Slack, PagerDuty) - Cached fallback data available ## Severity Levels | Level | Definition | Response Time | Example | |-------|------------|---------------|---------| | P1 | Integration fully down | < 15 min | All API calls returning 401/500 | | P2 | Degraded service | < 1 hour | High 429 rate, elevated latency | | P3 | Minor impact | < 4 hours | Webhook delays, form sync lag | | P4 | No user impact | Next business day | Monitoring gap, stale cache | ## Quick Triage (Run First) ```bash #!/bin/bash echo "=== Webflow Incident Triage ===" echo "Time: $(date -u)" # 1. Webflow platform status echo "" echo "--- Platform Status ---" curl -s https://status.webflow.com/api/v2/status.json 2>/dev/null | \ python3 -c " import sys,json d=json.load(sys.stdin) print(f'Status: {d[\"status\"][\"description\"]}') for c in d.get('components',
- Overview
- Prerequisites
- Severity Levels
- Quick Triage (Run First)
- Decision Tree
- Immediate Actions by Error Type
- 401/403 — Authentication Failure (P1)
- 429 — Rate Limited (P2)
- 500/502/503 — Webflow Server Error (P2)
- Webhook Delivery Failure (P3)
- Communication Templates
- Internal (Slack)
- External (Status Page)
- Post-Incident
echo "=== Webflow Incident Triage ==="
echo "Time: $(date -u)"
echo ""
echo "--- Platform Status ---"
curl -s https://status.webflow.com/api/v2/status.json 2>/dev/null | \
python3 -c "
import sys,json
for c in d.get('components',[]):
if c['status'] != 'operational':
echo "--- API Connectivity ---"What does the webflow-incident-runbook skill do?
Execute Webflow incident response \u2014 triage by HTTP status (401/403/429/500),\n\ circuit breaker activation, cached fallback, Webflow status page checks,\ncommunication\ \ templates, and postmortem process.\nTrigger with phrases like \"webflow incident\"\ , \"webflow outage\",\n\"webflow down\", \"webflow on-call\", \"webflow emergency\"\ , \"webflow broken\".\n"
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill webflow-incident-runbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.