Agent skill · security · jeremylongshore
clerk-incident-runbook
Manage incident response for Clerk authentication issues.
Why this skill is useful
Provides specific emergency scripts and procedures for handling Clerk authentication incidents that the AI wouldn't reliably generate on its own.
What it needs
Requires bash, curl, python3 installed locally. Requires clerk account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clerk Incident Runbook Overview Procedures for responding to Clerk-related incidents in production. Covers triage, emergency auth bypass, recovery scripts, and post-incident review. Prerequisites Access to Clerk Dashboard (dashboard.clerk.com) Access to application logs and monitoring Emergency contact list for on-call team Rollback procedures documented Instructions Step 1: Triage — Identify Incident Category Category Symptoms Severity ---------- ---------- ---------- Clerk outage status.clerk.com shows incident, all auth fails Critical Key compromise Unauthorized access detected Critical Middleware failure All routes return 500 High Session issues Users randomly logged out Medium Webhook backlog User sync falling behind Low Quick diagnostic: Step 2: Emergency Auth Bypass (Clerk Outage Only) Activate bypass: Step 3: Key Rotation (Compromised Secret Key) Step 4: Session Recovery (Mass Logout Fix) Step 5: Webhook Replay (Missed Events) Step 6: Post-Incident Review Template Output Triage script identifying incident category and severity Emergency auth bypass middleware (activate via env var) Key rotation procedure for compromised credentials Session revocation endpoint for mass-logout recovery Post-incident review template Error Handling Scenario Response ---------- ---------- Clerk API completely down Activate emergency bypass, monitor status.clerk.com Secret key compromised Rotate keys immediately, revoke all sessions, audit logs Middleware 500 errors Check middleware.ts syntax, verify Clerk SDK version Webhook delivery failures Retry from Dashboard, check endpoint accessibility Users randomly logged out Check session lifetime settings, verify domain config Examples Quick Status Check One-Liner Resources Clerk Status Page Clerk Support Clerk Discord Next Steps After resolving incident, review clerk-observability for improved monitoring.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clerk-incident-runbook--a2144c