@raishin/vanguard-frontier-agentic 2.8.0 → 2.10.0

package/skills/oci/oci-multi-cloud-architect/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-multi-cloud-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-networking-mcp-server for VCN/DRG/VPN/FastConnect-adjacent evidence through supported APIs; oracle.oci-monitoring-mcp-server for tunnel/circuit telemetry where available; oracle.oci-resource-search-mcp-server for cross-domain inventory.
-- 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-mysql-heatwave-ai-specialist/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-mysql-heatwave-ai-specialist`.
-
-## 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-mysql-heatwave-ai-specialist/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-mysql-heatwave-ai-specialist`.
-
-## 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.mysql-mcp-server: configured MySQL connections, SQL execution, MySQL AI/HeatWave ML and GenAI tools, object storage helper tools
-
-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-network-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-network-architect`.
-
-## 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-network-architect/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-network-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-networking-mcp-server: list_vcns, get_vcn, list_subnets, list_security_lists, list_network_security_groups; oracle.oci-network-load-balancer-mcp-server for NLB path checks.
-- 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-observability-incident-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-observability-incident-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-observability-incident-responder/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-observability-incident-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-monitoring-mcp-server: list_alarms, get_metrics_data, get_available_metrics; oracle.oci-logging-mcp-server: list_log_groups, list_logs, get_log; oracle.oci-support-mcp-server for incident 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-recovery-service-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-recovery-service-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-recovery-service-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-recovery-service-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-recovery-mcp-server: list_protected_databases, get_protected_database, summarize_protected_database_health, summarize_protected_database_redo_status, summarize_backup_space_used, list_protection_policies, get_recovery_service_metrics
-
-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-registry-artifact-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-registry-artifact-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-registry-artifact-governor/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-registry-artifact-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-registry-mcp-server: create_container_repository, list_container_repositories, get_container_repo_details, delete_container_repository
-
-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.
-
-## 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-resource-search-inventory-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-resource-search-inventory-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-resource-search-inventory-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-resource-search-inventory-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-resource-search-mcp-server: search_resources; oracle.oci-cloud-mcp-server: list_oci_clients, find_oci_api, describe_oci_operation, invoke_oci_api, list_client_operations
-
-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-security-compliance-reviewer/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-security-compliance-reviewer`.
-
-## 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-security-compliance-reviewer/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-security-compliance-reviewer`.
-
-## 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; oracle.oci-identity-mcp-server for compartment/identity context; oracle.oci-resource-search-mcp-server for asset 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-solution-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-solution-architect`.
-
-## 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-solution-architect/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-solution-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-resource-search-mcp-server for estate discovery; oracle.oci-cloud-mcp-server for generic service API exploration; domain-specific official Oracle MCP servers for IAM, network, compute, database, storage, monitoring, security, limits, and cost 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-storage-backup-steward/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-storage-backup-steward`.
-
-## 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-storage-backup-steward/references/oracle-mcp.md

@@ -1,22 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-storage-backup-steward`.
-
-## 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-object-storage-mcp-server: get_namespace, list_buckets, get_bucket_details, list_objects, list_object_versions; oracle.oci-recovery-mcp-server for database recovery evidence where relevant.
-- 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-support-incident-coordinator/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-support-incident-coordinator`.
-
-## 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-support-incident-coordinator/references/oracle-mcp.md

@@ -1,23 +0,0 @@
-# Official Oracle MCP Capability Mapping
-
-Use this reference when selecting live Oracle MCP tools for `oci-support-incident-coordinator`.
-
-## 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-support-mcp-server: list_incidents, get_incident, create_incident, list_incident_resource_types, validate_user
-
-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.