Agent skill · operations · jeremylongshore
lindy-incident-runbook
Incident response procedures for Lindy AI agent failures and outages.
Why this skill is useful
Adds detailed incident response procedures and executable scripts for troubleshooting Lindy AI outages that aren't publicly documented.
What it needs
Requires curl installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 Severity Description Response Time Examples ---------- ------------- --------------- ---------- SEV1 All agents failing, customer impact 15 minutes Lindy platform outage, all webhooks failing SEV2 Critical agent down 30 minutes Support bot offline, phone agent unreachable SEV3 Degraded performance 2 hours High latency, intermittent failures SEV4 Minor issue 24 hours Non-critical agent misconfigured Quick Diagnostics (First 5 Minutes) Step 1: Check Lindy Platform Status Step 2: Check Your Integration 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 …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-incident-runbook