oci-developer-services
/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.
- Author
- adibirzu ↗
- Repository
- oci-skills ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 6
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 5
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- First decisions
- Routing
- Workflow
- Common multi-step flows
- Command contract
- Failure discrimination
- Validation and evidence
- Expected output
- Official documentation
SKILL.md preview
--- name: oci-developer-services description: >- 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. --- # OCI Developer Services Default API gateways, build runners, target environments, and workloads to private networking. Make public exposure an explicit reviewed requirement. Apply the shared [skill entrypoint quality standard](../../references/skill-quality-standard.md): decide the owning surface first, discriminate failures before changing a pipeline, and report evidence at its actual verification class. ## First decisions Resolve the source owner, artifact type and immutable identity, delivery target, ingress audience, deployment strategy, rollback target, secrets path, Terraform owner, and acceptance canaries. Separate platform creation from a release: a project, pipeline, or deployment resource in `ACTIVE` state does not prove that the intended artifact reached a healthy data plane. ## Routing | Surface | Owner | |---|---| | DevOps project, repository/connection, build/deploy pipeline, artifact, API Gateway, Container Instance, OCIR delivery | This skill | | OKE environment, manifest, rollout, ingress, or Kubernetes health | **oci-oke-admin** | | Function application/runtime, Event, Queue, Streaming, or DLQ | **oci-events-functions** | | VCN, subnet, NSG, DNS, certificate, generic load balancer, or compute target | **oci-networking-compute** | | Durable HCL and state ownership | **oci-terraform-authoring** | | Vulnerability, provenance, policy, or release-security decision | **oci-security-compliance** | ## Workflow 1. 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. 2. Check service limits, IAM for both operators and resource principals, subnet/NSG reachability, log availability, and target health. 3. Author durable resources with **oci-terraform-authoring**. Use exact wrapper-routed CLI plans for inspection or unsupported/recovery operations. 4. Keep source connection tokens, image-pull credentials, and deploy secrets in Vault; reference them from DevOps or runtime principals. 5. 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. 6. Deploy with a canary or blue-green stage plus automatic rollback. 7. Verify pipeline state, target health, Cloud Guard/WAF posture, logs, alarms, and the user-visible route. Exercise rollback before production. Read [developer-services.md](../../references/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`. ## Failure discrimination - A successful build proves artifact production, not deployment, target health, route reachability, or release acceptance. Follow the artifact digest through every deployment stage and target. - Distinguish source-connection authentication, build-runner network access, artifact-repository authorization, deploy principal IAM, target health, and API route/auth policy. Do not “fix IAM” for an unproven network or target issue. - A pipeline waiting on approval is not failed; a deployment stage marked successful with an unhealthy canary is not accepted. - A `404` at the gateway can mean route mismatch, deployment selection, upstream absence, or authorization masking. Verify the gateway deployment and backend independently before changing exposure. ## Validation and evidence Validate build/deploy specifications and command plans offline; lint CLI plans with `oci_cli_lint.py`. Record the immutable artifact digest, provenance/SBOM result, pipeline and stage states, target revision, logs/alarms, and work-request outcome. Then run one authenticated positive canary, one intended unauthenticated or unauthorized negative canary, and a last-known-good rollback/redeployment exercise. Classify those separately as local, provider, data-plane, security, and release evidence. ## 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](https://docs.oracle.com/en-us/iaas/Content/devops/using/devops_overview.htm) · [DevOps build specifications](https://docs.oracle.com/en-us/iaas/Content/devops/using/build_specs.htm) · [API Gateway](https://docs.oracle.com/en-us/iaas/Content/APIGateway/Concepts/apigatewayconcepts.htm) · [Container Instances](https://docs.oracle.com/en-us/iaas/Content/container-instances/overview-of-container-instances.htm) · [Container Registry](https://docs.oracle.com/en-us/iaas/Content/Registry/home.htm). Full list in the [developer-services reference](../../references/developer-services.md). **Open Knowledge Format grounding** - every doc link here is registered and liveness-checked in the [oracle-docs.md index](../../references/oracle-docs.md) (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.
Files in this package (6)
- SKILL.md 7 KB
- agents/openai.yaml 1 KB
- assets/terraform/private-platform/.terraform.lock.hcl 1 KB
- assets/terraform/private-platform/main.tf 2 KB
- assets/terraform/private-platform/variables.tf 1 KB
- assets/terraform/private-platform/versions.tf 1 KB
Versions
The database has no other skills named oci-developer-services.
Database snapshot: 13.11.2026 · package version 60f819944a76 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 85oracle-oci-specialist
Oracle Cloud Infrastructure — compute, networking, storage, databases, security, DevOps pipelines, Container Engine (OKE), Functions, Streaming, AI services. Trigger on: OCI, Oracle Cloud, OKE, OCI Compute, OCI Networking, OCI Object Storage, OCI IAM, OCI DevOps, OCI Functions,… - 100oraclecloud-deploy-integration
Deploy containers to OCI using OKE (Kubernetes) or Container Instances. Use when deploying applications to Oracle Cloud, pushing images to OCIR, or configuring OKE clusters. Trigger with "oraclecloud deploy", "oci kubernetes", "oke deploy", "oci container instances", "oracle… - 90oci-product-development
Compose secure OCI platform bundles for five product-development golden paths: API Gateway with Functions, Container Instances applications, OKE applications, Queue or Streaming event workers, and ADB-backed services. Use when a user asks to design, scaffold, or deploy an OCI… - 87oci
Oracle Cloud Infrastructure guidance for designing, operating, and troubleshooting OCI services, including OCI Kubernetes Engine (OKE), OCI Internet of Things Platform, OCI Functions deployment and troubleshooting, OCI Exadata Database Service Terraform configuration, OCI IAM… - 100oci-administrator
Default router for tenancy-agnostic Oracle Cloud Infrastructure engineering. Use for OCI administration, audit, security, IAM, Bastion, networking, compute, OKE, observability, storage, disaster recovery, Base Database, Exadata, DBM/OPSI, ADB, data platforms, OS Management Hub,… - 100oci
Oracle Cloud Infrastructure guidance for designing, operating, and troubleshooting OCI services, including OCI Kubernetes Engine (OKE), OCI Internet of Things Platform, OCI Functions deployment and troubleshooting, and Enterprise AI workflows for OCI Generative AI models,…