clickup-incident-runbook
Execute ClickUp API incident response: triage, diagnosis, mitigation, and postmortem for API failures and integration outages. "clickup on-call", "clickup emergency", "clickup API broken". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-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.
# ClickUp Incident Runbook ## Overview Rapid incident response for ClickUp API v2 integration failures. Covers triage, diagnosis by error type, mitigation, and postmortem. ## Severity Classification | Level | Definition | Response Time | Example | |-------|-----------|---------------|---------| | P1 | All ClickUp API calls failing | < 15 min | 401 on all requests, API unreachable | | P2 | Degraded
What does the clickup-incident-runbook skill do?
Execute ClickUp API incident response: triage, diagnosis, mitigation, and postmortem for API failures and integration outages. "clickup on-call", "clickup emergency", "clickup API broken". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill clickup-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,596 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.