Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/lindy-incident-runbook
Incident response procedures for Lindy AI agent failures and outages.
Passed 22 of 23 test cases with the skill, and 10 of 23 without it.
and 12 more in the full report
12 fixed10 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our engineer wants to verify if the public Lindy API endpoint is reachable via terminal command with a strict 5-second timeout. What precise endpoint URL and timeout flag should be used in the curl command?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the URL https://public.lindy.ai | Missed | Passed |
| Includes the flag --max-time 5 | Passed | Passed |
The instructions your model reads when the skill loads.
Incident response procedures for Lindy AI agent failures. Covers platform outages, individual agent failures, integration breakdowns, credit exhaustion, and webhook endpoint failures.
| 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 |
# 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"
# 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" \
test cases passed, vs 10 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.