Agent skill

Clickup Incident Runbook

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Triage, contain, recover, and review ClickUp API and webhook incidents with bounded read-only evidence.

MITAuto-check passedDevOps & Cloud

Install Clickup Incident Runbook

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-incident-runbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace clickup-incident-runbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/clickup-incident-runbook .claude/skills/clickup-incident-runbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clickup-incident-runbook
GitHub stars
2.8k
Token cost
~1k tokens
SKILL.md length
390 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Triage, contain, recover, and review ClickUp API and webhook incidents with bounded read-only evidence.

  • Works in 6 steps: Declare scope, commander, severity,… → Check provider status and run… → Classify auth, plan/permission, rate,… → …
  • ClickUp-backed production behavior is degraded
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Clickup Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live response requires authorized operational access and an incident commander

It sits in DevOps & Cloud, covering Incident response, Runbooks and postmortems and Webhooks. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • ClickUp-backed production behavior is degraded
  • With ClickUp incident
  • ClickUp webhook failing

Example prompts

  • “ClickUp incident”
  • “ClickUp outage”
  • “ClickUp webhook failing”
  • “/clickup-incident-runbook”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; live response requires authorized operational access and an incident commander
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  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. Close only after verification, stakeholder communication, evidence capture, and assigned follow-up.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • developer.clickup.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; live response requires authorized operational access and an incident commander

    From compatibility in the SKILL.md frontmatter.

Context cost

Clickup Incident Runbook loads about 1k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 390 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 390 words, ~1,034 tokens.

Download SKILL.mdSave it as .claude/skills/clickup-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
clickup-incident-runbook
description
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".
allowed-tools
Read, Glob, Grep, WebFetch, Write, Edit
compatibility
Designed for Claude Code; live response requires authorized operational access and an incident commander
argument-hint
[incident-id] [severity]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, clickup, incident-response
model
inherit
effort
high

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 fail_count=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. Close only after verification, stakeholder communication, evidence capture, and assigned follow-up.
Show full SKILL.md (121 more words)Show less

Approval Boundaries

Do not rotate shared tokens, reactivate webhooks, replay queues, mutate tasks, or suppress evidence without commander and owner approval.

Output

Return timeline, failure class, containment, affected Workspaces/operations, recovery evidence, reconciliation result, and follow-up owners. Include unresolved risk and the next decision deadline.

Error Handling

ConditionResponse
Evidence includes work contentRedact or quarantine before sharing.
Webhook events were droppedReconcile from source-of-truth reads; do not assume ClickUp will resend them.
Credential ownership is unknownFreeze writes and escalate before rotation.
Recovery increases error rateReturn to containment and roll back.

Examples

The example below is a redacted operator receipt; it contains no task text, member data, credential, or webhook secret.

text
incident=CU-207; provider=healthy; class=webhook-suspended; writes=frozen; reconcile=required; commander=assigned

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/clickup-incident-runbook of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Clickup Incident Runbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clickup Incident Runbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clickup Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1kAutomated safety check: PassMIT
Oncallpigweed-project/pigweed548—~963Automated safety check: PassApache-2.0
Activation Governance Chaos RolloutAli-Marandi/DataSense107—~1.9kAutomated safety check: PassMIT
Incident Response686f6c61/alfred-dev117—~1.1kAutomated safety check: PassMIT
Superset Incident Triagesuperset-sh/superset15k—~1kAutomated safety check: PassCustom licence
Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan109—~1.9kAutomated safety check: PassMIT

Similar skills

  • Oncall

    pigweed-project/pigweed

    Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).

    548 GitHub stars~963 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Design, validate, and govern fail-closed customer-activation automations that use an Outbox/worker pattern.

    107 GitHub stars~1.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Incident Response

    686f6c61/alfred-dev

    Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem.

    117 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Superset Incident Triage

    superset-sh/superset

    Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.

    15k GitHub stars~1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Post-Incident Debrief

    VeryGoodOpenSource/vgv-wingspan

    Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.

    109 GitHub stars~1.9k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • SRE Engineer

    Jeffallan/claude-skills

    Defines SLIs, SLOs and error budgets, and sets up golden-signal monitoring, blameless postmortems, toil automation and chaos experiments for production systems.

    12k GitHub stars~1.7k tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Clickup Incident Runbook

What does Clickup Incident Runbook do?

Triage, contain, recover, and review ClickUp API and webhook incidents with bounded read-only evidence. Clickup Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Triage, contain, recover, and review ClickUp API and webhook incidents with bounded read-only evidence.

When should I use Clickup Incident Runbook?

Clickup Incident Runbook fits situations like: clickUp-backed production behavior is degraded; with ClickUp incident; clickUp webhook failing.

How do I install Clickup Incident Runbook in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-incident-runbook -a claude-code`. Or copy the skill folder (skills/.curated/clickup-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/clickup-incident-runbook in your project. Claude Code loads it when a task matches its description.

How do I install Clickup Incident Runbook in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-incident-runbook -a codex`. Or copy the skill folder (skills/.curated/clickup-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/clickup-incident-runbook in your project. Codex loads it when a task matches its description.

Can I use Clickup Incident Runbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-incident-runbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clickup-incident-runbook, .gemini/skills/clickup-incident-runbook, .github/skills/clickup-incident-runbook and .opencode/skills/clickup-incident-runbook in your project.

What does Clickup Incident Runbook need to run?

SKILL.md names no scripts, command-line tools or credentials: Clickup Incident Runbook is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live response requires authorized operational access and an incident commander.

Does Clickup Incident Runbook access the network?

SKILL.md names 1 domain. As links in the text: developer.clickup.com. This is read from the text; nothing was executed.

Is Clickup Incident Runbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clickup Incident Runbook use?

Clickup Incident Runbook is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clickup Incident Runbook use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 584 tokens, read only when the agent opens those files.

What are the alternatives to Clickup Incident Runbook?

Skills that share tags, products or a category with Clickup Incident Runbook: Oncall (pigweed-project/pigweed, 548 stars), Activation Governance Chaos Rollout (Ali-Marandi/DataSense, 107 stars), Incident Response (686f6c61/alfred-dev, 117 stars) and Superset Incident Triage (superset-sh/superset, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clickup Incident Runbook?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.