Oci developer services

Skill adibirzu/oci-skills/skills/oci-developer-services

Design, provision, deliver, inspect, and roll back OCI developer platforms: DevOps projects, code repositories and external connections, build pipelines/specifications, artifacts, environments, deployment pipelines and triggers, API Gateway, Container Instances, Artifact Registry, and OCIR delivery. Use for OCI CI/CD, private APIs, container deployments, blue-green or canary releases, and DevOps-to-OKE/Functions/instance-group targets. Hand off runtime ownership to the matching OKE, Functions, networking, or Terraform skill.From its SKILL.md

Install

npx -y skills add adibirzu/oci-skills --skill oci-developer-services

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.9 KB, as published. Nobody here has run it

OCI Developer Services

Default API gateways, build runners, target environments, and workloads to private networking. Make public exposure an explicit reviewed requirement.

Workflow

Preflight the named context (./scripts/oci_preflight.sh -c "$COMPARTMENT_OCID") and read existing resources by display name. Stop if the resolved tenancy/compartment does not match the intended target.
Check service limits, IAM for both operators and resource principals, subnet/NSG reachability, log availability, and target health.
Author durable resources with oci-terraform-authoring. Use exact wrapper-routed CLI plans for inspection or unsupported/recovery operations.
Keep source connection tokens, image-pull credentials, and deploy secrets in Vault; reference them from DevOps or runtime principals.
Build immutable artifacts, attach provenance/SBOM evidence, and apply the oci-security-compliance release gate. OCI DevOps ADM vulnerability audits support Maven builds; hand off other ecosystems to an approved scanner rather than claiming coverage.
Deploy with a canary or blue-green stage plus automatic rollback.
Verify pipeline state, target health, Cloud Guard/WAF posture, logs, alarms, and the user-visible route. Exercise rollback before production.

Read developer-services.md for detailed flows, ownership, IAM, network, logging, and rollback checks. Reuse assets/terraform/private-platform/ for provider-schema-validated private DevOps project, API Gateway, and Container Instance resources; materialize only the components selected by the design.

Common multi-step flows

Request	Sequence
DevOps CI/CD	quota/IAM/network/log checks → project → repository/connection → build pipeline/spec → artifact → environment → deployment pipeline → trigger → canary → verify/rollback
API Gateway to Function	private regional subnet → gateway → function-principal IAM → deployment spec from file → logs/rate/auth policy → invoke/verify; Function runtime belongs to oci-events-functions
Container Instance	image/artifact → Vault pull secret → private subnet/NSG → container instance → logs/metrics → health → rollback to immutable image
OKE delivery	DevOps project/pipeline here → OKE environment and rollout in oci-oke-admin
Function delivery	DevOps project/pipeline here → application/function lifecycle in oci-events-functions
Instance-group delivery	pipeline here → compute/network target in oci-networking-compute

Command contract

Query installed command shapes with ../../scripts/oci_cli_help.py --json <path>.
Store each read/action/verification/rollback plan as JSON and lint it with ../../scripts/oci_cli_lint.py.
Put nested payloads and credentials in a temporary 0600 file, pass file://..., and delete it in a trap/finally block.
Run mutations through run_action --risk <additive|in-place|credential|destructive> --compartment <COMPARTMENT_OCID> --description "<...>" -- oci_cli ... (honors OCI_SKILLS_DRY_RUN=true for a no-op preview). Deployment triggers, rollbacks, and any resource deletion additionally require explicit confirm.

Expected output

Report the owner of every component, quota/IAM/network/log checks, artifact identity, rollout strategy, exact verification, and rollback result. Do not expose endpoints, namespaces, image-pull tokens, or connection credentials.

Official documentation

OCI DevOps · DevOps build specifications · API Gateway · Container Instances · Container Registry. Full list in the developer-services reference.

Open Knowledge Format grounding - every doc link here is registered and liveness-checked in the oracle-docs.md index (the pack's single source of truth). When extending this skill, cite the most specific official page through that index; the non-official MCP gateway is never a source of truth.