Agent skill

Klaviyo Incident Runbook

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

Execute Klaviyo incident response procedures with triage, mitigation, and postmortem.

MITAuto-check passedDevOps & Cloud

Install Klaviyo Incident Runbook

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace klaviyo-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/klaviyo-incident-runbook .claude/skills/klaviyo-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
klaviyo-incident-runbook
GitHub stars
2.8k
Token cost
~1.5k tokens
SKILL.md length
561 words
Files
4 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Execute Klaviyo incident response procedures with triage, mitigation, and postmortem.

  • Works in 5 steps: Triage immediately. Run the quick-triage… → Classify the failure. Walk the decision… → Assign a severity from the table above… → …
  • Responding to Klaviyo-related outages
  • SKILL.md covers Overview, Prerequisites, Severity Levels and Instructions, plus 4 more sections
  • Calls curl and python3; reaches status.klaviyo.com and a.klaviyo.com; needs KLAVIYO_PRIVATE_KEY

What it does

Klaviyo Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute Klaviyo incident response procedures with triage, mitigation, and postmortem. Use when responding to Klaviyo-related outages, investigating API errors (401/403/429/5xx), or running post-incident reviews for Klaviyo integration failures on an on-call rotation. Trigger with phrases like "klaviyo incident", "klaviyo outage", "klaviyo down", "klaviyo on-call", "klaviyo emergency", "klaviyo broken".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/communication-and-postmortem.md`, `references/remediation.md` and `references/triage.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Incident response, Email marketing and Runbooks and postmortems. 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

  • Responding to Klaviyo-related outages
  • Investigating API errors (401/403/429/5xx)
  • Running post-incident reviews for Klaviyo integration failures on an on-call rotation
  • With phrases like klaviyo incident

Example prompts

  • “klaviyo incident”
  • “klaviyo outage”
  • “klaviyo down”
  • “/klaviyo-incident-runbook”

Requirements

  • Python 3
  • A credential in KLAVIYO_PRIVATE_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Bash(curl:*), Bash(kubectl:*), Bash(npm:*)

Workflow steps

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

  1. Triage immediately. Run the quick-triage script to answer the four
  2. Classify the failure. Walk the decision tree in
  3. Assign a severity from the table above and set the response-time clock.
  4. Apply the remediation for the observed error type — auth failure (401),
  5. Communicate and write the postmortem. Post the internal + external

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
    • Bash(curl:*)
    • Bash(kubectl:*)
    • Bash(npm:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • python3

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • status.klaviyo.com
    • a.klaviyo.com

    Also links to:

    • klaviyo.com
    • developers.klaviyo.com

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • KLAVIYO_PRIVATE_KEY

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

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Klaviyo Incident Runbook loads about 1.5k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 108 tokens; SKILL.md has 561 words of instructions outside code blocks.

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

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). 561 words, ~1,480 tokens.

Download SKILL.mdSave it as .claude/skills/klaviyo-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
klaviyo-incident-runbook
description
Execute Klaviyo incident response procedures with triage, mitigation, and postmortem. Use when responding to Klaviyo-related outages, investigating API errors (401/403/429/5xx), or running post-incident reviews for Klaviyo integration failures on an on-call rotation. Trigger with phrases like "klaviyo incident", "klaviyo outage", "klaviyo down", "klaviyo on-call", "klaviyo emergency", "klaviyo broken".
allowed-tools
Read, Bash(curl:*), Bash(kubectl:*), Bash(npm:*)
compatibility
Designed for Claude Code
version
1.7.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, klaviyo, email-marketing, cdp

Klaviyo Incident Runbook

Overview

Rapid incident response for Klaviyo API outages and integration failures: quick triage, decision trees, mitigation steps, and postmortem templates. Use this skill to move from "Klaviyo is broken" to a classified severity, an applied mitigation, and a written postmortem — without improvising under pressure.

The heavy content (full triage script, per-error remediation blocks, and the communication + postmortem templates) lives in references/ so this file stays a fast high-level runbook you can follow end-to-end, then drill into for depth.

Prerequisites

  • KLAVIYO_PRIVATE_KEY exported in the shell (a private API key, pk_...).
  • curl and python3 available for the triage and monitoring commands.
  • Read access to your app's health endpoint and, ideally, its Prometheus metrics.
  • Access to the Klaviyo dashboard to rotate a key if needed.
  • Klaviyo's revision header value your app ships (this runbook pins 2024-10-15, a dated stable API version — Klaviyo requires the header on every request).

Severity Levels

LevelDefinitionResponse TimeExample
P1Complete outage<15 minAll Klaviyo API calls returning 5xx
P2Degraded service<1 hour429 rate limiting, high latency
P3Minor impact<4 hoursWebhook delays, single endpoint errors
P4No user impactNext business dayMonitoring gaps, deprecation warnings

Instructions

Work the incident in five steps. Each step points at the reference file that carries the full, copy-paste-ready detail.

  1. Triage immediately. Run the quick-triage script to answer the four questions that classify every Klaviyo incident: Is Klaviyo itself down? Can we authenticate? Are we rate limited? Is our app healthy? See the full script in references/triage.md.
  2. Classify the failure. Walk the decision tree in references/triage.md to split a Klaviyo-side outage (status page shows an incident → enable fallback, monitor, communicate) from an integration issue (route by status code: 401/403, 429, 400, 5xx).
  3. Assign a severity from the table above and set the response-time clock.
  4. Apply the remediation for the observed error type — auth failure (401), rate limit (429), or Klaviyo server error (5xx). The exact commands are in references/remediation.md.
  5. Communicate and write the postmortem. Post the internal + external updates and, once resolved, collect evidence and fill the postmortem template from references/communication-and-postmortem.md.
Show full SKILL.md (208 more words)Show less

Output

Following this runbook produces:

  • A triage report printed to the terminal: Klaviyo status-page state, your API auth HTTP code, current rate-limit headers, and app health.
  • A severity classification (P1–P4) with the matching response-time target.
  • An applied mitigation (key rotation, concurrency reduction, or graceful degradation) with confirmation the error rate is recovering.
  • Stakeholder updates — one internal Slack message and, for P1/P2, one external status-page note.
  • A completed postmortem document (summary, timeline, root cause, impact, action items, lessons learned) plus an evidence bundle of logs and metrics.

Examples

Triage first (always run this before anything else):

bash
# Is Klaviyo itself down, or is it us?
curl -s "https://status.klaviyo.com/api/v2/status.json" \
  | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['status']['description'])"

Then classify by the auth HTTP code:

bash
curl -s -w "\nHTTP %{http_code}\n" -o /dev/null \
  -H "Authorization: Klaviyo-API-Key $KLAVIYO_PRIVATE_KEY" \
  -H "revision: 2024-10-15" \
  "https://a.klaviyo.com/api/accounts/"
# 401 → key problem  ·  429 → rate limited  ·  5xx → Klaviyo server error

For the complete triage script and decision tree see references/triage.md; for the full per-error remediation commands see references/remediation.md; for the Slack/status-page templates and the postmortem template see references/communication-and-postmortem.md.

Error Handling

IssueCauseSolution
Can't reach status pageNetwork issueUse mobile or check Twitter @klaviyo
Metrics unavailablePrometheus downCheck direct API with cURL
Key rotation panicNo backup keyAlways have a rotation procedure documented
Alert fatigueToo many false alarmsTune thresholds based on baseline

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 3 other files (references) in skills/.curated/klaviyo-incident-runbook of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/communication-and-postmortem.md
  • references/remediation.md
  • references/triage.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Klaviyo 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.

Klaviyo Incident Runbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Klaviyo Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.5kAutomated 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

Categories

Questions about Klaviyo Incident Runbook

What does Klaviyo Incident Runbook do?

Execute Klaviyo incident response procedures with triage, mitigation, and postmortem. Klaviyo Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute Klaviyo incident response procedures with triage, mitigation, and postmortem.

When should I use Klaviyo Incident Runbook?

Klaviyo Incident Runbook fits situations like: responding to Klaviyo-related outages; investigating API errors (401/403/429/5xx); running post-incident reviews for Klaviyo integration failures on an on-call rotation; with phrases like klaviyo incident.

How do I install Klaviyo Incident Runbook in Claude Code?

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

How do I install Klaviyo Incident Runbook in Codex?

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

Can I use Klaviyo 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 klaviyo-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/klaviyo-incident-runbook, .gemini/skills/klaviyo-incident-runbook, .github/skills/klaviyo-incident-runbook and .opencode/skills/klaviyo-incident-runbook in your project.

What does Klaviyo Incident Runbook need to run?

Going by SKILL.md and its folder, Klaviyo Incident Runbook needs the command-line tools its instructions call (curl and python3) and credentials named KLAVIYO_PRIVATE_KEY. Our summary lists: Python 3; A credential in KLAVIYO_PRIVATE_KEY. Its frontmatter pre-approves these tools: Read, Bash(curl:*), Bash(kubectl:*), Bash(npm:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Klaviyo Incident Runbook access the network?

SKILL.md names 4 domains. In commands or code: status.klaviyo.com and a.klaviyo.com; the agent is likely to contact these when it follows the instructions. As links in the text: klaviyo.com and developers.klaviyo.com. This is read from the text; nothing was executed.

Is Klaviyo 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 Klaviyo Incident Runbook use?

Klaviyo 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 Klaviyo Incident Runbook use?

About 1.5k tokens (SKILL.md is roughly 5.9k 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 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Klaviyo Incident Runbook?

Skills that share tags, products or a category with Klaviyo 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 Klaviyo 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.