@raishin/vanguard-frontier-agentic 2.7.1 → 2.9.0

package/skills/oci/oci-dbtools-sql-analyst/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-dbtools-sql-analyst`.
-
-## 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.dbtools-mcp-server: list_dbtools_connection_tool, list_all_connections, get_dbtools_connection_by_name_tool, execute_sql_tool, get_table_info, list_tables, report tools; oracle.oracle-db-doc-mcp-server: search_oracle_database_documentation
-
-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-devops-container-platform-engineer/references/documentation-fallback.md

@@ -1,30 +0,0 @@
-# Documentation Fallback
-
-Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-devops-container-platform-engineer`.
-
-## 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-devops-container-platform-engineer/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-devops-container-platform-engineer`.
-
-## 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-registry-mcp-server: list_container_repositories, get_container_repo_details, create_container_repository, delete_container_repository; oracle.oci-cloud-mcp-server for DevOps APIs not covered by a dedicated server.
-- 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-exadata-platform-architect/references/compatibility-checklist.md

@@ -1,25 +0,0 @@
-# Exadata Compatibility Checklist
-
-## Database and platform compatibility
-
-- Confirm Oracle Database version, Grid Infrastructure version, RAC requirements, CDB/PDB layout, options/packs, and database software image strategy.
-- Validate application client compatibility: connection strings, SCAN, FAN/ONS, TLS, wallets, JDBC/ODP.NET versions, and failover behavior.
-- Validate storage and performance assumptions with evidence such as AWR/ASH, IOPS, throughput, latency, CPU, memory, interconnect, and cell offload indicators.
-
-## Deployment compatibility
-
-- Identify exact platform: OCI Dedicated Infrastructure, Exadata Cloud@Customer, Exascale, Oracle Database@Azure, Oracle Database@Google Cloud, or Oracle Database@AWS.
-- Confirm region/provider availability, capacity/quota, subscription/billing, support process, and IaC/API support.
-- Confirm network path between applications and database: VCN, VNet, VPC, FastConnect, VPN, interconnect, DNS, and security controls.
-
-## Operations compatibility
-
-- Backup destination and restore process are tested, not just configured.
-- Data Guard topology, switchover/failover runbook, observer/auto-failover assumptions, and RPO/RTO are documented.
-- Patching and maintenance windows are aligned across GI, DB homes, VM clusters, applications, and provider control planes.
-- IORM and consolidation rules exist for noisy-neighbor control.
-
-## Multicloud compatibility
-
-- The database may be Oracle-managed while the application lives in AWS, Azure, Google Cloud, OCI, or on-premises. Do not blur those responsibility boundaries.
-- Cross-cloud latency, egress, DNS, route propagation, identity, monitoring, and incident ownership are first-class design inputs.

package/skills/oci/oci-exadata-platform-architect/references/deployment-options.md

@@ -1,22 +0,0 @@
-# Exadata Deployment Options
-
-Use this reference when choosing an Exadata Database Service deployment pattern.
-
-## Deployment families
-
-| Family | Where it runs | Good fit | Watch-outs |
-|---|---|---|---|
-| Exadata Database Service on Dedicated Infrastructure | OCI region on Oracle-managed dedicated Exadata infrastructure | Highest Oracle database performance in OCI, RAC, consolidation, predictable database platform | Capacity planning, VM cluster design, network design, patching windows, backup/DR, licensing |
-| Exadata Database Service on Exascale Infrastructure | OCI and selected multicloud offers where available | Elastic Exadata-style consumption and simplified capacity model | Feature availability and operational semantics vary; verify current service docs and limits |
-| Exadata Cloud@Customer | Customer data center with Oracle-managed Exadata cloud infrastructure | Data residency, low latency to on-premises apps, cloud subscription model | Site readiness, physical capacity lead time, OCI control-plane connectivity, support demarcation |
-| Oracle Database@Azure | Oracle Exadata Database Service and Autonomous database services integrated with Azure regions where available | Azure app proximity and Azure operating model | Azure region availability, VNet/DNS/private connectivity, billing/support split, IaC path |
-| Oracle Database@Google Cloud | Exadata Database Service integrated with Google Cloud regions and Google Cloud interfaces where available | Google Cloud app proximity, Google Cloud networking/security consumption path | Exact offer matters: Dedicated, Exascale, Base Database, or Autonomous; verify Google/Oracle API responsibilities |
-| Oracle Database@AWS | Oracle database services integrated with AWS where available | AWS app proximity and AWS operating model | Region/offer maturity, VPC/DNS/private connectivity, capacity, support, and Terraform/provider coverage |
-
-## Non-negotiable design checks
-
-- VM cluster sizing: OCPU/ECPU equivalent, memory, local storage, DATA/RECO split, DB node count, and spare capacity.
-- Database topology: CDB/PDB layout, RAC services, Data Guard, backup destination, TDE/key ownership.
-- Network: client subnet, backup subnet, NSGs/security lists, SCAN/listener ports, DNS, routing, and cross-cloud latency.
-- Operations: maintenance windows, patch sequencing, node lifecycle, IORM, monitoring, incident owner, and support route.
-- Migration: source platform, endian/version compatibility, downtime budget, backup/restore, Data Pump, GoldenGate, ZDM, or app-level migration path.

package/skills/oci/oci-exadata-platform-architect/references/documentation-fallback.md

@@ -1,30 +0,0 @@
-# Documentation Fallback
-
-Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-exadata-platform-architect`.
-
-## Grounding order
-
-1. Live official Oracle MCP evidence.
-2. User-provided sanitized evidence such as exports, diagrams, screenshots, AWR summaries, 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 and Oracle Database services should behave. It does not prove the user's current infrastructure state, capacity, quota, regional availability, or provider-specific entitlement.
-
-## Context7 prompts to use
-
-- `OCI Autonomous Database Exadata deployment options Oracle Database at Azure AWS Google Cloud Cloud Customer compatibility`
-- `OCI database multicloud networking private endpoint Data Guard backup Recovery Service limits`
-- `OCI Exadata cloud VM cluster autonomous VM cluster API CLI operations maintenance IORM`
-
-Keep prompts free of customer names, identifiers, IP addresses, secrets, or proprietary architecture details.

package/skills/oci/oci-exadata-platform-architect/references/oracle-mcp.md

@@ -1,28 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-exadata-platform-architect`.
-
-## 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-database-mcp-server for cloud-exadata-infrastructure, exadata-infrastructure, cloud-vm-cluster, vm-cluster, exadb-vm-cluster, db-home, database, pluggable-database, backups, Data Guard, IORM, updates, and Exascale-related resources; oracle.oci-limits-mcp-server for capacity/limit posture; oracle.oracle-db-doc-mcp-server for database documentation fallback.
-
-## Useful OCI command families when generic OCI API MCP or CLI fallback is needed
-
-- `db autonomous-database` for Autonomous Database and Autonomous AI Database list/get/update/backup/clone/DR operations where supported.
-- `db autonomous-container-database` for dedicated autonomous container database lifecycle and Data Guard operations where supported.
-- `db autonomous-vm-cluster` and `db cloud-autonomous-vm-cluster` for dedicated autonomous fleet capacity where supported.
-- `db cloud-exa-infra`, `db exadata-infrastructure`, `db cloud-vm-cluster`, `db vm-cluster`, `db db-home`, `db database`, and `db pluggable-database` for Exadata and database stack evidence where supported.
-
-## 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, credentials, API tokens, fingerprints, tenancy identifiers, database passwords, wallets, 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 command help and OCI command execution, when service-specific tools are unavailable.
-3. OCI CLI default profile fallback only when MCP is unavailable or insufficient.

package/skills/oci/oci-fusion-apps-environment-operator/references/documentation-fallback.md

@@ -1,30 +0,0 @@
-# Documentation Fallback
-
-Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-fusion-apps-environment-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-fusion-apps-environment-operator/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-fusion-apps-environment-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-faaas-mcp-server: list_fusion_environment_families, list_fusion_environments, get_fusion_environment, get_fusion_environment_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-goldengate-replication-operator/references/documentation-fallback.md

@@ -1,30 +0,0 @@
-# Documentation Fallback
-
-Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-goldengate-replication-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-goldengate-replication-operator/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-goldengate-replication-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.oracle-goldengate-mcp-server: list_domains, list_connections, list_extracts, list_replicats, get_extract_status, get_replicat_status, create_extract, create_replicat, start, stop
-
-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-identity-access-governor/references/documentation-fallback.md

@@ -1,30 +0,0 @@
-# Documentation Fallback
-
-Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-identity-access-governor`.
-
-## 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-identity-access-governor/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-identity-access-governor`.
-
-## 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-identity-mcp-server: list_compartments, get_current_tenancy, get_current_user, get_compartment_by_name, list_subscribed_regions; oracle.oci-cloud-mcp-server for unsupported IAM API discovery.
-- 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-iot-digital-twin-engineer/references/documentation-fallback.md

@@ -1,30 +0,0 @@
-# Documentation Fallback
-
-Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-iot-digital-twin-engineer`.
-
-## 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-iot-digital-twin-engineer/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-iot-digital-twin-engineer`.
-
-## 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-iot-mcp-server: get_digital_twin_adapter, create_digital_twin_model, create_digital_twin_instance, create_digital_twin_relationship, derive_domain_context, update/delete digital twin resources
-
-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-limits-capacity-planner/references/documentation-fallback.md

@@ -1,30 +0,0 @@
-# Documentation Fallback
-
-Use this reference when live OCI infrastructure data is unavailable, incomplete, denied, or unsafe to query for `oci-limits-capacity-planner`.
-
-## 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-limits-capacity-planner/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-limits-capacity-planner`.
-
-## 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-limits-mcp-server: list_services, list_limit_definitions, list_limit_values, get_resource_availability; oracle.oci-identity-mcp-server: list_subscribed_regions
-
-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-live-autonomous-db-lifecycle-guard/references/permission-model.md

@@ -1,49 +0,0 @@
-# Permission Model: OCI Live Autonomous DB Lifecycle Guard
-
-## 3-tier separation
-
-| Tier | Group | Verb | Scope |
-|------|-------|------|-------|
-| Audit | `<adb-auditors>` | inspect / read | `<prod-db-compartment>` |
-| Operator | `<adb-operators>` | use | `<prod-db-compartment>` |
-| Admin | `<adb-admins>` | manage + tag condition | `<prod-db-compartment>` |
-
-## Baseline read (no mutation)
-
-```
-Allow group <adb-auditors> to inspect autonomous-databases in compartment <prod-db-compartment>
-Allow group <adb-auditors> to read autonomous-databases in compartment <prod-db-compartment>
-Allow group <adb-auditors> to read autonomous-database-backups in compartment <prod-db-compartment>
-```
-
-## Operator — start, stop, scale (use verb, no terminate/clone)
-
-```
-Allow group <adb-operators> to use autonomous-databases in compartment <prod-db-compartment>
-```
-
-With `use`: start, stop, scale CPU/storage, generate wallet.
-Cannot: terminate, clone, change network-access type.
-
-## Admin — clone and terminate (manage + tag condition)
-
-```
-Allow group <adb-admins> to manage autonomous-databases in compartment <prod-db-compartment>
-  where target.resource.tag.Operations.Lifecycle.value != 'protected'
-```
-
-The `Operations.Lifecycle = protected` tag must be set in a **protected tag namespace** on all
-production ADBs. Only tag-namespace admins can remove the tag.
-
-> **IRREVERSIBILITY WARNING**
-> - **Termination** is permanent. OCI does not recover terminated ADB instances.
-> - **Storage scale-up** is a one-way door — storage can only grow, never shrink.
-> - Both operations require dual-sign-off and a confirmed maintenance window.
-
-## Do not use
-
-```
-# FORBIDDEN
-Allow group <adb-operators> to manage autonomous-databases in tenancy
-Allow any-user to use autonomous-databases in compartment prod-db
-```

package/skills/oci/oci-live-autonomous-db-lifecycle-guard/references/preflight-commands.md

@@ -1,58 +0,0 @@
-# Preflight Commands: OCI Live Autonomous DB Lifecycle Guard
-
-Run these before any ADB lifecycle mutation. Paste sanitized output as evidence.
-
-## 1. Confirm identity and tenancy
-
-```bash
-oci iam region list --query "data[0]" 2>/dev/null || true
-oci iam user get --user-id $(oci iam user list --query "data[0].id" --raw-output) \
-  --query "data.{name:name,id:id}" 2>/dev/null
-# Or check OCI config profile
-cat ~/.oci/config | grep -E "^(user|tenancy|region|fingerprint)"
-```
-
-## 2. Get current ADB state
-
-```bash
-oci db autonomous-database get \
-  --autonomous-database-id <ADB_OCID> \
-  --query "data.{displayName:\"display-name\",lifecycleState:\"lifecycle-state\",ocpuCount:\"ocpu-count\",dataStorageSizeInTBs:\"data-storage-size-in-tbs\",freeformTags:\"freeform-tags\",definedTags:\"defined-tags\"}"
-```
-
-## 3. Verify protection tag is set (before any manage-verb operation)
-
-```bash
-oci db autonomous-database get \
-  --autonomous-database-id <ADB_OCID> \
-  --query "data.\"defined-tags\".Operations.Lifecycle"
-# Must return "protected" on production ADBs
-```
-
-## 4. Confirm recent backup exists
-
-```bash
-oci db autonomous-database-backup list \
-  --autonomous-database-id <ADB_OCID> \
-  --sort-by TIMECREATED \
-  --sort-order DESC \
-  --limit 3 \
-  --query "data[].{displayName:\"display-name\",lifecycleState:\"lifecycle-state\",timeStarted:\"time-started\",isAutomatic:\"is-automatic\"}"
-```
-
-## 5. Check wallet and connection strings (before scale/clone)
-
-```bash
-oci db autonomous-database get \
-  --autonomous-database-id <ADB_OCID> \
-  --query "data.{connectionStrings:\"connection-strings\",connectionUrls:\"connection-urls\"}"
-```
-
-## 6. Verify no in-flight operations
-
-```bash
-oci db autonomous-database get \
-  --autonomous-database-id <ADB_OCID> \
-  --query "data.{lifecycleState:\"lifecycle-state\",lifecycleDetails:\"lifecycle-details\"}"
-# lifecycleState must be AVAILABLE before any mutation
-```

package/skills/oci/oci-live-autonomous-db-lifecycle-guard/references/rollback-playbook.md

@@ -1,44 +0,0 @@
-# Rollback Playbook: OCI Live Autonomous DB Lifecycle Guard
-
-## Restore from automatic backup (after accidental stop or data issue)
-
-```bash
-# List available backups
-oci db autonomous-database-backup list \
-  --autonomous-database-id <ADB_OCID> \
-  --query "data[].{id:id,displayName:\"display-name\",timeStarted:\"time-started\",type:type}"
-
-# Restore to a specific backup
-oci db autonomous-database restore \
-  --autonomous-database-id <ADB_OCID> \
-  --timestamp <ISO8601_TIMESTAMP>
-# Example: --timestamp "2025-04-29T12:00:00.000Z"
-```
-
-## Start a stopped database
-
-```bash
-oci db autonomous-database start \
-  --autonomous-database-id <ADB_OCID>
-
-# Poll for AVAILABLE state
-oci db autonomous-database get \
-  --autonomous-database-id <ADB_OCID> \
-  --query "data.\"lifecycle-state\""
-```
-
-## Scale CPU down (if over-provisioned)
-
-```bash
-oci db autonomous-database update \
-  --autonomous-database-id <ADB_OCID> \
-  --ocpu-count <TARGET_COUNT>
-# Note: storage cannot be scaled down — only CPU is reversible
-```
-
-## Rollback limitations
-
-- **Termination is permanent** — no recovery path exists after an ADB is terminated.
-- **Storage scale-up is irreversible** — OCI does not shrink ADB storage after an increase.
-- Point-in-time restore is available only within the automatic backup retention window (default: 60 days).
-- Connection wallet files generated for the new ADB (after clone) are not interchangeable with the source ADB wallet.