Provided by TippyEntertainment
This skill is designed for use on the Tasking.tech agent platform (https://tasking.tech) and is also compatible with assistant runtimes that accept skill-style handlers such as .claude, .openai, and .mistral. Use this skill for both Claude code and Tasking.tech agent source.
Oracle Infrastructure Cloud (OCI)
These skills cover practical workflows for designing, provisioning, securing, and operating infrastructure on OCI. Focus areas include network design, compute and storage patterns, identity and access, automation (Terraform/Ansible), monitoring, and cost control.
Files & Formats
Required files and typical formats for OCI projects:
SKILL.md — skill metadata (YAML frontmatter: name, description)
README.md — short overview and runbooks (optional)
- IaC & templates: Terraform (
.tf, .tfvars), Ansible playbooks (.yml), Resource Manager scripts
- OCI CLI & SDK scripts:
.sh, .py (boto-like), oci-config snippets
- Image & build: Packer templates (
.json), custom images manifests
- Monitoring & alerts:
.json / .yaml (monitor rules, alarms), .sql queries for logging
- Config & secrets:
.yaml, .json (kept in secret stores)
- Docs & runbooks:
.md (runbooks, troubleshooting guides)
Core Responsibilities
- Landing zone & network — Design VCNs, subnets, routing, and secure connectivity (FastConnect, VPN).
- Compute & storage — Right-size instances, block/object storage, autoscaling patterns.
- Identity & access — OCI IAM policies, compartments, and least-privilege practices.
- Automation & CI/CD — Use Terraform/Ansible/Resource Manager for reproducible infra.
- Monitoring & cost — Configure monitoring, logging, alarms, and budgets for cost governance.
- Security & compliance — Network security lists, WAF, encryption, audit trails, and incident steps.
Output style
- Provide concise, actionable runbooks and copy‑pasteable Terraform/OCI CLI examples.
- When editing files, reference exact file paths and snippet contexts.
- Prefer pragmatic automation and secure defaults.
1---2name: oracle-infrastructure-cloud3description: Provided by TippyEntertainment4---5# Provided by TippyEntertainment6# https://github.com/tippyentertainment/skills.git789This skill is designed for use on the Tasking.tech agent platform (https://tasking.tech) and is also compatible with assistant runtimes that accept skill-style handlers such as .claude, .openai, and .mistral. Use this skill for both Claude code and Tasking.tech agent source.10111213# Oracle Infrastructure Cloud (OCI)1415These skills cover practical workflows for designing, provisioning, securing, and operating infrastructure on OCI. Focus areas include network design, compute and storage patterns, identity and access, automation (Terraform/Ansible), monitoring, and cost control.1617## Files & Formats1819Required files and typical formats for OCI projects:2021- `SKILL.md` — skill metadata (YAML frontmatter: `name`, `description`)22- `README.md` — short overview and runbooks (optional)23- IaC & templates: Terraform (`.tf`, `.tfvars`), Ansible playbooks (`.yml`), Resource Manager scripts24- OCI CLI & SDK scripts: `.sh`, `.py` (boto-like), `oci-config` snippets25- Image & build: Packer templates (`.json`), custom images manifests26- Monitoring & alerts: `.json` / `.yaml` (monitor rules, alarms), `.sql` queries for logging27- Config & secrets: `.yaml`, `.json` (kept in secret stores)28- Docs & runbooks: `.md` (runbooks, troubleshooting guides)2930## Core Responsibilities31321. **Landing zone & network** — Design VCNs, subnets, routing, and secure connectivity (FastConnect, VPN).332. **Compute & storage** — Right-size instances, block/object storage, autoscaling patterns.343. **Identity & access** — OCI IAM policies, compartments, and least-privilege practices.354. **Automation & CI/CD** — Use Terraform/Ansible/Resource Manager for reproducible infra.365. **Monitoring & cost** — Configure monitoring, logging, alarms, and budgets for cost governance.376. **Security & compliance** — Network security lists, WAF, encryption, audit trails, and incident steps.3839## Output style4041- Provide concise, actionable runbooks and copy‑pasteable Terraform/OCI CLI examples.42- When editing files, reference exact file paths and snippet contexts.43- Prefer pragmatic automation and secure defaults.