posthog-incident-runbook
PostHog incident response: triage decision tree, immediate actions for 401/429/500 errors, graceful degradation, evidence collection, and postmortem. "posthog on-call", "posthog emergency", "posthog broken production". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill posthog-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.
# PostHog Incident Runbook ## Overview Rapid incident response for PostHog integration failures. PostHog Cloud has its own status page (status.posthog.com) — the first step is always determining whether the issue is PostHog-side or your integration. ## Severity Levels | Level | Definition | Response Time | Examples | |-------|------------|---------------|----------| | P1 | Analytics completely down | < 15 min | All capture calls failing, feature flags returning defaults | | P2 | Degraded analytics | < 1 hour | High latency, partial event loss, slow flag eval | | P3 | Minor impact | < 4 hours | Webhook delays, specific event type missing | | P4 | No user impact | Next day | Monitoring gaps, dashboard stale data | ## Quick Triage (Run First) ```bash set -euo pipefail echo "=== PostHog Triage ===" echo "" # 1. Is PostHog Cloud up? echo -n "PostHog US Cloud: " curl -sf -o /dev/null -w "%{http_code}" https://us.i.posthog.com/healthz || echo "UNREACHABLE" echo "" # 2. Can we capture events? echo -n "Event capture: " curl -sf -o /dev/null -w "%{http_code}" -X POST 'https://us.i.posthog.com/capture/' \ -H 'Content-Type: application/json' \ -d "{\"api_key\":\"${NEXT_PUBLIC_POSTHOG_KEY}\",\"
- Overview
- Severity Levels
- Quick Triage (Run First)
- Decision Tree
- Immediate Actions by Error Type
- 401/403 — Authentication Failed
- 429 — Rate Limited
- Events Not Appearing
- Feature Flags Returning Defaults
- Graceful Degradation Pattern
- Post-Incident Evidence Collection
- Error Handling
- Output
- Resources
set -euo pipefail
echo "=== PostHog Triage ==="
echo ""
echo -n "PostHog US Cloud: "
curl -sf -o /dev/null -w "%{http_code}" https://us.i.posthog.com/healthz || echo "UNREACHABLE"
echo -n "Event capture: "
curl -sf -o /dev/null -w "%{http_code}" -X POST 'https://us.i.posthog.com/capture/' \
echo -n "Flag evaluation: "
curl -sf -o /dev/null -w "%{http_code}" -X POST 'https://us.i.posthog.com/decide/?v=3' \
if [ -n "${POSTHOG_PERSONAL_API_KEY:-}" ]; thenWhat does the posthog-incident-runbook skill do?
PostHog incident response: triage decision tree, immediate actions for 401/429/500 errors, graceful degradation, evidence collection, and postmortem. "posthog on-call", "posthog emergency", "posthog broken production". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill posthog-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.