oci

Estrelas0

Forks0

Atualizado20 de junho de 2026 às 15:15

Use when working with Oracle Cloud Infrastructure via the OCI CLI, especially for session auth, budgets, quotas, networking, and compute operations. Read workspace AGENTS.md, if present, for workspace-specific tenancy and VPS state.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

roktas

roktas/home

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	oci
description	Use when working with Oracle Cloud Infrastructure via the OCI CLI, especially for session auth, budgets, quotas, networking, and compute operations. Read workspace AGENTS.md, if present, for workspace-specific tenancy and VPS state.
metadata	{"author":"https://github.com/roktas","version":"1.0.0","triggers":"OCI, Oracle Cloud, Oracle Cloud Infrastructure, oci CLI, budget, quota, VCN, compute instance","role":"specialist","scope":"operations","output-format":"command-oriented","related-skills":null}

OCI

Use this skill for Oracle Cloud Infrastructure CLI work. Read workspace AGENTS.md, if present, for tenancy, region, compartment, VPS, or other workspace-specific state. Read references/official-docs.md only when exact Oracle docs or command references matter.

Default Pattern

Use explicit config and session-token auth unless the workspace says otherwise:

oci <command> --config-file ~/.oci/config --profile SESSION --auth security_token

Validate auth before inferring resource state:

oci session validate --config-file ~/.oci/config --profile SESSION
oci session refresh --config-file ~/.oci/config --profile SESSION

If refresh is not enough, use oci session authenticate ... --no-browser, ask the user to open the printed URL and finish login, then return to the terminal flow.

Working Rules

Prefer read-only inspection before mutation.
Confirm profile, region, compartment, and resource OCID/name before write operations.
Treat terminate, delete, detach, resize, route, and security-list changes as destructive unless the user explicitly requested them.
Use JSON output for parsed data; prefer --query ... --raw-output for narrow extraction.
Prefer generated JSON input plus file://... over long inline JSON.
Prefer --wait-for-state when the command supports it.
Cite the command result or exact field behind conclusions about limits, budgets, networking, or compute.
If a networked OCI call hangs in a sandboxed agent environment, consider sandbox or network restrictions before treating it as an auth problem.

Operational Notes

Budgets are soft limits; they alert and do not stop resources. Quotas are the main creation and scale guardrail.
PAYG accounts still retain Always Free entitlements, but charges start when usage exceeds Always Free limits or paid resources are created.
For instance launch work, check the installed CLI's supported flags.
To relaunch across immutable network identity boundaries, preserve the boot volume, verify its OCID and preservation setting, terminate the old instance, then relaunch from --source-boot-volume-id.
Capacity can be transient for some shapes and availability domains; retry across availability domains when appropriate.

Mais deste repositório

mesmo repositório

humanizer

roktas/home

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.

2026-07-140

ruby

roktas/home

Use when working on Ruby code, gems, Rails-adjacent projects, Minitest or RSpec tests, Ruby packaging, Ruby style review, Ruby typing with RBI/RBS, modern Ruby syntax choices, or public API documentation with YARD.

2026-07-130

dotagents

roktas/home

Use when creating, placing, moving, reorganizing, or updating repository-local agent assets and artifacts that follow the dotagents layout under `.agents/`, including guides, skills, specs, tests, task state, logs, scratch files, or runtime state. Also use when deciding how `.agents/` relates to root project docs such as `PLAN.md`, `TODO.md`, `CHANGELOG.md`, `README.md`, and `AGENTS.md`.

2026-07-050

colon

roktas/home

Use when the user message starts with `:` to interpret prompt shortcuts such as `:commit`, `:co`, `:push`, `:pu`, `:ship`, `:sh`, `:opencode TEXT`, `:oc TEXT`, `:todo TEXT`, `:to TEXT`, `:ok NUMBER`, `:do NUMBER`, `:learn TEXT`, `:le TEXT`, `:close`, or `:cl`.

2026-06-240

bash

roktas/home

Use when editing, writing, or debugging Bash or POSIX shell scripts, shell-based automation, CLI wrappers, dotfiles, CI scripts, or when Bash style, safety, portability, or shell testing matter. Use when writing Bash code inside Markdown fenced code blocks. Always load this skill before writing or modifying any Bash code, even if the task seems straightforward — the skill catches subtle pitfalls that are easy to overlook.

2026-06-160

commits

roktas/home

Use when creating, editing, reviewing, or explaining git commit messages, commit scopes, changelog-friendly history, semantic-release compatibility, or Conventional Commits formatting. Always load this skill before preparing a commit message, even if only suggesting one.

2026-06-020

name	oci
description	Use when working with Oracle Cloud Infrastructure via the OCI CLI, especially for session auth, budgets, quotas, networking, and compute operations. Read workspace AGENTS.md, if present, for workspace-specific tenancy and VPS state.
metadata	{"author":"https://github.com/roktas","version":"1.0.0","triggers":"OCI, Oracle Cloud, Oracle Cloud Infrastructure, oci CLI, budget, quota, VCN, compute instance","role":"specialist","scope":"operations","output-format":"command-oriented","related-skills":null}

OCI

Default Pattern

Use explicit config and session-token auth unless the workspace says otherwise:

oci <command> --config-file ~/.oci/config --profile SESSION --auth security_token

Validate auth before inferring resource state:

oci session validate --config-file ~/.oci/config --profile SESSION
oci session refresh --config-file ~/.oci/config --profile SESSION

If refresh is not enough, use oci session authenticate ... --no-browser, ask the user to open the printed URL and finish login, then return to the terminal flow.

Working Rules

Prefer read-only inspection before mutation.
Confirm profile, region, compartment, and resource OCID/name before write operations.
Treat terminate, delete, detach, resize, route, and security-list changes as destructive unless the user explicitly requested them.
Use JSON output for parsed data; prefer --query ... --raw-output for narrow extraction.
Prefer generated JSON input plus file://... over long inline JSON.
Prefer --wait-for-state when the command supports it.
Cite the command result or exact field behind conclusions about limits, budgets, networking, or compute.
If a networked OCI call hangs in a sandboxed agent environment, consider sandbox or network restrictions before treating it as an auth problem.

Operational Notes

Budgets are soft limits; they alert and do not stop resources. Quotas are the main creation and scale guardrail.
PAYG accounts still retain Always Free entitlements, but charges start when usage exceeds Always Free limits or paid resources are created.
For instance launch work, check the installed CLI's supported flags.
To relaunch across immutable network identity boundaries, preserve the boot volume, verify its OCID and preservation setting, terminate the old instance, then relaunch from --source-boot-volume-id.
Capacity can be transient for some shapes and availability domains; retry across availability domains when appropriate.