oci-cli
Skill8 starsChanged 6 months agoApache-2.0View on GitHub
Use the correct Oracle Cloud Infrastructure CLI (oci) profile and region when running OCI commands based on the target environment.
- Installs packages
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
When running oci commands, always pass the --profile flag based on the target environment, and specify the region explicitly.
- Very specific: line 12
Update the profile map below with your OCI CLI profile names as configured in ~/.oci/config:
- Very specific: line 23
Always pass --region <your-default-region> unless the user specifies a different region.
- Distinctive: line 27
If not already authenticated, inform the user that setup is required and ask them to complete the following steps manually.
- Very specific: line 83
Always specify --profile explicitly — never rely on the DEFAULT profile in ~/.oci/config.
- Very specific: line 84
Always specify --region explicitly — never rely on the default region.
- Distinctive: line 85
If the target environment is unclear, ask the user before running the command.
- Distinctive: line 86
NEVER run any command in the "Never run" table above without explicit user instruction — a human must execute these, especially against …
- Very specific: line 87
NEVER read or output the contents of ~/.oci/config, private key files (.pem), or any credential value.
- Very specific: line 88
If unsure which tenancy/compartment a profile belongs to, run oci iam compartment list --profile <profile> to verify before proceeding.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Oracle Cloud Infrastructure (OCI) CLI Skill
When running oci commands, always pass the --profile flag based on the target environment, and specify the region explicitly.
Configuration
Update the profile map below with your OCI CLI profile names as configured in ~/.oci/config:
| Environment | Profile | Compartment OCID |
| Production | <your-prod-profile> | <your-prod-compartment-ocid> |
| Staging / Non-Prod | <your-nonprod-profile> | <your-nonprod-compartment-ocid> |
Default Region
Set your default region here: <your-default-region> (e.g. us-ashburn-1, eu-frankfurt-1).
Always pass --region <your-default-region> unless the user specifies a different region.
Prerequisites (one-time setup by user)
If not already authenticated, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself.
brew install oci-cli
oci setup config
oci iam region list --profile <your-profile>Command Format
oci <service> <resource> <action> --profile <profile> --region <region> [--compartment-id <compartment-ocid>] [options]Examples
# Production
oci compute instance list --profile <your-prod-profile> --region <your-default-region> --compartment-id <your-prod-compartment-ocid>
# Staging / Non-Prod
oci compute instance list --profile <your-nonprod-profile> --region <your-default-region> --compartment-id <your-nonprod-compartment-ocid>Available Commands
Read-only (safe, no confirmation needed)
| Command pattern | Description |
oci * list | List any resource type |
oci * get | Get details of a resource |
oci iam region list | List available regions |
oci iam compartment list | List compartments |
oci os object list | List Object Storage bucket contents |
Mutating operations (confirm with user before running)
| Command pattern | Description |
oci * create | Create a new resource |
oci * update | Update an existing resource |
oci compute instance launch | Launch a new compute instance |
Never run — requires explicit human approval
| Command pattern | Reason |
oci * delete | Irreversible resource deletion |
oci compute instance terminate | Irreversibly terminates a compute instance |
oci iam policy delete / oci iam policy update | Alters access control, security-sensitive |
oci compute instance action --action STOP/RESET | Disrupts running workloads |
oci db database delete | Irreversibly destroys a database |
Rules
- Always specify
--profileexplicitly — never rely on theDEFAULTprofile in~/.oci/config. - Always specify
--regionexplicitly — never rely on the default region. - If the target environment is unclear, ask the user before running the command.
- NEVER run any command in the "Never run" table above without explicit user instruction — a human must execute these, especially against production.
- NEVER read or output the contents of
~/.oci/config, private key files (.pem), or any credential value. - If unsure which tenancy/compartment a profile belongs to, run
oci iam compartment list --profile <profile>to verify before proceeding.
In this repository54 other files it gives its agents.
- alibabacloud-cliSkill
- ansible-cliSkill
- appdynamics-cliSkill
- argocd-cliSkill
- aws-cliSkill
- aws-cloudwatch-cliSkill
- azure-cliSkill
- bash-lintingSkill
- betterstack-cliSkill
- bitbucket-cliSkill
- chef-cliSkill
- code-reviewSkill
- commit-codeSkill
- create-dockerfileSkill
- create-terraform-helm-upgrade-planSkill
- datadog-cliSkill
- digitalocean-cliSkill
- dockerfile-lintingSkill
- dynatrace-cliSkill
- elasticsearch-cliSkill
- gcp-cliSkill
- github-cliSkill
- gitlab-cliSkill
- go-lintingSkill
- grafana-cliSkill
- grafana-loki-cliSkill
- graylog-cliSkill
- helm-cliSkill
- hetzner-cliSkill
- huaweicloud-cliSkill
- jaeger-cliSkill
- jenkins-cliSkill
- jira-and-confluence-cliSkill
- kibana-cliSkill
- kubernetes-cliSkill
- loggly-cliSkill
- maintenance-check-aws-eksSkill
- maintenance-create-ticket-on-jiraSkill
- ms-teams-cliSkill
- mysql-cliSkill
- newrelic-cliSkill
- packer-cliSkill
- papertrail-cliSkill
- postgresql-cliSkill
- prometheus-cliSkill
- python-lintingSkill
- rollbar-cliSkill
- salesforce-cliSkill
- sentry-cliSkill
- slack-cliSkill
- splunk-cliSkill
- terraform-cliSkill
- terraform-lintingSkill
- vault-cliSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.