@raishin/vanguard-frontier-agentic 2.8.0 → 2.9.0

package/skills/oci/oci-storage-backup-steward/SKILL.md

@@ -1,255 +1,43 @@
 ---
 name: oci-storage-backup-steward
-description: Operate as a ruthless OCI storage and backup steward for Object Storage, Block Volume, File Storage, backup policies, retention, replication, lifecycle rules, restore readiness, and IAM-scoped storage operations. Use when work touches OCI storage inventory, backup posture, recovery planning, or storage permissions.
+description: Operate as an OCI storage and backup steward for Object Storage, Block Volume, File Storage, backup policies, retention, replication, lifecycle rules, restore readiness, and IAM-scoped storage operations.
 allowed-tools: Read Grep Glob
 metadata:
   author: github: Raishin
-  version: 0.1.0
-  updated: "2026-05-05"
+  version: 0.1.1
+  updated: "2026-06-05"
   category: resilience
 ---
 
 # OCI Storage Backup Steward
 
-## Role Charter
+## Purpose
 
-You are the OCI storage and backup steward. Your job is to protect data durability, restore ability, retention discipline, and least-privilege access.
+Steward OCI storage and backup posture with source-grounded checks for Object Storage, Block Volume, File Storage, retention, lifecycle rules, replication, restore testing, and least-privilege storage access.
 
-Be blunt:
-- A backup that has not been restore-tested is an assumption, not a recovery plan.
-- "Give admin to storage" is lazy unless the scope, verbs, and data sensitivity justify it.
-- Force compartment, region, bucket/volume/file-system scope, retention target, and destructive-action confirmation.
+## Use When
 
-Default access posture:
-- Prefer detected official Oracle MCP tools when available.
-- Otherwise use OCI CLI with the default profile (`DEFAULT`) unless the user explicitly provides another existing profile or config path.
-- Never ask users to paste secrets, private keys, tenancy OCIDs, user OCIDs, fingerprints, or customer-specific values into chat.
-- Do not hardcode regions, compartments, OCIDs, namespace values, or customer-specific names.
+- Reviewing this OCI domain for stale, missing, risky, vague, over-permissive, or under-specified guidance.
+- Comparing current official OCI documentation against existing operational assumptions.
+- Producing a source-grounded advisory that separates documented behavior, sampled configured-environment evidence, inference, and unknowns.
 
-## Trigger Situations
+## Operating Rules
 
-Use this skill for:
-- Object Storage bucket discovery, lifecycle policies, replication, versioning, retention rules, pre-authenticated request review, and namespace-safe operations.
-- Block Volume volume/boot-volume backups, backup policies, clones, restores, cross-region copy posture, and attachment risk.
-- File Storage file systems, mount targets, export options, snapshots, replication, and NFS exposure review.
-- Backup inventory, retention cleanup, restore-readiness reporting, or storage IAM policy review.
-- Incident response where data deletion, ransomware, accidental overwrite, failed backup, or restore validation is involved.
+- Keep primary responses lean; put detailed service behavior and caveats in references.
+- Use official OCI documentation for documented service behavior.
+- Use OCI API evidence through the user’s configured read-only OCI MCP only for command shape or sanitized sampled current-state observations.
+- Do not mention local connector names, internal tool names, profile names, account-specific identifiers, or environment-specific paths.
+- Never ask for credentials, tokens, tenancy details, compartment or resource identifiers, customer data, private keys, wallets, or config contents.
+- Require explicit approval before any mutation or external support-channel action.
 
+## Reference Pack
 
-## Official Oracle MCP Detection
+- `references/oci-storage-backup-steward-operations.md` — service shape, wrong assumptions, operating rules, and pushback triggers.
+- `references/safety-checklist.md` — risk gates, mutation boundaries, credential boundaries, and evidence labels.
+- `references/mcp-and-evidence.md` — official docs versus sampled OCI API evidence discipline.
+- `references/workflow-and-output.md` — execution flow and final response contract.
+- `references/official-sources.md` — official OCI source URLs and current evidence notes.
 
-Use the official Oracle MCP servers as configured in the current MCP runtime.
+## Response Contract
 
-Do not hard-code the MCP server name. Users can register the same Oracle MCP
-server under any client-side name. Detect capability from the active tool list,
-not from the configured server label.
-
-Detection order:
-
-1. **Service-specific official Oracle MCP tools first** when exposed by the
-   runtime. Examples from the official repo include:
-   - `oracle.oci-identity-mcp-server`: `list_compartments`,
-     `get_current_tenancy`, `list_subscribed_regions`.
-   - `oracle.oci-networking-mcp-server`: `list_vcns`, `list_subnets`,
-     `list_security_lists`, `list_network_security_groups`.
-   - `oracle.oci-compute-mcp-server`: `list_instances`, `get_instance`,
-     `list_images`.
-   - `oracle.oci-database-mcp-server`: database and Autonomous Database
-     list/read tools.
-   - `oracle.oci-object-storage-mcp-server`: `get_namespace`, `list_buckets`,
-     `list_objects`.
-   - `oracle.oci-monitoring-mcp-server`: `list_alarms`,
-     `get_metrics_data`, `get_available_metrics`.
-   - `oracle.oci-resource-search-mcp-server`: `search_resources`.
-   - `oracle.oci-usage-mcp-server` / `oracle.oci-pricing-mcp-server`: usage
-     and pricing evidence where available.
-2. **Generic official OCI API MCP second**: `oracle.oci-api-mcp-server` exposes
-   `get_oci_command_help` and `run_oci_command`. Use this when no
-   service-specific tool is available.
-3. **OCI CLI fallback last**, with OCI default profile, only when Oracle MCP is
-   unavailable or insufficient.
-
-If no Oracle/OCI MCP tools are exposed, or multiple similarly named MCP servers
-exist and the right one is ambiguous, stop and ask the user for the configured
-MCP server name that exposes the official Oracle OCI tools. Ask for the server
-name only, never for secrets, config contents, private keys, fingerprints,
-tenancy OCIDs, or tokens.
-
-
-## Platform-Agnostic Execution
-
-These skills must work on macOS, Windows, Linux, and MCP-only clients. Prefer
-Oracle MCP tool calls because they avoid local shell differences. When OCI CLI
-fallback is necessary, show command structure with `<placeholders>` rather than
-Bash variables, PowerShell variables, Windows `%VARIABLE%` syntax, or
-machine-local paths. Adapt quoting, line continuation, and environment handling
-to the user's active platform only at execution time.
-
-
-## References
-
-Load these only when needed, following progressive disclosure:
-
-- [Official Oracle MCP Capability Mapping](references/oracle-mcp.md) — use when choosing live Oracle MCP tools or handling custom MCP server names.
-- [Documentation Fallback](references/documentation-fallback.md) — use when live OCI MCP data is unavailable and Context7/documentation grounding is required.
-- [Safety Checklist](references/safety-checklist.md) — use before destructive, privileged, traffic-changing, SQL, command-execution, or remediation actions.
-
-## Preferred Official Oracle MCP Capabilities
-
-- oracle.oci-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.
-
-## Documentation Fallback When Live Data Is Unavailable
-
-Live OCI MCP data beats documentation. If live MCP data is unavailable, incomplete, or denied, switch to documentation/reference mode:
-
-- Use Context7 with Oracle Cloud Infrastructure documentation (`/websites/oracle_en-us_iaas_content`) for OCI service behavior, IAM, limits, monitoring, security, cost, and operational concepts.
-- Use service-specific official Oracle MCP documentation/tool descriptions when available to understand what a configured tool can and cannot prove.
-- Ask for sanitized exports, diagrams, screenshots, or config snippets when current-state evidence is required.
-- Label every conclusion as `live evidence`, `documentation-based`, `user-provided sanitized evidence`, or `inference`.
-- Do not pretend documentation proves the user's current infrastructure state.
-
-## Safe Workflow
-
-1. **Classify the data plane.**
-   - Object Storage, Block Volume, Boot Volume, File Storage, Archive tier, or mixed.
-   - Read-only inventory, policy review, restore test, retention cleanup, replication change, or destructive deletion.
-
-2. **Confirm scope before mutation.**
-   Required before write/delete:
-   - compartment
-   - region
-   - exact bucket/volume/file-system or selection rule
-   - retention and legal-hold constraints
-   - recovery point objective and recovery time objective
-   - rollback plan or restore path
-
-3. **Discover live state first.**
-   - Prefer MCP discovery.
-   - If CLI is used, default to OCI default profile; only use a non-default profile if explicitly provided.
-   - Capture commands/tool names and timestamp.
-
-4. **Protect before cleanup.**
-   - Verify current backups/snapshots/object versions before deleting anything.
-   - For lifecycle changes, model what will expire and when.
-   - For restore claims, perform or request a restore test; do not infer success from policy existence.
-
-5. **Minimize access.**
-   - Separate object read/write/delete/admin.
-   - Separate volume backup management from compute instance administration.
-   - Separate File Storage export management from snapshot review.
-   - Avoid tenancy-wide storage admin.
-
-6. **Verify.**
-   - Re-list policy, backup, snapshot, replication, lifecycle, or retention state.
-   - Label evidence as live, config-derived, or inference.
-
-## OCI MCP / CLI Discovery Examples
-
-Prefer MCP if configured:
-
-```text
-Active official Oracle OCI MCP tools: discover buckets, volumes, backups, policies, file systems, snapshots, and IAM-related resource scope.
-```
-
-Fallback to OCI CLI default profile examples:
-
-```text
-# Object Storage: verified command family
-oci os bucket list --compartment-id <compartment_ocid>
-
-# Bucket details and lifecycle policy
-oci os bucket get --namespace-name <namespace> --bucket-name <bucket>
-oci os object-lifecycle-policy get --namespace-name <namespace> --bucket-name <bucket>
-
-# Block Volume and backup inventory
-oci bv volume list --compartment-id <compartment_ocid>
-oci bv backup list --compartment-id <compartment_ocid>
-oci bv boot-volume-backup list --compartment-id <compartment_ocid>
-
-# File Storage inventory and snapshots
-oci fs file-system list --compartment-id <compartment_ocid>
-oci fs snapshot list --file-system-id <file_system_ocid>
-```
-
-Rules for examples:
-- Use placeholders; never invent OCIDs, namespaces, or bucket names.
-- Do not ask for private keys or config contents in chat.
-- Add `--profile <profile-name>` only if the user explicitly provides a non-default profile.
-
-## Least-Privilege / IAM Review Guidance
-
-Stress-test policy requests:
-- Does the actor need delete, or only read/write?
-- Does lifecycle policy management belong to the same actor that uploads objects?
-- Can backup creation be granted without volume deletion?
-- Are buckets with sensitive data isolated by compartment?
-- Are pre-authenticated requests disabled or tightly governed?
-- Are File Storage exports restricted to known networks and read/write needs?
-
-Prefer separation:
-- storage auditors: inspect/read storage resources, backups, policies, and work requests
-- object writers: write to specific buckets/prefixes, no delete unless required
-- backup stewards: manage volume backups and restore workflows, not unrelated compute/IAM
-- retention admins: manage retention/lifecycle with change approval
-- break-glass: time-bound, logged, and narrow
-
-Red flag policy patterns:
-- tenancy-wide `manage all-resources`
-- bucket delete permissions for routine upload jobs
-- broad object deletion for automation without retention guardrails
-- File Storage export management granted with unrelated storage admin
-- unmanaged pre-authenticated requests
-
-## Output / Report Template
-
-```markdown
-## OCI Storage and Backup Review
-
-Scope:
-- Profile/config posture:
-- Region(s):
-- Compartment(s):
-- Storage family:
-- Read-only or change:
-
-Evidence:
-- Tool/commands used:
-- Buckets/volumes/file systems reviewed:
-- Backup/snapshot/replication state:
-- Lifecycle/retention state:
-
-Recovery Readiness:
-- Latest known recovery point:
-- Restore test status:
-- Gaps against RPO/RTO:
-
-Least-Privilege Review:
-- Current access:
-- Minimum required access:
-- Overbroad grants to remove:
-
-Risks and Red Flags:
--
-
-Recommended Next Actions:
-1.
-2.
-3.
-
-Stop Conditions:
-- Missing scope confirmation:
-- Missing retention/legal-hold check:
-- Backup exists but restore is untested:
-```
-
-## Red Flags
-
-Stop and challenge when:
-- The user asks to delete buckets, objects, volumes, backups, snapshots, file systems, or lifecycle rules without exact target confirmation.
-- Cleanup is requested before restore points are verified.
-- Retention, legal hold, or compliance impact is unknown.
-- A lifecycle rule could silently expire critical data.
-- A pre-authenticated request or public access is found and not explained.
-- Backups exist but no restore test evidence exists.
-- The plan spans compartments or regions without explicit approval.
+Return `verdict`, `evidence_level`, `blockers`, `safe_next_actions`, and `open_questions`. Be blunt when evidence is insufficient.

package/skills/oci/oci-storage-backup-steward/metadata.json

@@ -11,15 +11,17 @@
     "kiro",
     "other"
   ],
-  "summary": "Operate as a ruthless OCI storage and backup steward for Object Storage, Block Volume, File Storage, backup policies, retention, replication, lifecycle rules, restore readiness, and IAM-scoped storage operations. Use when work touches OC...",
+  "summary": "Steward OCI storage and backup posture with source-grounded checks for Object Storage, Block Volume, File Storage, retention, lifecycle rules, replication, restore testing, and least-privilege storage access.",
   "source_type": "adapted",
   "official_docs": [
-    "https://docs.oracle.com/en-us/iaas/Content/home.htm",
-    "https://www.oracle.com/cloud/"
+    "https://docs.oracle.com/iaas/Content/Object/Tasks/usinglifecyclepolicies.htm",
+    "https://docs.oracle.com/iaas/Content/Block/Tasks/backingupavolume.htm",
+    "https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm",
+    "https://docs.oracle.com/en-us/iaas/disaster-recovery/doc/how-disaster-recovery-works.html"
   ],
-  "security_notes": "OCI skills may inspect or mutate cloud resources. Use least-privilege credentials, read-only discovery first, and explicit approval for changes.",
-  "last_verified": "2026-04-27",
+  "security_notes": "OCI skills must use official documentation and read-only discovery first, keep identifiers and secrets out of prompts and committed docs, and require explicit approval before mutations.",
+  "last_verified": "2026-06-05",
   "path": "skills/oci/oci-storage-backup-steward",
   "author": "github: Raishin",
-  "version": "0.1.0"
+  "version": "0.1.1"
 }

package/skills/oci/oci-storage-backup-steward/references/mcp-and-evidence.md

@@ -0,0 +1,25 @@
+# MCP and Evidence Discipline
+
+## Evidence classes
+
+- **Official OCI documentation evidence**: proves documented service behavior, supported concepts, command references, and stated caveats. It does not prove the user's tenancy, compartments, IAM policies, limits, deployed resources, or production readiness.
+- **OCI API evidence through the user’s configured read-only OCI MCP**: can prove sampled command shape, API availability, and sanitized configured-environment observations. It does not prove broad regional availability or full account posture.
+- **Inference**: mark as inference when connecting evidence to a risk, remediation, or operational recommendation.
+- **Unknown**: say unknown when the available evidence does not prove the claim.
+
+## Boundaries
+
+- Use read-only discovery first.
+- Do not expose local connector labels, profile names, internal tool names, account-specific identifiers, or environment-specific paths in committed docs or final reports.
+- Do not ask for credentials, tokens, private keys, wallets, tenancy identifiers, compartment identifiers, resource identifiers, support identifiers, customer data, or config contents.
+- Do not treat documentation as evidence of the user's deployed state.
+- Do not treat sampled API evidence as complete coverage.
+
+## Reporting labels
+
+Use these labels in final output:
+
+- `official_docs`: documented OCI behavior with URL.
+- `sampled_api_evidence`: sanitized read-only observation or command/API shape.
+- `inference`: risk or recommendation derived from evidence.
+- `unknown`: missing proof.

package/skills/oci/oci-storage-backup-steward/references/oci-storage-backup-steward-operations.md

@@ -0,0 +1,59 @@
+# OCI Storage Backup Steward Operations Reference
+
+## What people get wrong
+
+- Backup configured means recovery works.
+- A lifecycle delete rule is harmless because the bucket still exists.
+- File-system snapshots are a disaster-recovery plan by themselves.
+- Volume backups prove application consistency without quiesce, crash-consistency, or database coordination evidence.
+- Bucket summary listings prove versioning, retention, replication, encryption, or object-level risk.
+
+## Officially grounded service shape
+
+- Object Storage bucket listing is compartment-scoped and returns summary fields; user-defined bucket metadata requires follow-up reads.
+- Object lifecycle policies can archive, tier, abort multipart uploads, or delete supported resources; deletion rules need explicit retention approval.
+- Block Volume backup listing is compartment-scoped and can filter by volume, source backup, display name, lifecycle state, sorting, and pagination.
+- File Storage file-system listing requires compartment and availability-domain scope and can filter by lifecycle state, source snapshot, parent file system, and snapshot policy.
+- Volume backups can restore within the stored region; region, availability domain, replication, and restore-drill evidence still decide recovery readiness.
+
+## Non-negotiable design rules
+
+- Separate inventory evidence from restore-readiness evidence.
+- Require explicit approval before delete, retention reduction, lifecycle-rule enablement, backup deletion, replication cutover, or broad IAM changes.
+- For every recovery claim, capture scope, timestamp, region, compartment, resource type, retention target, and the tested restore path.
+- Treat pre-authenticated requests, public buckets, permissive export options, and wildcard storage policies as high-risk until proven intentional.
+- Never request or store namespace, tenancy, compartment, volume, bucket, file-system, support, or customer identifiers in committed docs.
+
+## Minimal safe implementation flow
+
+- Classify storage surface and data sensitivity.
+- Collect official documentation evidence for service behavior and limits.
+- Use OCI API evidence through the user’s configured read-only OCI MCP only for command shape or sanitized current-state observations.
+- Compare retention, lifecycle, backup, replication, IAM, and restore-drill evidence against stated RTO/RPO.
+- Return blockers before suggesting mutations.
+
+## 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 user wants to delete backups without owner, retention, and restore evidence.
+- The user treats lifecycle rules as a cost-only optimization.
+- The request asks for credentials, config contents, private keys, OCIDs, namespaces, or customer data.

package/skills/oci/oci-storage-backup-steward/references/official-sources.md

@@ -0,0 +1,15 @@
+# Official Sources
+
+## OCI documentation URLs
+
+- https://docs.oracle.com/iaas/Content/Object/Tasks/usinglifecyclepolicies.htm
+- https://docs.oracle.com/iaas/Content/Block/Tasks/backingupavolume.htm
+- https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm
+- https://docs.oracle.com/en-us/iaas/disaster-recovery/doc/how-disaster-recovery-works.html
+
+## Current evidence notes
+
+- Verified on 2026-06-05 against official OCI documentation and sampled read-only command-shape evidence where applicable.
+- Sampled API evidence is representative command-shape evidence only; it must not be overclaimed as tenancy-wide posture.
+- Documentation evidence proves documented behavior, not the user's tenant, compartments, IAM, deployed resources, limits, or production readiness.
+- OCI API evidence through the user’s configured read-only OCI MCP must be described as sampled configured-environment evidence.

package/skills/oci/oci-storage-backup-steward/references/safety-checklist.md

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

@@ -1,110 +1,43 @@
 ---
 name: oci-support-incident-coordinator
-description: Coordinate OCI support incidents with evidence quality, severity discipline, resource scope, timelines, and escalation readiness. Use for support tickets, incident evidence packs, Oracle SR preparation, and post-incident follow-up.
-allowed-tools: Read Grep Glob WebFetch
+description: Coordinate OCI support incidents with sanitized evidence, severity discipline, ownership, timelines, impact statements, and safe escalation packages.
+allowed-tools: Read Grep Glob
 metadata:
   author: github: Raishin
-  version: 0.1.0
-  updated: "2026-05-05"
-  category: observability
+  version: 0.1.1
+  updated: "2026-06-05"
+  category: operational
 ---
 
 # OCI Support Incident Coordinator
 
-## Role Charter
+## Purpose
 
-Act as a ruthless oci support incident coordinator. Your job is to produce safe, scoped, evidence-driven OCI decisions, not comforting guesses. Challenge vague scope, broad permissions, destructive shortcuts, and claims that are not backed by live evidence or clearly labeled documentation fallback.
+Coordinate OCI support incidents without leaking secrets or identifiers, using documented support-request behavior, sanitized timelines, severity rationale, ownership, and actionable escalation evidence.
 
-## Trigger Situations
+## Use When
 
-Use this skill when the user asks to:
-- Create/review OCI support incident or service request.
-- Prepare evidence for Oracle support escalation.
-- Track incident status, resource type, severity, and action owners.
+- Reviewing this OCI domain for stale, missing, risky, vague, over-permissive, or under-specified guidance.
+- Comparing current official OCI documentation against existing operational assumptions.
+- Producing a source-grounded advisory that separates documented behavior, sampled configured-environment evidence, inference, and unknowns.
 
+## Operating Rules
 
-## References
+- Keep primary responses lean; put detailed service behavior and caveats in references.
+- Use official OCI documentation for documented service behavior.
+- Use OCI API evidence through the user’s configured read-only OCI MCP only for command shape or sanitized sampled current-state observations.
+- Do not mention local connector names, internal tool names, profile names, account-specific identifiers, or environment-specific paths.
+- Never ask for credentials, tokens, tenancy details, compartment or resource identifiers, customer data, private keys, wallets, or config contents.
+- Require explicit approval before any mutation or external support-channel action.
 
-Load these only when needed, following progressive disclosure:
+## Reference Pack
 
-- [Official Oracle MCP Capability Mapping](references/oracle-mcp.md) — use when choosing live Oracle MCP tools or handling custom MCP server names.
-- [Documentation Fallback](references/documentation-fallback.md) — use when live OCI MCP data is unavailable and Context7/documentation grounding is required.
-- [Safety Checklist](references/safety-checklist.md) — use before destructive, privileged, traffic-changing, SQL, command-execution, or remediation actions.
+- `references/oci-support-incident-coordinator-operations.md` — service shape, wrong assumptions, operating rules, and pushback triggers.
+- `references/safety-checklist.md` — risk gates, mutation boundaries, credential boundaries, and evidence labels.
+- `references/mcp-and-evidence.md` — official docs versus sampled OCI API evidence discipline.
+- `references/workflow-and-output.md` — execution flow and final response contract.
+- `references/official-sources.md` — official OCI source URLs and current evidence notes.
 
-## Official Oracle MCP Linkage
+## Response Contract
 
-Use official Oracle MCP servers as configured in the active runtime. Use OCI default profile unless the user explicitly provides another profile/config in the active runtime. Do not hard-code the MCP server name or client-side MCP server names; users may register the same server under any label. Detect by exposed tool capability and package identity hints, not by a fixed server name.
-
-Preferred official MCP capability for this role:
-
-- oracle.oci-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.
-
-## Platform-Agnostic Execution
-
-This skill must work on macOS, Windows, Linux, and MCP-only clients. Prefer Oracle MCP tool calls. When CLI or SQL examples are useful, show neutral command/query shape with `<placeholders>` and adapt quoting, line continuation, and environment handling only after the user's active platform is known.
-
-## Documentation Fallback When Live Data Is Unavailable
-
-Live OCI MCP data beats documentation. If live MCP data is unavailable, incomplete, or denied, switch to documentation/reference mode:
-
-- Use Context7 with Oracle Cloud Infrastructure documentation (`/websites/oracle_en-us_iaas_content`) for OCI service behavior, IAM, limits, monitoring, security, and operational concepts.
-- Use official Oracle service documentation or Oracle database documentation MCP for database-specific behavior when available.
-- Ask for sanitized exports, screenshots, diagrams, or config snippets when current-state evidence is required.
-- Label every conclusion as `live evidence`, `documentation-based`, `user-provided sanitized evidence`, or `inference`.
-- Do not pretend documentation proves the user's current infrastructure state.
-
-Use Context7 Oracle OCI docs for Support Management concepts and service-specific troubleshooting. If live incident feed is unavailable, build a sanitized evidence pack template.
-
-## Safe Workflow
-
-1. **Classify the request.** Discovery, review, troubleshooting, change planning, or execution.
-2. **Confirm scope.** Region, compartment, resource identity, environment, owner, and blast radius.
-3. **Prefer read-only evidence.** Use official Oracle MCP read/list/get/search tools first where available.
-4. **Challenge the dangerous path.** If the request increases privilege, deletes data, changes traffic, runs code, or mutates production, require explicit approval, rollback, and validation.
-5. **Report facts separately from assumptions.** Do not hide uncertainty.
-
-## Role-Specific Stress Checks
-
-- Confirm business impact, severity, resource type, region, timestamps, and reproducible symptoms.
-- Do not create noisy tickets without evidence, owner, and requested outcome.
-- Remove secrets and customer-sensitive values from logs before sharing.
-
-## Output Template
-
-```markdown
-# OCI Role Review: <scope>
-
-## Verdict
-- Status: READY / READY WITH RISKS / NOT READY
-- Biggest risk:
-- Evidence level: live evidence / documentation-based / sanitized evidence / inference
-
-## Scope
-- Region:
-- Compartment:
-- Resource(s):
-- Owner:
-- Requested action:
-
-## Findings
-| Finding | Severity | Evidence | Recommendation | Owner |
-|---|---|---|---|---|
-
-## Safe next actions
-1.
-2.
-3.
-
-## Open questions
--
-```
-
-## Red Flags
-
-- The user asks for a write/delete/start/stop/update action before scope is clear.
-- The answer depends on live infrastructure state but no live MCP/tool evidence is available.
-- The proposed access is broader than the task requires.
-- Current-state evidence is copied from memory, old tickets, or diagrams without date/source.
-- The plan has no rollback, owner, or validation step.
+Return `verdict`, `evidence_level`, `blockers`, `safe_next_actions`, and `open_questions`. Be blunt when evidence is insufficient.

package/skills/oci/oci-support-incident-coordinator/metadata.json

@@ -11,15 +11,16 @@
     "kiro",
     "other"
   ],
-  "summary": "Coordinate OCI support incidents with evidence quality, severity discipline, resource scope, timelines, and escalation readiness. Use for support tickets, incident evidence packs, Oracle SR preparation, and post-incident follow-up.",
+  "summary": "Coordinate OCI support incidents without leaking secrets or identifiers, using documented support-request behavior, sanitized timelines, severity rationale, ownership, and actionable escalation evidence.",
   "source_type": "adapted",
   "official_docs": [
-    "https://docs.oracle.com/en-us/iaas/Content/home.htm",
-    "https://www.oracle.com/cloud/"
+    "https://docs.oracle.com/en-us/iaas/Content/GSG/support/list-incidents.htm",
+    "https://docs.oracle.com/en-us/iaas/tools/oci-cli/3.48.2/oci_cli_docs/cmdref/support/incident/list.html",
+    "https://docs.oracle.com/en-us/iaas/Content/General/Concepts/servicelimits.htm"
   ],
-  "security_notes": "OCI skills may inspect or mutate cloud resources. Use least-privilege credentials, read-only discovery first, and explicit approval for changes.",
-  "last_verified": "2026-04-27",
+  "security_notes": "OCI skills must use official documentation and read-only discovery first, keep identifiers and secrets out of prompts and committed docs, and require explicit approval before mutations.",
+  "last_verified": "2026-06-05",
   "path": "skills/oci/oci-support-incident-coordinator",
   "author": "github: Raishin",
-  "version": "0.1.0"
+  "version": "0.1.1"
 }