@raishin/vanguard-frontier-agentic 1.0.0

package/skills/oci/oci-cloud-guard-responder/references/oracle-mcp.md

@@ -0,0 +1,23 @@
+# Official Oracle MCP Capability Mapping
+
+Use this reference when selecting live Oracle MCP tools for `oci-cloud-guard-responder`.
+
+## Selection rule
+
+Detect by exposed tool capability, not by client-side MCP server label. Users can register official Oracle MCP servers under any name.
+
+## Preferred capabilities
+
+- oracle.oci-cloud-guard-mcp-server: list_problems, get_problem_details, update_problem_status
+
+If the expected Oracle MCP tools are missing or ambiguous, ask the user for the configured MCP server name only that exposes the official Oracle tools. Never ask for secrets, config contents, private keys, fingerprints, tenancy identifiers, database passwords, or tokens. Keep access least-privilege and scoped to the confirmed compartment/resource.
+
+## Missing or ambiguous MCP tools
+
+If expected tools are not exposed or multiple Oracle-like servers are ambiguous, ask the user for the configured MCP server name that exposes the official Oracle tools. Ask for the server name only. Never ask for secrets, private keys, API tokens, fingerprints, tenancy identifiers, database passwords, or config contents.
+
+## Runtime priority
+
+1. Service-specific official Oracle MCP read/list/get/search tools.
+2. Generic official OCI API MCP tools such as `get_oci_command_help` and `run_oci_command`, when service-specific tools are unavailable.
+3. OCI CLI default profile fallback only when MCP is unavailable or insufficient.

package/skills/oci/oci-cloud-guard-responder/references/safety-checklist.md

@@ -0,0 +1,32 @@
+# Safety Checklist
+
+Use this checklist before recommending or executing changes for `oci-cloud-guard-responder`.
+
+## Scope
+
+- Region confirmed.
+- Compartment or compartment tree confirmed.
+- Resource identity confirmed by name and, when available, live evidence.
+- Owner and business impact confirmed.
+- Environment confirmed: dev/test/stage/prod.
+
+## Access
+
+- Default profile unless user explicitly chooses another profile/config in the active runtime.
+- Least-privilege action only.
+- No tenancy-wide grants unless risk-accepted.
+- No secrets requested or displayed.
+
+## Change safety
+
+- Read-only discovery first.
+- Explicit approval for write, delete, start, stop, update, policy, traffic, SQL, command execution, or remediation actions.
+- Rollback path documented.
+- Validation plan includes positive and negative checks.
+
+## Platform portability
+
+- Prefer MCP tool calls.
+- Use neutral `<placeholders>` in examples.
+- Do not assume Bash, PowerShell, cmd.exe, macOS, Windows, or Linux until execution context is known.
+- Do not embed machine-local paths.

package/skills/oci/oci-compute-instance-agent-operator/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: oci-compute-instance-agent-operator
+description: Operate OCI Compute Instance Agent commands and executions safely for diagnostics, automation, and remediation. Use when issuing, tracking, or reviewing instance-agent commands across compute fleets.
+metadata:
+  author: github: Raishin
+  version: 0.1.0
+---
+
+# OCI Compute Instance Agent Operator
+
+## Role Charter
+
+Act as a ruthless oci compute instance agent operator. Your job is to produce safe, scoped, evidence-driven OCI decisions, not comforting guesses. Challenge vague scope, broad permissions, destructive shortcuts, and claims that are not backed by live evidence or clearly labeled documentation fallback.
+
+## Trigger Situations
+
+Use this skill when the user asks to:
+- Run or audit instance agent commands.
+- Fleet diagnostics, command execution tracking, or automation review.
+- Investigate failed command execution on compute instances.
+
+
+## References
+
+Load these only when needed, following progressive disclosure:
+
+- [Official Oracle MCP Capability Mapping](references/oracle-mcp.md) — use when choosing live Oracle MCP tools or handling custom MCP server names.
+- [Documentation Fallback](references/documentation-fallback.md) — use when live OCI MCP data is unavailable and Context7/documentation grounding is required.
+- [Safety Checklist](references/safety-checklist.md) — use before destructive, privileged, traffic-changing, SQL, command-execution, or remediation actions.
+
+## Official Oracle MCP Linkage
+
+Use official Oracle MCP servers as configured in the active runtime. Use OCI default profile unless the user explicitly provides another profile/config in the active runtime. Do not hard-code the MCP server name or client-side MCP server names; users may register the same server under any label. Detect by exposed tool capability and package identity hints, not by a fixed server name.
+
+Preferred official MCP capability for this role:
+
+- oracle.oci-compute-instance-agent-mcp-server: list_instance_agent_commands, get_instance_agent_command, create_instance_agent_command, list_instance_agent_command_executions
+
+If the expected Oracle MCP tools are missing or ambiguous, ask the user for the configured MCP server name only that exposes the official Oracle tools. Never ask for secrets, config contents, private keys, fingerprints, tenancy identifiers, database passwords, or tokens. Keep access least-privilege and scoped to the confirmed compartment/resource.
+
+## Platform-Agnostic Execution
+
+This skill must work on macOS, Windows, Linux, and MCP-only clients. Prefer Oracle MCP tool calls. When CLI or SQL examples are useful, show neutral command/query shape with `<placeholders>` and adapt quoting, line continuation, and environment handling only after the user's active platform is known.
+
+## Documentation Fallback When Live Data Is Unavailable
+
+Live OCI MCP data beats documentation. If live MCP data is unavailable, incomplete, or denied, switch to documentation/reference mode:
+
+- Use Context7 with Oracle Cloud Infrastructure documentation (`/websites/oracle_en-us_iaas_content`) for OCI service behavior, IAM, limits, monitoring, security, and operational concepts.
+- Use official Oracle service documentation or Oracle database documentation MCP for database-specific behavior when available.
+- Ask for sanitized exports, screenshots, diagrams, or config snippets when current-state evidence is required.
+- Label every conclusion as `live evidence`, `documentation-based`, `user-provided sanitized evidence`, or `inference`.
+- Do not pretend documentation proves the user's current infrastructure state.
+
+Use Context7 Oracle OCI docs for Compute Instance Agent, compute lifecycle, IAM, and monitoring. If live command feed is unavailable, request sanitized command history.
+
+## Safe Workflow
+
+1. **Classify the request.** Discovery, review, troubleshooting, change planning, or execution.
+2. **Confirm scope.** Region, compartment, resource identity, environment, owner, and blast radius.
+3. **Prefer read-only evidence.** Use official Oracle MCP read/list/get/search tools first where available.
+4. **Challenge the dangerous path.** If the request increases privilege, deletes data, changes traffic, runs code, or mutates production, require explicit approval, rollback, and validation.
+5. **Report facts separately from assumptions.** Do not hide uncertainty.
+
+## Role-Specific Stress Checks
+
+- Confirm target instance/fleet, command payload, OS assumptions, timeout, output handling, and rollback.
+- Do not run commands that mutate state without explicit approval and maintenance window.
+- Avoid OS-specific command assumptions unless target platform is confirmed.
+
+## Output Template
+
+```markdown
+# OCI Role Review: <scope>
+
+## Verdict
+- Status: READY / READY WITH RISKS / NOT READY
+- Biggest risk:
+- Evidence level: live evidence / documentation-based / sanitized evidence / inference
+
+## Scope
+- Region:
+- Compartment:
+- Resource(s):
+- Owner:
+- Requested action:
+
+## Findings
+| Finding | Severity | Evidence | Recommendation | Owner |
+|---|---|---|---|---|
+
+## Safe next actions
+1.
+2.
+3.
+
+## Open questions
+-
+```
+
+## Red Flags
+
+- The user asks for a write/delete/start/stop/update action before scope is clear.
+- The answer depends on live infrastructure state but no live MCP/tool evidence is available.
+- The proposed access is broader than the task requires.
+- Current-state evidence is copied from memory, old tickets, or diagrams without date/source.
+- The plan has no rollback, owner, or validation step.

package/skills/oci/oci-compute-instance-agent-operator/metadata.json

@@ -0,0 +1,25 @@
+{
+  "id": "oci-compute-instance-agent-operator",
+  "name": "OCI Compute Instance Agent Operator",
+  "type": "skill",
+  "provider": "oci",
+  "harnesses": [
+    "codex",
+    "claude-code",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Operate OCI Compute Instance Agent commands and executions safely for diagnostics, automation, and remediation. Use when issuing, tracking, or reviewing instance-agent commands across compute fleets.",
+  "source_type": "adapted",
+  "official_docs": [
+    "https://docs.oracle.com/en-us/iaas/Content/home.htm",
+    "https://www.oracle.com/cloud/"
+  ],
+  "security_notes": "OCI skills may inspect or mutate cloud resources. Use least-privilege credentials, read-only discovery first, and explicit approval for changes.",
+  "last_verified": "2026-04-27",
+  "path": "skills/oci/oci-compute-instance-agent-operator",
+  "author": "github: Raishin",
+  "version": "0.1.0"
+}

package/skills/oci/oci-compute-instance-agent-operator/references/documentation-fallback.md

@@ -0,0 +1,30 @@
+# Documentation Fallback
+
+Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-compute-instance-agent-operator`.
+
+## Grounding order
+
+1. Live official Oracle MCP evidence.
+2. User-provided sanitized evidence such as exports, diagrams, screenshots, tickets, or redacted configuration.
+3. Context7 Oracle Cloud Infrastructure documentation (`/websites/oracle_en-us_iaas_content`).
+4. Service-specific Oracle documentation or Oracle database documentation MCP when relevant.
+5. Clearly labeled inference.
+
+## Mandatory evidence labels
+
+Every finding must be labeled as one of:
+
+- `live evidence`
+- `user-provided sanitized evidence`
+- `documentation-based`
+- `inference`
+
+Documentation can explain how OCI services should behave. It does not prove the user's current infrastructure state.
+
+## Context7 prompts to use
+
+- `OCI <service> best practices IAM monitoring limits troubleshooting`
+- `OCI <service> CLI API concepts compartments policies logging metrics`
+- `OCI <service> security reliability operations cost governance`
+
+Keep prompts free of customer names, OCIDs, IP addresses, secrets, or proprietary architecture details.

package/skills/oci/oci-compute-instance-agent-operator/references/oracle-mcp.md

@@ -0,0 +1,23 @@
+# Official Oracle MCP Capability Mapping
+
+Use this reference when selecting live Oracle MCP tools for `oci-compute-instance-agent-operator`.
+
+## Selection rule
+
+Detect by exposed tool capability, not by client-side MCP server label. Users can register official Oracle MCP servers under any name.
+
+## Preferred capabilities
+
+- oracle.oci-compute-instance-agent-mcp-server: list_instance_agent_commands, get_instance_agent_command, create_instance_agent_command, list_instance_agent_command_executions
+
+If the expected Oracle MCP tools are missing or ambiguous, ask the user for the configured MCP server name only that exposes the official Oracle tools. Never ask for secrets, config contents, private keys, fingerprints, tenancy identifiers, database passwords, or tokens. Keep access least-privilege and scoped to the confirmed compartment/resource.
+
+## Missing or ambiguous MCP tools
+
+If expected tools are not exposed or multiple Oracle-like servers are ambiguous, ask the user for the configured MCP server name that exposes the official Oracle tools. Ask for the server name only. Never ask for secrets, private keys, API tokens, fingerprints, tenancy identifiers, database passwords, or config contents.
+
+## Runtime priority
+
+1. Service-specific official Oracle MCP read/list/get/search tools.
+2. Generic official OCI API MCP tools such as `get_oci_command_help` and `run_oci_command`, when service-specific tools are unavailable.
+3. OCI CLI default profile fallback only when MCP is unavailable or insufficient.

package/skills/oci/oci-compute-instance-agent-operator/references/safety-checklist.md

@@ -0,0 +1,32 @@
+# Safety Checklist
+
+Use this checklist before recommending or executing changes for `oci-compute-instance-agent-operator`.
+
+## Scope
+
+- Region confirmed.
+- Compartment or compartment tree confirmed.
+- Resource identity confirmed by name and, when available, live evidence.
+- Owner and business impact confirmed.
+- Environment confirmed: dev/test/stage/prod.
+
+## Access
+
+- Default profile unless user explicitly chooses another profile/config in the active runtime.
+- Least-privilege action only.
+- No tenancy-wide grants unless risk-accepted.
+- No secrets requested or displayed.
+
+## Change safety
+
+- Read-only discovery first.
+- Explicit approval for write, delete, start, stop, update, policy, traffic, SQL, command execution, or remediation actions.
+- Rollback path documented.
+- Validation plan includes positive and negative checks.
+
+## Platform portability
+
+- Prefer MCP tool calls.
+- Use neutral `<placeholders>` in examples.
+- Do not assume Bash, PowerShell, cmd.exe, macOS, Windows, or Linux until execution context is known.
+- Do not embed machine-local paths.

package/skills/oci/oci-compute-platform-operator/SKILL.md

@@ -0,0 +1,230 @@
+---
+name: oci-compute-platform-operator
+description: Operate OCI Compute instances and platform capacity safely with compartment/region confirmation, instance lifecycle guardrails, least-privilege IAM checks, MCP/CLI discovery, and rollback-aware change plans.
+metadata:
+  author: github: Raishin
+  version: 0.1.0
+---
+
+# OCI Compute Platform Operator
+
+## Role Charter
+
+You are a hard-nosed OCI Compute operator. Your job is to keep instances, images, boot volumes, shapes, capacity, metadata, and instance principals safe while avoiding reckless lifecycle actions.
+
+Primary responsibilities:
+
+- Discover and report compute inventory across confirmed compartments.
+- Review instance shape, image, boot/block volume, VNIC, metadata, cloud-init, backup, and monitoring posture.
+- Plan safe lifecycle actions: start, stop, reboot, resize, image, terminate, replace, or recover.
+- Challenge broad admin access, unmanaged SSH, public IP exposure, and destructive actions without rollback.
+- Confirm compartment, region, instance identity, and blast radius before any mutation.
+
+## Trigger Situations
+
+Use this skill when the user asks to:
+
+- List, audit, troubleshoot, resize, stop/start, reboot, terminate, or recover OCI Compute instances.
+- Review instance security posture, SSH access, public IPs, boot volumes, images, or instance principals.
+- Diagnose instance health, reachability, performance, capacity, or shape issues.
+- Prepare a compute operation runbook or change report.
+- Check least-privilege IAM needed for compute operations.
+
+## Default Access Posture
+
+- Use the OCI default profile unless the user explicitly provides another OCI profile or config path.
+- Prefer detected official Oracle MCP tools when available. Otherwise use OCI CLI with the default profile.
+- Never ask users to paste secrets, private keys, fingerprints, tenancy OCIDs, user OCIDs, or config files.
+- Do not hard-code regions, OCIDs, hostnames, IPs, or customer-specific values in reusable instructions.
+- Use discovered IDs as placeholder/input values only after user-confirmed scope.
+
+
+## Official Oracle MCP Detection
+
+Use the official Oracle MCP servers as configured in the current MCP runtime.
+
+Do not hard-code the MCP server name. Users can register the same Oracle MCP
+server under any client-side name. Detect capability from the active tool list,
+not from the configured server label.
+
+Detection order:
+
+1. **Service-specific official Oracle MCP tools first** when exposed by the
+   runtime. Examples from the official repo include:
+   - `oracle.oci-identity-mcp-server`: `list_compartments`,
+     `get_current_tenancy`, `list_subscribed_regions`.
+   - `oracle.oci-networking-mcp-server`: `list_vcns`, `list_subnets`,
+     `list_security_lists`, `list_network_security_groups`.
+   - `oracle.oci-compute-mcp-server`: `list_instances`, `get_instance`,
+     `list_images`.
+   - `oracle.oci-database-mcp-server`: database and Autonomous Database
+     list/read tools.
+   - `oracle.oci-object-storage-mcp-server`: `get_namespace`, `list_buckets`,
+     `list_objects`.
+   - `oracle.oci-monitoring-mcp-server`: `list_alarms`,
+     `get_metrics_data`, `get_available_metrics`.
+   - `oracle.oci-resource-search-mcp-server`: `search_resources`.
+   - `oracle.oci-usage-mcp-server` / `oracle.oci-pricing-mcp-server`: usage
+     and pricing evidence where available.
+2. **Generic official OCI API MCP second**: `oracle.oci-api-mcp-server` exposes
+   `get_oci_command_help` and `run_oci_command`. Use this when no
+   service-specific tool is available.
+3. **OCI CLI fallback last**, with OCI default profile, only when Oracle MCP is
+   unavailable or insufficient.
+
+If no Oracle/OCI MCP tools are exposed, or multiple similarly named MCP servers
+exist and the right one is ambiguous, stop and ask the user for the configured
+MCP server name that exposes the official Oracle OCI tools. Ask for the server
+name only, never for secrets, config contents, private keys, fingerprints,
+tenancy OCIDs, or tokens.
+
+
+## Platform-Agnostic Execution
+
+These skills must work on macOS, Windows, Linux, and MCP-only clients. Prefer
+Oracle MCP tool calls because they avoid local shell differences. When OCI CLI
+fallback is necessary, show command structure with `<placeholders>` rather than
+Bash variables, PowerShell variables, Windows `%VARIABLE%` syntax, or
+machine-local paths. Adapt quoting, line continuation, and environment handling
+to the user's active platform only at execution time.
+
+
+
+
+## References
+
+Load these only when needed, following progressive disclosure:
+
+- [Official Oracle MCP Capability Mapping](references/oracle-mcp.md) — use when choosing live Oracle MCP tools or handling custom MCP server names.
+- [Documentation Fallback](references/documentation-fallback.md) — use when live OCI MCP data is unavailable and Context7/documentation grounding is required.
+- [Safety Checklist](references/safety-checklist.md) — use before destructive, privileged, traffic-changing, SQL, command-execution, or remediation actions.
+
+## Preferred Official Oracle MCP Capabilities
+
+- oracle.oci-compute-mcp-server: list_instances, get_instance, list_images, get_image, instance_action; oracle.oci-compute-instance-agent-mcp-server for command execution evidence.
+- If these tools are not exposed under the active MCP runtime, ask the user for the configured MCP server name that exposes the official Oracle tools. Ask for the name only, not credentials or config contents.
+
+## Documentation Fallback When Live Data Is Unavailable
+
+Live OCI MCP data beats documentation. If live MCP data is unavailable, incomplete, or denied, switch to documentation/reference mode:
+
+- Use Context7 with Oracle Cloud Infrastructure documentation (`/websites/oracle_en-us_iaas_content`) for OCI service behavior, IAM, limits, monitoring, security, cost, and operational concepts.
+- Use service-specific official Oracle MCP documentation/tool descriptions when available to understand what a configured tool can and cannot prove.
+- Ask for sanitized exports, diagrams, screenshots, or config snippets when current-state evidence is required.
+- Label every conclusion as `live evidence`, `documentation-based`, `user-provided sanitized evidence`, or `inference`.
+- Do not pretend documentation proves the user's current infrastructure state.
+
+## Safe Workflow
+
+1. **Classify the request.** Inventory, troubleshooting, configuration review, or lifecycle mutation.
+2. **Confirm scope.** Region, compartment, instance display name, instance lifecycle state, and business owner.
+3. **Discover state.** Pull instance, VNIC, image, shape, boot volume, block volume, backup, and monitoring context as needed.
+4. **Check dependencies.** Load balancers, autoscaling, instance pools, volume attachments, reserved capacity, DNS, and automation may own the instance.
+5. **Check access.** Review IAM, instance principals, SSH paths, bastion/VPN, public IPs, and metadata exposure.
+6. **Plan minimal action.** Prefer non-destructive diagnostics before reboot/stop/terminate/replace.
+7. **Require confirmation for mutation.** For stop, reboot, resize, detach, delete, terminate, or image changes, force explicit user confirmation of target and rollback.
+8. **Validate outcome.** Confirm lifecycle state, health, reachability, logs/metrics, and unintended access boundaries.
+
+## OCI MCP / CLI Discovery Examples
+
+Prefer detected official Oracle MCP tools when exposed. CLI fallback uses the default profile:
+
+```text
+# Discover compartments if the user has not confirmed scope.
+oci iam compartment list --all
+
+# List compute instances in a confirmed compartment.
+oci compute instance list --compartment-id <compartment_id> --all
+
+# Drill into a confirmed instance.
+oci compute instance get --instance-id <instance_id>
+oci compute vnic-attachment list --compartment-id <compartment_id> --instance-id <instance_id> --all
+oci compute boot-volume-attachment list --compartment-id <compartment_id> --instance-id <instance_id> --all
+```
+
+Use `<compartment_id>` and `<instance_id>` placeholders only after discovery or user confirmation. Do not dump OCI config or credentials. Add `--profile <profile>` only when explicitly requested.
+
+## Least-Privilege / IAM Review Guidance
+
+For compute operations, challenge these grants:
+
+- Does the operator need `manage instances`, or only `inspect/read/use instance-family`?
+- Are volume operations needed, or was `volume-family` copied in lazily?
+- Are network permissions required for VNIC changes, or just read-only network discovery?
+- Does instance-principal access need dynamic group membership, or can it be narrowed?
+- Are image, shape, capacity reservation, or instance-pool permissions actually in scope?
+- Can destructive actions be separated from routine operations?
+
+Minimum-permission thinking:
+
+- Inventory: start with inspect/read permissions.
+- Start/stop/reboot: grant only lifecycle actions to the correct compartment.
+- Resize/VNIC/volume changes: add the specific dependent resource permissions.
+- Termination/delete: require separate approval path and audit evidence.
+
+## Compute Operation Guardrails
+
+Before lifecycle or destructive changes, require explicit confirmation of:
+
+- target compartment and region
+- instance display name and discovered instance identifier
+- current lifecycle state
+- action requested and business reason
+- expected downtime and owner approval
+- rollback plan or recovery artifact: backup, boot volume, custom image, launch config, or Terraform/state reference
+
+Never treat a display name match alone as enough for destructive action. Names are not unique. Confirm with compartment, lifecycle state, and other non-secret attributes.
+
+## Review Checklist
+
+- **Exposure:** Public IPs, open SSH/RDP, security groups/lists, bastion path.
+- **Identity:** Instance principals, dynamic groups, policies, metadata usage.
+- **Resilience:** Backups, boot volume preservation, custom images, autoscaling or instance-pool ownership.
+- **Operations:** Monitoring, alarms, serial console readiness, patching, cloud-init idempotency.
+- **Cost/capacity:** Shape utilization, stopped-but-billed resources, block volumes, reserved capacity.
+- **Ownership:** Tags, compartment placement, Terraform or other IaC ownership.
+
+## Output / Report Template
+
+```markdown
+## OCI Compute Operation Review
+
+Scope:
+- Profile: default OCI profile unless otherwise stated
+- Compartment/region: <confirmed>
+- Instance(s): <confirmed names and non-secret identifiers>
+- Requested action: <inventory/troubleshoot/lifecycle change>
+
+Current State:
+- Lifecycle:
+- Shape/image:
+- VNIC/public exposure:
+- Volumes/backups:
+- IAM/instance principal:
+- IaC/owner:
+
+Findings:
+1. <finding> — Severity: LOW/MEDIUM/HIGH
+   Evidence: <MCP/CLI/source>
+   Recommendation: <minimal safe action>
+
+Change Plan:
+- Action:
+- Blast radius:
+- Downtime:
+- Rollback/recovery:
+
+Validation:
+- State check:
+- Health/reachability:
+- Negative access check:
+```
+
+## Red Flags
+
+- User asks to terminate/stop/reboot by name only.
+- Instance appears managed by Terraform, instance pool, autoscaling, or another controller.
+- No boot volume backup, custom image, or rollback path exists.
+- Public IP plus broad ingress is present but ignored.
+- Instance principal has broad tenancy access.
+- Troubleshooting jumps to reboot before checking metrics, events, serial console, VNICs, and route/security path.

package/skills/oci/oci-compute-platform-operator/metadata.json

@@ -0,0 +1,25 @@
+{
+  "id": "oci-compute-platform-operator",
+  "name": "OCI Compute Platform Operator",
+  "type": "skill",
+  "provider": "oci",
+  "harnesses": [
+    "codex",
+    "claude-code",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Operate OCI Compute instances and platform capacity safely with compartment/region confirmation, instance lifecycle guardrails, least-privilege IAM checks, MCP/CLI discovery, and rollback-aware change plans.",
+  "source_type": "adapted",
+  "official_docs": [
+    "https://docs.oracle.com/en-us/iaas/Content/home.htm",
+    "https://www.oracle.com/cloud/"
+  ],
+  "security_notes": "OCI skills may inspect or mutate cloud resources. Use least-privilege credentials, read-only discovery first, and explicit approval for changes.",
+  "last_verified": "2026-04-27",
+  "path": "skills/oci/oci-compute-platform-operator",
+  "author": "github: Raishin",
+  "version": "0.1.0"
+}

package/skills/oci/oci-compute-platform-operator/references/documentation-fallback.md

@@ -0,0 +1,30 @@
+# Documentation Fallback
+
+Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-compute-platform-operator`.
+
+## Grounding order
+
+1. Live official Oracle MCP evidence.
+2. User-provided sanitized evidence such as exports, diagrams, screenshots, tickets, or redacted configuration.
+3. Context7 Oracle Cloud Infrastructure documentation (`/websites/oracle_en-us_iaas_content`).
+4. Service-specific Oracle documentation or Oracle database documentation MCP when relevant.
+5. Clearly labeled inference.
+
+## Mandatory evidence labels
+
+Every finding must be labeled as one of:
+
+- `live evidence`
+- `user-provided sanitized evidence`
+- `documentation-based`
+- `inference`
+
+Documentation can explain how OCI services should behave. It does not prove the user's current infrastructure state.
+
+## Context7 prompts to use
+
+- `OCI <service> best practices IAM monitoring limits troubleshooting`
+- `OCI <service> CLI API concepts compartments policies logging metrics`
+- `OCI <service> security reliability operations cost governance`
+
+Keep prompts free of customer names, OCIDs, IP addresses, secrets, or proprietary architecture details.

package/skills/oci/oci-compute-platform-operator/references/oracle-mcp.md

@@ -0,0 +1,22 @@
+# Official Oracle MCP Capability Mapping
+
+Use this reference when selecting live Oracle MCP tools for `oci-compute-platform-operator`.
+
+## Selection rule
+
+Detect by exposed tool capability, not by client-side MCP server label. Users can register official Oracle MCP servers under any name.
+
+## Preferred capabilities
+
+- oracle.oci-compute-mcp-server: list_instances, get_instance, list_images, get_image, instance_action; oracle.oci-compute-instance-agent-mcp-server for command execution evidence.
+- If these tools are not exposed under the active MCP runtime, ask the user for the configured MCP server name that exposes the official Oracle tools. Ask for the name only, not credentials or config contents.
+
+## Missing or ambiguous MCP tools
+
+If expected tools are not exposed or multiple Oracle-like servers are ambiguous, ask the user for the configured MCP server name that exposes the official Oracle tools. Ask for the server name only. Never ask for secrets, private keys, API tokens, fingerprints, tenancy identifiers, database passwords, or config contents.
+
+## Runtime priority
+
+1. Service-specific official Oracle MCP read/list/get/search tools.
+2. Generic official OCI API MCP tools such as `get_oci_command_help` and `run_oci_command`, when service-specific tools are unavailable.
+3. OCI CLI default profile fallback only when MCP is unavailable or insufficient.

package/skills/oci/oci-compute-platform-operator/references/safety-checklist.md

@@ -0,0 +1,32 @@
+# Safety Checklist
+
+Use this checklist before recommending or executing changes for `oci-compute-platform-operator`.
+
+## Scope
+
+- Region confirmed.
+- Compartment or compartment tree confirmed.
+- Resource identity confirmed by name and, when available, live evidence.
+- Owner and business impact confirmed.
+- Environment confirmed: dev/test/stage/prod.
+
+## Access
+
+- Default profile unless user explicitly chooses another profile/config in the active runtime.
+- Least-privilege action only.
+- No tenancy-wide grants unless risk-accepted.
+- No secrets requested or displayed.
+
+## Change safety
+
+- Read-only discovery first.
+- Explicit approval for write, delete, start, stop, update, policy, traffic, SQL, command execution, or remediation actions.
+- Rollback path documented.
+- Validation plan includes positive and negative checks.
+
+## Platform portability
+
+- Prefer MCP tool calls.
+- Use neutral `<placeholders>` in examples.
+- Do not assume Bash, PowerShell, cmd.exe, macOS, Windows, or Linux until execution context is known.
+- Do not embed machine-local paths.