Manage incident response for Clerk authentication issues. Use when handling auth outages, security incidents, or production authentication problems. Trigger with phrases like "clerk incident", "clerk outage", "clerk down", "auth not working", "clerk emergency".
Procedures for responding to Clerk-related incidents in production.
For full implementation details and code examples, load:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
| Error | Cause | Resolution |
|---|---|---|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with security |
| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
Basic usage: Apply clerk incident runbook to a standard project setup with default configuration options.
Advanced scenario: Customize clerk incident runbook for production environments with multiple constraints and team-specific requirements.43:["$","$L4b",null,{"content":"$4c","frontMatter":{"name":"clerk-incident-runbook","description":"Manage incident response for Clerk authentication issues.\nUse when handling auth outages, security incidents,\nor production authentication problems.\nTrigger with phrases like "clerk incident", "clerk outage",\n"clerk down", "auth not working", "clerk emergency".\n","allowed-tools":"Read, Write, Edit, Bash(npm:), Bash(curl:), Grep","version":"1.0.0","license":"MIT","author":"Jeremy Longshore [email protected]","compatible-with":"claude-code, codex, openclaw"}}]