@raishin/vanguard-frontier-agentic 2.8.0 → 2.9.0

package/skills/oci/oracle-oci-mcp-grounded-advisor/references/oracle-oci-mcp-grounded-advisor-operations.md

@@ -0,0 +1,58 @@
+# Oracle and OCI MCP Grounded Advisor Operations Reference
+
+## What people get wrong
+
+- An Oracle-published MCP package is safe in production by default.
+- Tool availability means the user has permission or should use the tool.
+- A read/write-capable connector is acceptable for discovery.
+- Database or cloud identifiers can be pasted into prompts for convenience.
+- Community examples replace official Oracle source verification.
+
+## Officially grounded service shape
+
+- Oracle-published MCP sources document available Oracle tooling and integration paths; they do not prove the user’s local runtime wiring, permissions, or safety posture.
+- MCP can connect assistants to external tools, data sources, and services, so authentication, authorization, tool boundaries, and auditability are first-class review items.
+- OCI API evidence through the user’s configured read-only OCI MCP can prove sampled command shape or configured-environment observations, not broad tenancy posture.
+- Documentation evidence and configured-environment evidence must be separated in every recommendation.
+
+## Non-negotiable design rules
+
+- Verify official Oracle source, package identity, capability set, auth model, read/write boundary, data sensitivity, and audit path before recommending use.
+- Prefer read-only discovery for advisory work and require explicit approval for any mutation-capable path.
+- Do not name local connector labels, profile names, internal tool names, or environment-specific identifiers in committed guidance.
+- Do not ask for credentials, tokens, wallets, private keys, tenancy details, database connection strings, customer data, or config contents.
+- Mark every claim as official-documentation evidence, sampled configured-environment evidence, inference, or unknown.
+
+## Minimal safe implementation flow
+
+- Identify the Oracle product, tool, or protocol question.
+- Verify current official Oracle source and documented capability.
+- Use OCI API evidence through the user’s configured read-only OCI MCP only for sanitized command shape or sampled current-state evidence.
+- Evaluate auth, permission, data exposure, and mutation boundaries before advising.
+- Return a grounded recommendation with explicit uncertainties.
+
+## High-risk assumptions to kill
+
+- Documentation proves service behavior; it does not prove the user's deployed posture.
+- Sampled API evidence proves only the sampled command shape or observation.
+- Read-only discovery is not approval for mutation.
+- Missing evidence is a blocker, not a detail to smooth over.
+
+## Safe command/code verification targets
+
+- Prefer schema, manifest, link, and asset-integrity validation for repository edits.
+- Prefer read-only list/get/help operations for cloud evidence.
+- Redact or omit identifiers and sensitive values from notes and reports.
+
+## Safe verification targets
+
+- Official OCI documentation URL is attached to each service-behavior claim.
+- Sampled API evidence is labeled with scope and limitation.
+- Approval gates are explicit for every proposed mutation.
+- Evidence gaps are listed as open questions.
+
+## When to push back
+
+- The request treats MCP as a trust boundary instead of a tool invocation protocol.
+- The user wants production enablement without auth, permission, audit, and data-sensitivity review.
+- The prompt asks for secrets, config contents, identifiers, or customer data.

package/skills/oci/oracle-oci-mcp-grounded-advisor/references/safety-checklist.md

@@ -0,0 +1,18 @@
+# Safety Checklist
+
+## Non-negotiable gates
+
+- [ ] Scope is explicit: service, workload, region class, compartment boundary, and evidence window are defined without exposing identifiers.
+- [ ] Official OCI documentation is used for service behavior and caveats.
+- [ ] OCI API evidence through the user’s configured read-only OCI MCP is labeled as sampled evidence.
+- [ ] Secrets and identifiers are absent from prompts, notes, committed docs, and examples.
+- [ ] Mutations require explicit user approval and a rollback or recovery path.
+- [ ] Findings separate fact, inference, unknowns, and recommended action.
+
+## High-risk mutation boundary
+
+Stop and require explicit approval before any action that creates, updates, deletes, enables, disables, rotates, attaches, detaches, escalates, fails over, resizes, purchases commitments, changes access, changes retention, or sends data to a support channel.
+
+## Credential boundary
+
+Never ask the user to paste credentials, tokens, tenant or tenancy identifiers, subscription-like identifiers, compartment identifiers, resource identifiers, support identifiers, customer data, private keys, wallets, fingerprints, connection strings, kubeconfigs, or config contents. Ask for a sanitized description or permission to inspect through already configured read-only tooling instead.

package/skills/oci/oracle-oci-mcp-grounded-advisor/references/workflow-and-output.md

@@ -0,0 +1,24 @@
+# Workflow and Output Contract
+
+## Execution flow
+
+1. Restate the workload, service boundary, and decision to be made.
+2. Gather official OCI documentation evidence for service behavior.
+3. Gather only read-only, sanitized OCI API evidence through the user’s configured read-only OCI MCP when current-state or command-shape evidence is needed.
+4. Compare evidence against the asset-specific risk checklist.
+5. Identify stale, missing, risky, vague, over-permissive, or ungrounded guidance.
+6. Return blockers before optional improvements.
+
+## Final response minimum
+
+Return:
+
+- `verdict`: pass, caution, or block.
+- `evidence_level`: official_docs, sampled_api_evidence, inference, or unknown.
+- `blockers`: risks that prevent a safe positive recommendation.
+- `safe_next_actions`: read-only or approved actions only.
+- `open_questions`: missing facts that materially change the recommendation.
+
+## Tone
+
+Be direct. Do not validate weak assumptions. If evidence is missing, say so.

package/skills/oci/oci-autonomous-database-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-autonomous-database-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-autonomous-database-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-autonomous-database-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 autonomous-database, autonomous-container-database, autonomous-vm-cluster, cloud-autonomous-vm-cluster, backups, peers, Data Guard, wallet, Operations Insights, and Data Safe posture; oracle.oci-recovery-mcp-server for recovery 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-cloud-guard-responder/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-cloud-guard-responder`.
-
-## 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-cloud-guard-responder/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# 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-compute-instance-agent-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-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

@@ -1,23 +0,0 @@
-# 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-platform-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-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

@@ -1,22 +0,0 @@
-# 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-cost-finops-analyst/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-cost-finops-analyst`.
-
-## 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-cost-finops-analyst/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-cost-finops-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.oci-usage-mcp-server: list_usage_reports, get_usage_report; oracle.oci-pricing-mcp-server: pricing_get_sku, pricing_search_name; oracle.oci-limits-mcp-server for capacity-vs-cost constraints.
-- 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-database-platform-dba/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-database-platform-dba`.
-
-## 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-database-platform-dba/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-database-platform-dba`.
-
-## 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 DB systems, Autonomous Database, backups, Data Guard, Exadata relationships; oracle.oci-recovery-mcp-server for protected database recovery posture; oracle.oracle-db-doc-mcp-server for docs fallback.
-- 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-dbtools-sql-analyst/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-dbtools-sql-analyst`.
-
-## 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-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.