New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Lindy Incident Runbook

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

Incident response procedures for Lindy AI agent failures and outages.

MITAuto-check passedDevOps & Cloud

Install Lindy Incident Runbook

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

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

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

At a glance

Incident response procedures for Lindy AI agent failures and outages.

  • Works in 3 steps: Check Lindy Platform Status → Check Your Integration → Check Credit Balance
  • Responding to incidents
  • SKILL.md covers Overview, Prerequisites, Instructions and Incident Severity Levels, plus 9 more sections
  • Calls curl; reaches status.lindy.ai and public.lindy.ai; needs LINDY_WEBHOOK_SECRET

What it does

Lindy Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Incident response procedures for Lindy AI agent failures and outages. Use when responding to incidents, troubleshooting agent outages, or creating on-call procedures for Lindy-powered systems. Trigger with phrases like "lindy incident", "lindy outage", "lindy on-call", "lindy runbook", "lindy down".

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Incident response 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 incidents
  • Troubleshooting agent outages
  • Creating on-call procedures for Lindy-powered systems
  • With phrases like lindy incident

Example prompts

  • “lindy incident”
  • “lindy outage”
  • “lindy on-call”
  • “/lindy-incident-runbook”

Requirements

  • A credential in LINDY_WEBHOOK_SECRET
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*)

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Check Lindy Platform Status
  2. Check Your Integration
  3. Check Credit Balance

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
    • Write
    • Edit
    • Bash(curl:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    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.lindy.ai
    • public.lindy.ai

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

  • Credentials

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

    • LINDY_WEBHOOK_SECRET

    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

Lindy Incident Runbook loads about 2.3k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 867 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.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). 867 words, ~2,305 tokens.

Download SKILL.mdSave it as .claude/skills/lindy-incident-runbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lindy-incident-runbook
description
Incident response procedures for Lindy AI agent failures and outages. Use when responding to incidents, troubleshooting agent outages, or creating on-call procedures for Lindy-powered systems. Trigger with phrases like "lindy incident", "lindy outage", "lindy on-call", "lindy runbook", "lindy down".
allowed-tools
Read, Write, Edit, Bash(curl:*)
compatibility
Designed for Claude Code
version
1.20.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, lindy, incident-response

Lindy Incident Runbook

Overview

Incident response procedures for Lindy AI agent failures. Covers platform outages, individual agent failures, integration breakdowns, credit exhaustion, and webhook endpoint failures.

Prerequisites

  • Access to the affected Lindy workspace and task history
  • Ownership and escalation contacts for each affected integration
  • Read access to the receiving application's health checks and sanitized logs
  • A queue, manual route, or other documented fallback for critical events
  • An approved location for incident receipts that excludes secrets and payloads

Instructions

  1. Declare severity from customer impact and record the UTC detection time.
  2. Bound the failure to the platform, one agent, an integration, credits, or the receiving endpoint before changing configuration.
  3. Preserve sanitized task IDs and error evidence, then activate the smallest safe fallback that stops additional loss or duplicate actions.
  4. Apply the matching playbook below and verify recovery with fresh synthetic work rather than by retrying customer data blindly.
  5. Monitor the recovery window, document the outcome, and assign prevention work before resolving the incident.

Incident Severity Levels

SeverityDescriptionResponse TimeExamples
SEV1All agents failing, customer impact15 minutesLindy platform outage, all webhooks failing
SEV2Critical agent down30 minutesSupport bot offline, phone agent unreachable
SEV3Degraded performance2 hoursHigh latency, intermittent failures
SEV4Minor issue24 hoursNon-critical agent misconfigured

Quick Diagnostics (First 5 Minutes)

Step 1: Check Lindy Platform Status
bash
# Is Lindy up?
curl -s -o /dev/null -w "Lindy API: HTTP %{http_code}\n" \
  "https://public.lindy.ai" --max-time 5

# Check status page
echo "Status page: https://status.lindy.ai"
Step 2: Check Your Integration
bash
# Is your webhook receiver up?
curl -s -o /dev/null -w "Our endpoint: HTTP %{http_code}\n" \
  "https://api.yourapp.com/health" --max-time 5

# Is the webhook auth working?
curl -s -o /dev/null -w "Webhook auth: HTTP %{http_code}\n" \
  -X POST "https://api.yourapp.com/lindy/callback" \
  -H "Authorization: Bearer $LINDY_WEBHOOK_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"test": true}' --max-time 5
Step 3: Check Credit Balance

Log in at > Settings > Billing

  • Credits at 0? Agents stop processing
  • Credits low? Non-essential agents may be paused

Incident Playbooks

Incident: Lindy Platform Outage (SEV1)

Symptoms: All agents failing, status.lindy.ai shows incident Impact: All Lindy-dependent workflows halted

Runbook:

  1. Confirm outage at https://status.lindy.ai
  2. Notify team: "Lindy platform outage confirmed. All agents affected."
  3. Activate fallback procedures:
    • Route support emails to human inbox
    • Disable webhook triggers from your app
    • Queue events for replay when Lindy recovers
  4. Monitor status page for recovery
  5. When recovered: re-enable triggers, replay queued events, verify agent health

Fallback code:

typescript
async function triggerLindyWithFallback(payload: any) {
  try {
    const response = await fetch(WEBHOOK_URL, {
      method: 'POST',
      headers: {
        'Authorization': `Bearer ${SECRET}`,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify(payload),
      signal: AbortSignal.timeout(10000), // 10s timeout
    });

    if (!response.ok) throw new Error(`HTTP ${response.status}`);
    return { routed: 'lindy' };
  } catch (error) {
    console.error('Lindy unreachable, activating fallback:', error);
    await queueForReplay(payload); // Store for later
    await notifyTeam(`Lindy trigger failed: ${error}`);
    return { routed: 'fallback' };
  }
}
Incident: Individual Agent Failure (SEV2)

Symptoms: Specific agent tasks showing "Failed" status Impact: One workflow affected, others may be fine

Runbook:

  1. Open agent > Tasks tab > Filter by "Failed"
  2. Click latest failed task — identify the failing step
  3. Diagnose based on failing step type:
    • Trigger step: Auth expired? Filter too restrictive?
    • Action step: Integration token expired? Target API down?
    • Condition step: Ambiguous condition prompt?
    • Agent step: Looping? Exit conditions unreachable?
  4. Fix the root cause:
    • Re-authorize expired integrations
    • Fix action configuration
    • Simplify condition prompts
    • Add fallback exit conditions
  5. Test with a manual trigger
  6. Monitor next 5 tasks for success
Incident: Integration Auth Expired (SEV2-3)

Symptoms: Actions failing with "Not authorized" or "Token expired" Impact: All tasks using that integration fail

Runbook:

  1. Identify which integration is failing (Gmail, Slack, Sheets, etc.)
  2. In Lindy dashboard: Settings > Integrations
  3. Find the expired connection (may show warning icon)
  4. Click Re-authorize and complete OAuth flow
  5. Re-test the agent with a manual trigger
  6. Set calendar reminder for 90-day re-authorization check
Show full SKILL.md (362 more words)Show less
Incident: Credit Exhaustion (SEV2-3)

Symptoms: Agents stop running, no new tasks created Impact: All agents paused until credits refill

Runbook:

  1. Confirm at Settings > Billing: credits at 0
  2. Immediate: Upgrade plan or purchase additional credits
  3. Investigate: Which agent consumed the most credits?
  4. Root cause: trigger storm? looping agent step? large model overuse?
  5. Fix: Add trigger filters, set exit conditions, downgrade model
  6. Prevent: Set budget alerts at 50%, 80%, 95% thresholds
Incident: Webhook Endpoint Failure (SEV2-3)

Symptoms: Lindy agent runs but your callback never receives data Impact: Agent completes but results are lost

Runbook:

  1. Check your endpoint health: curl -s https://api.yourapp.com/health
  2. Check server logs for incoming requests from Lindy
  3. Verify the HTTP Request action URL matches your production endpoint
  4. Test endpoint independently: send a POST with curl
  5. If endpoint was down: replay failed tasks (re-trigger the agent)
  6. If URL mismatch: update URL in Lindy agent HTTP Request action

Escalation Matrix

LevelContactWhen
L1On-call engineerInitial response, diagnostics
L2Engineering leadAfter 30 min SEV1, 1 hour SEV2
L3VP EngineeringAfter 1 hour SEV1
Lindy Supportsupport@lindy.aiConfirmed Lindy platform issue

Post-Incident Template

markdown
## Incident Report

**Date**: YYYY-MM-DD
**Severity**: SEV[1-4]
**Duration**: [start time] to [end time] ([total minutes])
**Impact**: [what was affected, customer impact]

### Timeline
- HH:MM — Issue detected via [monitoring/user report]
- HH:MM — On-call paged, diagnostics started
- HH:MM — Root cause identified: [cause]
- HH:MM — Fix applied: [what was done]
- HH:MM — Service restored, monitoring confirmed

### Root Cause
[Technical description of what failed and why]

### Resolution
[What was done to fix it]

### Prevention
- [ ] [Action item 1]
- [ ] [Action item 2]
- [ ] [Action item 3]

Output

Produce an incident receipt that records the severity, UTC start and recovery times, affected agents and integrations, sanitized task IDs, the confirmed failure boundary, mitigation, recovery checks, and follow-up owners. Keep credentials, webhook secrets, customer payloads, and complete private endpoint URLs out of the receipt.

Examples

For an expired integration, record the failing action and task ID, preserve the original error text without its token, re-authorize the connection, and verify five subsequent tasks before resolving the incident. For a platform outage, record the status-page confirmation, queue or fallback activation time, replay count after recovery, and the check that proved normal processing resumed.

Error Handling

Incident TypeDetectionAutomated Response
Platform outageHealth check failsQueue events, notify team
Agent failureTask Completed triggerSlack alert to #ops
Auth expiryAction step failsAlert + re-auth link
Credit exhaustionBilling checkPause non-critical agents
Endpoint downHealth checkRedirect to fallback

Resources

Next Steps

Proceed to lindy-data-handling for data security and compliance.

© 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/lindy-incident-runbook of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

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

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

  • Activation Governance Chaos Rollout

    Ali-Marandi/DataSense

    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 8 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 Lindy Incident Runbook

What does Lindy Incident Runbook do?

Incident response procedures for Lindy AI agent failures and outages. Lindy Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Incident response procedures for Lindy AI agent failures and outages.

When should I use Lindy Incident Runbook?

Lindy Incident Runbook fits situations like: responding to incidents; troubleshooting agent outages; creating on-call procedures for Lindy-powered systems; with phrases like lindy incident.

How do I install Lindy Incident Runbook in Claude Code?

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

How do I install Lindy Incident Runbook in Codex?

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

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

What does Lindy Incident Runbook need to run?

Going by SKILL.md and its folder, Lindy Incident Runbook needs the command-line tools its instructions call (curl) and credentials named LINDY_WEBHOOK_SECRET. Our summary lists: A credential in LINDY_WEBHOOK_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Lindy Incident Runbook access the network?

SKILL.md names 2 domains. In commands or code: status.lindy.ai and public.lindy.ai; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

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

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

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

What are the alternatives to Lindy Incident Runbook?

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