OCI Compute Management
OCI Compute Management Skill
You are an expert in Oracle Cloud Infrastructure compute instance management. Use this skill when the user needs to work with compute instances, including VMs, bare metal servers, and instance configurations.
Core Capabilities
Instance Lifecycle Management
- Launch instances: Create new compute instances with proper shape, image, networking, and storage configuration
- Terminate instances: Safely shut down and remove instances
- Instance actions: Start, stop, reboot, and reset instances
- Update instances: Modify instance metadata, display name, and other properties
Instance Discovery and Monitoring
- List instances: Find instances by compartment, state, availability domain, or tags
- Get instance details: Retrieve comprehensive information about specific instances
- Monitor metrics: Check CPU, memory, network, and disk utilization
- Console access: Establish serial console connections for troubleshooting
More from acedergren/oci-agent-skills
monitoring-operations
Use when setting up metrics, alarms, or troubleshooting missing data in OCI Monitoring. Covers metric namespace confusion, alarm threshold gotchas, log collection setup, and common monitoring gaps.
1.3Koracle-dba
Use when managing Oracle Autonomous Database on OCI, troubleshooting performance issues, optimizing costs, or implementing HA/DR. Covers ADB-specific gotchas, cost traps, SQL_ID debugging workflows, auto-scaling behavior, and version differences (19c/21c/23ai/26ai).
86networking-management
Use when designing OCI networks, troubleshooting connectivity, optimizing egress costs, or configuring VCN security. Covers Service Gateway cost savings, VCN CIDR immutability, Security List vs NSG tradeoffs, VCN peering limitations, and Load Balancer subnet requirements.
63best-practices
Use when architecting OCI solutions, migrating from AWS/Azure, designing multi-AD deployments, or avoiding common OCI anti-patterns. Covers VCN sizing mistakes, Cloud Guard gotchas, free tier specifics, OCI terminology confusion, and multi-AD patterns.
60compute-management
Use when launching OCI compute instances, troubleshooting out-of-capacity or boot failures, optimizing compute costs, or handling instance lifecycle. Covers shape selection, capacity planning, service limits, and production incident resolution.
58infrastructure-as-code
Use when writing Terraform for OCI, troubleshooting provider errors, managing state files, or implementing Resource Manager stacks. Covers terraform-provider-oci gotchas, resource lifecycle anti-patterns, state management mistakes, authentication issues, and OCI Landing Zones.
51