Configure Apollo.io local development workflow. Use when setting up development environment, testing API calls locally, or establishing team development practices. Trigger with phrases like "apollo local dev", "apollo development setup", "apollo dev environment", "apollo testing locally".
From apollo-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin apollo-packThis skill is limited to using the following tools:
references/implementation-guide.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Set up efficient local development workflow for Apollo.io integrations with proper environment management, testing, and debugging.
apollo-install-auth setupFollow these high-level steps to implement apollo-local-dev-loop:
For full implementation details, load: Read(plugins/saas-packs/apollo-pack/skills/apollo-local-dev-loop/references/implementation-guide.md)
| Error | Cause | Solution |
|---|---|---|
| Missing API Key | .env not loaded | Run source .env or use dotenv |
| Mock Not Working | MSW not configured | Ensure setupServer is called |
| Rate Limited in Dev | Too many test calls | Use mock server for tests |
| Stale Credentials | Key rotated | Update .env with new key |
Proceed to apollo-sdk-patterns for production-ready code patterns.
Basic usage: Apply apollo local dev loop to a standard project setup with default configuration options.
Advanced scenario: Customize apollo local dev loop for production environments with multiple constraints and team-specific requirements.