From lindy-pack
Troubleshoot common Lindy AI errors and issues. Use when encountering errors, debugging agent failures, or resolving integration problems. Trigger with phrases like "lindy error", "lindy not working", "debug lindy", "lindy troubleshoot".
How this skill is triggered — by the user, by Claude, or both
Slash command
/lindy-pack:lindy-common-errorsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comprehensive guide to troubleshooting common Lindy AI errors and issues.
Comprehensive guide to troubleshooting common Lindy AI errors and issues.
Causes:
Solutions:
Causes:
Solutions:
Solutions:
Solutions:
Solutions:
For detailed implementation code and configurations, load the reference guide:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
| Error Code | HTTP Status | Retry? |
|---|---|---|
| LINDY_AUTH_INVALID_KEY | 401 | No |
| LINDY_RATE_LIMITED | 429 | Yes |
| LINDY_AGENT_NOT_FOUND | 404 | No |
| LINDY_AGENT_TIMEOUT | 504 | Yes |
| LINDY_TOOL_FAILED | 500 | Maybe |
Proceed to lindy-debug-bundle for comprehensive debugging.
See debugging implementation details for output format specifications.
Basic usage: Apply lindy common errors to a standard project setup with default configuration options.
Advanced scenario: Customize lindy common errors for production environments with multiple constraints and team-specific requirements.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
4plugins reuse this skill
First indexed Jul 11, 2026
npx claudepluginhub terrylica/claude-code-plugins-plus --plugin lindy-pack