Individual skill
lindy-incident-runbook
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".
plugins/saas-packs/lindy-pack/skills/lindy-incident-runbook/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,917
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- lindy Declared skill tag
- incident-response Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,231 bytesSKILL.mdcore · 9,231 bytesSKILL.mdcore · 9,231 bytesreferences/implementation-guide.mddoc · 5,326 bytes
Read excerpt
# 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