apollo-incident-runbook

The Apollo Incident Runbook aligns with its stated purpose of guiding incident diagnosis and remediation for Apollo.io integration issues. It relies on standard ops tools (curl, kubectl) and clearly defines severity tiers, quick checks, and recovery steps. However, there are security concerns around credential handling and potential secret leakage through command output/logs, as well as general data-flow exposure of API keys in documentation and commands. The footprint is proportionate to an ops-oriented runbook, but the credential exposure risks warrant tightening (redacted examples, explicit secret rotation policy, and guidance to avoid echoing secrets in logs). Overall, the skill is BENIGN to SUSPICIOUS in risk terms: the operational intent is legitimate, but data flow and secret handling require mitigations to reduce exposure.