LI

lindy-debug-bundle

Provides diagnostic commands and support bundle generation for troubleshooting Lindy AI agent issues.

Install

mkdir -p .claude/skills/lindy-debug-bundle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6016" && unzip -o skill.zip -d .claude/skills/lindy-debug-bundle && rm skill.zip

Installs to .claude/skills/lindy-debug-bundle

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Comprehensive debugging toolkit for Lindy AI agents.
52 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Collect local environment diagnostics
  • Test webhook trigger connectivity
  • Review agent task history for failures
  • Test outbound connectivity to integration targets

How it works

The tool collects system environment data, validates API and webhook connectivity, and guides users through identifying specific failure points in agent task history.

Inputs & outputs

You give it
Agent ID and failing task details
You get back
Diagnostic report and support bundle

When to use lindy-debug-bundle

  • Investigate agent execution failures
  • Collect local environment diagnostics
  • Test webhook triggers
  • Generate support bundles for troubleshooting

About this skill

Lindy Debug Bundle

Current State

!node --version 2>/dev/null || echo 'Node.js not installed' !python3 --version 2>/dev/null || echo 'Python not installed' !curl --version 2>/dev/null | head -1 || echo 'curl not installed'

Overview

Systematic diagnostics for Lindy AI agent issues. Collects environment info, tests API connectivity, reviews agent task history, and generates a support bundle for Lindy's support team.

Prerequisites

  • Access to Lindy dashboard (https://app.lindy.ai)
  • curl installed for API testing
  • Agent ID and webhook URLs available

Instructions

Step 1: Collect Environment Info

# Local environment diagnostics
echo "=== Local Environment ==="
echo "Node: $(node --version 2>/dev/null || echo 'N/A')"
echo "Python: $(python3 --version 2>/dev/null || echo 'N/A')"
echo "OS: $(uname -srm)"
echo "Date: $(date -u '+%Y-%m-%d %H:%M:%S UTC')"
echo "LINDY_API_KEY set: $([ -n "$LINDY_API_KEY" ] && echo 'yes' || echo 'NO')"
echo "LINDY_WEBHOOK_SECRET set: $([ -n "$LINDY_WEBHOOK_SECRET" ] && echo 'yes' || echo 'NO')"

Step 2: Test Webhook Connectivity

# Test webhook trigger endpoint
echo "=== Webhook Connectivity ==="
WEBHOOK_URL="${LINDY_WEBHOOK_URL:-https://public.lindy.ai/api/v1/webhooks/YOUR_ID}"

# Test without auth (expect 401)
echo "Without auth (expect 401):"
curl -s -o /dev/null -w "HTTP %{http_code} in %{time_total}s\n" \
  -X POST "$WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{"test": true}'

# Test with auth (expect 200)
echo "With auth (expect 200):"
curl -s -o /dev/null -w "HTTP %{http_code} in %{time_total}s\n" \
  -X POST "$WEBHOOK_URL" \
  -H "Authorization: Bearer $LINDY_WEBHOOK_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"test": true, "debug": "bundle-test"}'

Step 3: Review Agent Task History

In the Lindy dashboard:

  1. Navigate to the failing agent
  2. Open the Tasks tab
  3. Filter by Failed status
  4. For each failed task:
    • Note the timestamp
    • Click to expand step-by-step execution
    • Identify the failing step (marked red)
    • Copy the error message and input/output data
  5. Look for patterns: same step failing? same time of day? same input type?

Step 4: Check Integration Health

# Test outbound connectivity to common Lindy integration targets
echo "=== Integration Targets ==="
for url in \
  "https://public.lindy.ai" \
  "https://slack.com/api/auth.test" \
  "https://www.googleapis.com/gmail/v1/users/me/profile" \
  "https://api.notion.com/v1/users/me"
do
  status=$(curl -s -o /dev/null -w "%{http_code}" --max-time 5 "$url" 2>/dev/null)
  echo "$url -> HTTP $status"
done

Step 5: Diagnose Specific Failure Types

Trigger not firing:

  • Verify agent status: active (not paused)
  • Check trigger filter conditions
  • For webhooks: test URL with curl
  • For email: re-authorize Gmail/Outlook
  • For schedule: verify timezone settings

Action failing:

  • Check integration authorization (re-auth if token expired)
  • Verify field references: {{step_name.field}} syntax correct
  • Test the target service independently
  • Check if action is a Premium Action (requires Pro plan)

Agent step looping:

  • Review exit conditions — are they achievable?
  • Check credit consumption (rapid drain = looping)
  • Reduce available skills to 2-4 focused ones
  • Add a fallback exit condition

High credit consumption:

  • Review model selection: Gemini Flash (cheap) vs GPT-4 (expensive)
  • Check for unnecessary agent steps (use deterministic actions instead)
  • Review loop configurations for unbounded max cycles

Step 6: Generate Support Bundle

Compile the following for a support ticket to [email protected]:

## Lindy Support Bundle

**Account**: [your email]
**Agent Name**: [agent name]
**Agent URL**: agents/[agent-id]
**Issue Start**: [date/time UTC]
**Frequency**: [every time / intermittent / once]

### Environment
- Browser: [Chrome/Firefox/Safari version]
- Plan: [Free/Pro/Business/Enterprise]
- Credit Balance: [remaining credits]

### Reproduction Steps
1. [step 1]
2. [step 2]

### Failed Task IDs
- [task-id-1] at [timestamp]
- [task-id-2] at [timestamp]

### Error Messages
[Copy exact error text from task detail view]

### What I Tried
- [attempt 1]
- [attempt 2]

Diagnostic Decision Tree

Agent not working?
├── No task created → Check trigger configuration
│   ├── Webhook? → Test with curl (Step 2)
│   ├── Email? → Re-authorize + check filters
│   └── Schedule? → Check timezone + credit balance
├── Task created but failed → Check task detail view
│   ├── Trigger step failed → Auth/connectivity issue
│   ├── Action step failed → Integration auth expired
│   ├── Condition step failed → Ambiguous condition prompt
│   └── Agent step looping → Exit conditions unreachable
└── Task completed but wrong result → Prompt/config issue
    ├── Wrong output → Refine agent prompt
    ├── Missing data → Check field references
    └── Partial execution → Review condition branches

Error Handling

SymptomLikely CauseResolution
All agents failing simultaneouslyLindy platform outageCheck status.lindy.ai
Single agent failingAgent-specific config issueReview task detail view
Intermittent failuresRate limits or credit exhaustionCheck usage dashboard
Slow executionModel too large or too many stepsSwitch to Gemini Flash, consolidate steps

Resources

Next Steps

Proceed to lindy-rate-limits for credit and rate management.

When not to use it

  • When the Lindy platform is experiencing a total outage
  • When the issue is related to billing or credit exhaustion

Prerequisites

Access to Lindy dashboardcurl installedAgent ID and webhook URLs

Limitations

  • Requires manual identification of failing steps in the dashboard
  • Webhook testing requires valid webhook secrets

How it compares

Unlike manual troubleshooting, this tool automates the collection of environment diagnostics and connectivity tests into a standardized support bundle.

Compared to similar skills

lindy-debug-bundle side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
lindy-debug-bundle (this skill)127dReviewIntermediate
memory-mcp628dReviewIntermediate
context-degradation32moReviewAdvanced
langsmith-fetch67moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

memory-mcp

d-o-hub

Use and troubleshoot the Memory MCP server for episodic memory retrieval and pattern analysis. Use this skill when working with MCP server tools (query_memory, analyze_patterns, advanced_pattern_analysis), validating the MCP implementation, or debugging MCP server issues.

6100

context-degradation

muratcankoylan

This skill should be used when the user asks to "diagnose context problems", "fix lost-in-middle issues", "debug agent failures", "understand context poisoning", or mentions context degradation, attention patterns, context clash, context confusion, or agent performance degradation. Provides patterns for recognizing and mitigating context failures.

323

langsmith-fetch

ComposioHQ

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

67

replit-common-errors

jeremylongshore

Diagnose and fix Replit common errors and exceptions. Use when encountering Replit errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "replit error", "fix replit", "replit not working", "debug replit".

11

skill-tuning

catlog22

Universal skill diagnosis and optimization tool. Detect and fix skill execution issues including context explosion, long-tail forgetting, data flow disruption, and agent coordination failures. Supports Gemini CLI for deep analysis. Triggers on "skill tuning", "tune skill", "skill diagnosis", "optimize skill", "skill debug".

10

agent-introspection-debugging

ThanhTrunggDEV

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.

00

Search skills

Search the agent skills registry