Apply Apollo.io API security best practices. Use when securing Apollo integrations, managing API keys, or implementing secure data handling. Trigger with phrases like "apollo security", "secure apollo api", "apollo api key security", "apollo data protection".
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.
Reviews prose for communication issues impeding comprehension, outputs minimal fixes in a three-column table per Microsoft Writing Style Guide. Useful for 'review prose' or 'improve prose' requests.
Implement security best practices for Apollo.io API integrations including key management, data protection, and access controls.
apollo-install-auth setupFollow these high-level steps to implement apollo-security-basics:
For full implementation details, load: Read(plugins/saas-packs/apollo-pack/skills/apollo-security-basics/references/implementation-guide.md)
| Issue | Mitigation |
|---|---|
| Key exposure | Immediate rotation |
| PII in logs | Implement redaction |
| Unauthorized access | Audit and revoke |
| Data breach | Follow incident response |
Proceed to apollo-prod-checklist for production deployment.
Basic usage: Apply apollo security basics to a standard project setup with default configuration options.
Advanced scenario: Customize apollo security basics for production environments with multiple constraints and team-specific requirements.