lindy-debug-bundle
Comprehensive debugging toolkit for Lindy AI agents. Use when investigating complex agent failures, collecting diagnostics, or preparing support tickets for Lindy support. Trigger with phrases like "lindy debug", "lindy diagnostics", "lindy support bundle", "investigate lindy issue".
Best use case
lindy-debug-bundle is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Comprehensive debugging toolkit for Lindy AI agents. Use when investigating complex agent failures, collecting diagnostics, or preparing support tickets for Lindy support. Trigger with phrases like "lindy debug", "lindy diagnostics", "lindy support bundle", "investigate lindy issue".
Teams using lindy-debug-bundle should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lindy-debug-bundle/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lindy-debug-bundle Compares
| Feature / Agent | lindy-debug-bundle | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Comprehensive debugging toolkit for Lindy AI agents. Use when investigating complex agent failures, collecting diagnostics, or preparing support tickets for Lindy support. Trigger with phrases like "lindy debug", "lindy diagnostics", "lindy support bundle", "investigate lindy issue".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# 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
```bash
# 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
```bash
# 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
```bash
# 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 support@lindy.ai:
```markdown
## Lindy Support Bundle
**Account**: [your email]
**Agent Name**: [agent name]
**Agent URL**: https://app.lindy.ai/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
| Symptom | Likely Cause | Resolution |
|---------|-------------|------------|
| All agents failing simultaneously | Lindy platform outage | Check status.lindy.ai |
| Single agent failing | Agent-specific config issue | Review task detail view |
| Intermittent failures | Rate limits or credit exhaustion | Check usage dashboard |
| Slow execution | Model too large or too many steps | Switch to Gemini Flash, consolidate steps |
## Resources
- [Lindy Community](https://community.lindy.ai)
- [Lindy Documentation](https://docs.lindy.ai)
- [Lindy Status](https://status.lindy.ai)
## Next Steps
Proceed to `lindy-rate-limits` for credit and rate management.Related Skills
workhuman-debug-bundle
Workhuman debug bundle for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman debug bundle".
wispr-debug-bundle
Wispr Flow debug bundle for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr debug bundle".
webflow-debug-bundle
Collect Webflow debug evidence for support tickets and troubleshooting. Gathers SDK version, token validation, rate limit status, site connectivity, CMS health, and error logs into a single diagnostic bundle. Trigger with phrases like "webflow debug", "webflow support bundle", "collect webflow logs", "webflow diagnostic", "webflow troubleshoot".
vercel-debug-bundle
Collect Vercel debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Vercel problems. Trigger with phrases like "vercel debug", "vercel support bundle", "collect vercel logs", "vercel diagnostic".
veeva-debug-bundle
Veeva Vault debug bundle for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva debug bundle".
vastai-debug-bundle
Collect Vast.ai debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Vast.ai problems. Trigger with phrases like "vastai debug", "vastai support bundle", "collect vastai logs", "vastai diagnostic".
twinmind-debug-bundle
Collect comprehensive diagnostic information for TwinMind issues. Use when preparing support requests, investigating complex problems, or gathering evidence for bug reports. Trigger with phrases like "twinmind debug", "twinmind diagnostics", "collect twinmind info", "twinmind support bundle".
together-debug-bundle
Together AI debug bundle for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together debug bundle".
techsmith-debug-bundle
TechSmith debug bundle for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith debug bundle".
supabase-debug-bundle
Collect Supabase diagnostic info for troubleshooting and support tickets. Use when debugging connection failures, auth issues, Realtime drops, Storage errors, RLS misconfigurations, or preparing a support escalation. Trigger: "supabase debug", "supabase diagnostics", "supabase support bundle", "collect supabase logs", "debug supabase connection".
stackblitz-debug-bundle
Collect WebContainer diagnostic info: boot state, file system, process list. Use when working with WebContainers or StackBlitz SDK. Trigger: "stackblitz debug".
speak-debug-bundle
Collect diagnostic information for Speak API issues: auth verification, audio format validation, session inspection, and network testing. Use when implementing debug bundle features, or troubleshooting Speak language learning integration issues. Trigger with phrases like "speak debug bundle", "speak debug bundle".