From apollo-pack
Diagnose and fix common Apollo.io API errors. Use when encountering Apollo API errors, debugging integration issues, or troubleshooting failed requests. Trigger with phrases like "apollo error", "apollo api error", "debug apollo", "apollo 401", "apollo 429", "apollo troubleshoot".
How this skill is triggered — by the user, by Claude, or both
Slash command
/apollo-pack:apollo-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 diagnosing and fixing common Apollo.io API errors with specific solutions and prevention strategies.
Comprehensive guide to diagnosing and fixing common Apollo.io API errors with specific solutions and prevention strategies.
apollo-install-auth setupFollow these high-level steps to implement apollo-common-errors:
For full implementation details, load: Read(plugins/saas-packs/apollo-pack/skills/apollo-common-errors/references/implementation-guide.md)
See debugging implementation details for output format specifications.
| Issue | Solution |
|---|---|
| 401 Unauthorized | Verify API key in environment variables |
| 429 Rate Limited | Implement exponential backoff, reduce request frequency |
| 500 Server Error | Retry with backoff, check Apollo status page |
Proceed to apollo-debug-bundle for collecting debug evidence.
Basic usage: Apply apollo common errors to a standard project setup with default configuration options.
Advanced scenario: Customize apollo common errors for production environments with multiple constraints and team-specific requirements.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
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.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026
npx claudepluginhub terrylica/claude-code-plugins-plus --plugin apollo-pack