Agent skill · marketing growth · jeremylongshore
clickup-incident-runbook
Triage, contain, recover, and review ClickUp API and webhook incidents with bounded read-only evidence. Use when ClickUp-backed production behavior is degraded. Trigger with "ClickUp incident", "ClickUp outage", or "ClickUp webhook failing".
Why this skill is useful
Adds executable scripts for rapid incident response to ClickUp API failures that are not publicly documented.
What it needs
Requires bash installed locally. Requires clickup account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ClickUp Integration Incident Response Overview Separate provider health, credential scope, rate exhaustion, webhook suspension, data drift, and application faults before taking recovery action. Prerequisites An incident commander, severity model, affected service/Workspace inventory, and communication channel Read-only diagnostic capability plus audited break-glass procedures Known last-good deployment, queue checkpoints, and rollback targets Tool Discipline Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode. Current Contract ClickUp status, API reachability, tenant authorization, and application side effects are independent signals. A webhook is failing after unsuccessful or over-seven-second responses; failed events are not resent after their delivery attempts. At failcount=100 a webhook is suspended; returning 401 suspends it immediately. 429 recovery follows the per-token reset header rather than a guessed delay. Authentication Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret. Instructions 1. Declare scope, commander, severity, affected Workspaces, write freeze, and evidence-retention boundary. 2. Check provider status and run metadata-only identity/rate probes. 3. Classify auth, plan/permission, rate, webhook health, schema, queue, deployment, or data-consistency failure. 4. Contain with write disablement, circuit breaking, queue pause, or rollback before rotating credentials. 5. Recover one lane at a time and reconcile missed or duplicate business operations from durable records. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-incident-runbook