New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Lindy Debug Bundle

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Comprehensive debugging toolkit for Lindy AI agents. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check passedSales & Support

Install Lindy Debug Bundle

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-debug-bundle -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace lindy-debug-bundle --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/lindy-debug-bundle .claude/skills/lindy-debug-bundle && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lindy-debug-bundle
GitHub stars
2.8k
Token cost
~1.7k tokens
SKILL.md length
449 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Comprehensive debugging toolkit for Lindy AI agents. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 6 steps: Collect Environment Info → Test Webhook Connectivity → Review Agent Task History → …
  • Investigating complex agent failures
  • SKILL.md covers Current State, Overview, Prerequisites and Instructions, plus 6 more sections
  • Calls curl, node and python3; reaches public.lindy.ai and slack.com; needs LINDY_WEBHOOK_SECRET and LINDY_API_KEY

What it does

Lindy Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in Sales & Support, covering Customer support and Debugging. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Investigating complex agent failures
  • Collecting diagnostics
  • Preparing support tickets for Lindy support
  • With phrases like lindy debug

Example prompts

  • “lindy debug”
  • “lindy diagnostics”
  • “lindy support bundle”
  • “/lindy-debug-bundle”

Requirements

  • Python 3
  • Node.js
  • A credential in LINDY_API_KEY
  • A credential in LINDY_WEBHOOK_SECRET
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*), Grep

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Collect Environment Info
  2. Test Webhook Connectivity
  3. Review Agent Task History
  4. Check Integration Health
  5. Diagnose Specific Failure Types
  6. Generate Support Bundle

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(curl:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • node
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • public.lindy.ai
    • slack.com
    • googleapis.com
    • api.notion.com

    Also links to:

    • docs.lindy.ai
    • status.lindy.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • LINDY_WEBHOOK_SECRET
    • LINDY_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Lindy Debug Bundle loads about 1.7k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 449 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 449 words, ~1,717 tokens.

Download SKILL.mdSave it as .claude/skills/lindy-debug-bundle/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lindy-debug-bundle
description
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".
allowed-tools
Read, Write, Edit, Bash(curl:*), Grep
compatibility
Designed for Claude Code
version
1.20.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, lindy, debugging

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
Show full SKILL.md (176 more words)Show less
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**: 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]

Output

Deliver a time-bounded support bundle containing the affected agent and task IDs, reproduction steps, sanitized error messages, environment facts, and the result of the webhook and integration checks. Remove credentials, personal data, and full webhook URLs before sharing the bundle outside the workspace.

Examples

If tasks begin failing after an integration reconnect, capture one failed task ID, the failing action name, the HTTP status from the target, and the time the connection was reauthorized. A bundle saying “agent failed” without a task ID, timestamp, and reproducible trigger is insufficient for escalation.

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.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/lindy-debug-bundle of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Lindy Debug Bundle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lindy Debug Bundle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lindy Debug Bundle this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: PassMIT
Bug ReproducerAnastasiyaW/codex-claude-code-config154—~4.1kAutomated safety check: PassMIT
Debugging ExperimentsPostHog/posthog40k—~5.4kAutomated safety check: PassCustom licence
Saleor Storefrontaiskillstore/marketplace430—~677Automated safety check: PassMIT
Analyze Dotnet Agent Logsnewrelic/newrelic-dotnet-agent117—~1.5kAutomated safety check: PassApache-2.0
Miniprogram DevelopmentTencentCloudBase/CloudBase-AI-Toolkit1.1k1 repos~3.7kAutomated safety check: PassMIT

Similar skills

  • Bug Reproducer

    AnastasiyaW/codex-claude-code-config

    Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix.

    154 GitHub stars~4.1k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Debugging Experiments

    PostHog/posthog

    Official

    Debug and support PostHog Experiments (A/B tests) for a customer looking at their own results.

    40k GitHub stars~5.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Saleor Storefront

    aiskillstore/marketplace

    Saleor e-commerce API patterns for building storefronts. An agent skill from aiskillstore/marketplace.

    430 GitHub stars~677 tokensUpdated today
    Sales & SupportAuto-check passed

  • Analyze Dotnet Agent Logs

    newrelic/newrelic-dotnet-agent

    Parse and diagnose New Relic .NET agent logs (newrelicagent.log) and profiler logs (NewRelic.Profiler.<pid.log) from a support ticket.

    117 GitHub stars~1.5k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Miniprogram Development

    TencentCloudBase/CloudBase-AI-Toolkit

    WeChat Mini Program development skill for building, debugging, previewing, testing, publishing, and optimizing mini program projects (小程序开发、调试、预览、发布).

    1.1k GitHub starsUsed in 1 repo~3.7k tokens
    Frontend & DesignAuto-check passed

  • Sf Debug

    Jaganpro/sf-skills

    Salesforce debug log analysis and troubleshooting with 100-point scoring.

    424 GitHub stars~1.3k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated yesterday
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Lindy Debug Bundle

What does Lindy Debug Bundle do?

Comprehensive debugging toolkit for Lindy AI agents. An agent skill from jeremylongshore/tons-of-skills-marketplace. Lindy Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Comprehensive debugging toolkit for Lindy AI agents.

When should I use Lindy Debug Bundle?

Lindy Debug Bundle fits situations like: investigating complex agent failures; collecting diagnostics; preparing support tickets for Lindy support; with phrases like lindy debug.

How do I install Lindy Debug Bundle in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-debug-bundle -a claude-code`. Or copy the skill folder (skills/.curated/lindy-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lindy-debug-bundle in your project. Claude Code loads it when a task matches its description.

How do I install Lindy Debug Bundle in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-debug-bundle -a codex`. Or copy the skill folder (skills/.curated/lindy-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lindy-debug-bundle in your project. Codex loads it when a task matches its description.

Can I use Lindy Debug Bundle in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lindy-debug-bundle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lindy-debug-bundle, .gemini/skills/lindy-debug-bundle, .github/skills/lindy-debug-bundle and .opencode/skills/lindy-debug-bundle in your project.

What does Lindy Debug Bundle need to run?

Going by SKILL.md and its folder, Lindy Debug Bundle needs the command-line tools its instructions call (curl, node and python3) and credentials named LINDY_WEBHOOK_SECRET and LINDY_API_KEY. Our summary lists: Python 3; Node.js; A credential in LINDY_API_KEY; A credential in LINDY_WEBHOOK_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Lindy Debug Bundle access the network?

SKILL.md names 6 domains. In commands or code: public.lindy.ai, slack.com, googleapis.com and api.notion.com; the agent is likely to contact these when it follows the instructions. As links in the text: docs.lindy.ai and status.lindy.ai. This is read from the text; nothing was executed.

Is Lindy Debug Bundle safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lindy Debug Bundle use?

Lindy Debug Bundle is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lindy Debug Bundle use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 936 tokens, read only when the agent opens those files.

What are the alternatives to Lindy Debug Bundle?

Skills that share tags, products or a category with Lindy Debug Bundle: Bug Reproducer (AnastasiyaW/codex-claude-code-config, 154 stars), Debugging Experiments (PostHog/posthog, 40k stars), Saleor Storefront (aiskillstore/marketplace, 430 stars) and Analyze Dotnet Agent Logs (newrelic/newrelic-dotnet-agent, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lindy Debug Bundle?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.