Apollo.io incident response procedures. Use when handling Apollo outages, debugging production issues, or responding to integration failures. Trigger with phrases like "apollo incident", "apollo outage", "apollo down", "apollo production issue", "apollo emergency".
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.
Structured incident response procedures for Apollo.io integration issues with diagnosis steps, mitigation actions, and recovery procedures.
apollo-install-auth setupFollow these high-level steps to implement apollo-incident-runbook:
For full implementation details, load: Read(plugins/saas-packs/apollo-pack/skills/apollo-incident-runbook/references/implementation-guide.md)
| Issue | Escalation |
|---|---|
| P1 > 30 min | Page on-call lead |
| P2 > 2 hours | Notify management |
| Recurring P3 | Create P2 tracking |
| Apollo outage | Open support ticket |
Proceed to apollo-data-handling for data management.
Basic usage: Apply apollo incident runbook to a standard project setup with default configuration options.
Advanced scenario: Customize apollo incident runbook for production environments with multiple constraints and team-specific requirements.