Agent skill · software engineering · jeremylongshore
oraclecloud-incident-runbook
Self-service incident runbook for OCI outages \u2014 health probes,\
Why this skill is useful
Adds executable scripts for automated health probes and instance recovery that are not available in public documentation.
What it needs
Requires oci, python3 installed locally. Requires oraclecloud account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Oracle Cloud Incident Runbook Overview Self-service runbook for when OCI instances go down and the status page stays green. OCI's status page has a history of not acknowledging outages in real time (London Jan 2026 — 502s and instances disappearing for 10 minutes with no status update). OCI Support response times average 4+ hours for Sev-1 tickets. This runbook gives you health probes, automated instance recovery, cross-AD failover, and cross-region failover — all executable without waiting on Oracle. Purpose: Detect OCI service degradation independently, recover instances automatically, and fail over to alternate availability domains or regions when the primary is impacted. Prerequisites OCI CLI installed and configured — ~/.oci/config validated (see oraclecloud-install-auth) Python 3.8+ with the OCI SDK — pip install oci Pre-configured resources: at least one compute instance, a VCN with subnets in multiple ADs IAM policies: manage instances, manage volumes, inspect work-requests in the target compartment Boot volume backups enabled (recovery depends on having a recent backup) Instructions Step 1: Independent Health Probes Do not trust the OCI status page alone. Run your own health checks against the OCI API: Step 2: Severity Classification Level Condition Detection Response Time ------- ----------- ----------- --------------- P1 — Total Outage All API probes fail, instances unreachable All 3 probes return degraded Immediate — trigger cross-region failover P2 — Partial Degradation Some APIs slow (>2s latency), instance agent unresponsive Latency >2000ms on any probe 15 min — attempt instance recovery, prepare failover P3 — Intermittent Sporadic 429/500 errors, some requests succeed Occasional probe failures 1 hour — enable retries, monitor trend Step 3: Instance Recovery Actions Step 4: Cross-AD Failover When an entire availability domain is impacted, launch a replacement instance in a different AD using the latest boot volume backup: Step 5: Cross-Region Failover …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/oraclecloud-incident-runbook