Agent skill · software engineering · jeremylongshore
oraclecloud-multi-env-setup
Configure multi-environment OCI workflows with config profiles and compartment-per-environment
Why this skill is useful
Adds specific OCI compartment management patterns and Python scripts for safe multi-environment workflows that the AI wouldn't reliably generate on its own.
What it needs
Requires oci installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Oracle Cloud Multi-Environment Setup Overview OCI has no "accounts" like AWS — you use compartments plus OCI config profiles for dev/staging/prod separation. But profile switching is manual, compartment OCIDs are easy to confuse, and one wrong --compartment-id deploys to production. This skill sets up safe multi-environment workflows with named profiles, compartment aliasing, environment validation, and deployment guardrails. Purpose: Configure safe, repeatable multi-environment OCI workflows that prevent accidental cross-environment operations. Prerequisites OCI Python SDK — pip install oci OCI CLI — installed and configured (oci setup config) Separate API keys per environment (recommended) or a single key with cross-compartment policies Compartment OCIDs for each environment (dev, staging, prod) Python 3.8+ Instructions Step 1: Configure Multi-Profile ~/.oci/config The OCI config file supports named profiles. Each profile can point to different tenancies, regions, or use different API keys: Best practice: Use different API key pairs per environment. If the dev key is compromised, prod is unaffected. Step 2: Create an Environment Configuration Module Centralize compartment OCIDs and profile mappings to prevent OCID confusion: Step 3: Build Safe Environment-Aware Clients Wrap OCI clients with environment validation to prevent cross-environment mistakes: Step 4: CLI Profile Switching Use profiles with the OCI CLI to target specific environments: Shell aliases for safety: Step 5: Validate Config Before Operations Always validate the config file and profile before running automation: Step 6: Environment Variables for CI/CD For CI/CD pipelines where config files are impractical, use environment variables: Output Successful completion produces: A ~/.oci/config file with named profiles for each environment (DEV, STAGING, PROD) An environment configuration module mapping profiles to compartment OCIDs An environment-aware client factory with safety guardrails blocking destr …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/oraclecloud-multi-env-setup