Configure Apollo.io multi-environment setup. Use when setting up development, staging, and production environments, or managing multiple Apollo configurations. Trigger with phrases like "apollo environments", "apollo staging", "apollo dev prod", "apollo multi-tenant", "apollo env config".
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.
Configure Apollo.io for multiple environments (development, staging, production) with proper isolation, configuration management, and deployment strategies.
apollo-install-auth setupFollow these high-level steps to implement apollo-multi-env-setup:
For full implementation details, load: Read(plugins/saas-packs/apollo-pack/skills/apollo-multi-env-setup/references/implementation-guide.md)
| Issue | Resolution |
|---|---|
| Wrong environment | Check NODE_ENV variable |
| Missing API key | Verify secrets configuration |
| Feature disabled | Check environment config |
| Rate limit mismatch | Verify config values |
Proceed to apollo-observability for monitoring setup.
Basic usage: Apply apollo multi env setup to a standard project setup with default configuration options.
Advanced scenario: Customize apollo multi env setup for production environments with multiple constraints and team-specific requirements.