agentsclimarketplace

Oci waf security review

Skill Raishin/vanguard-frontier-agentic/skills/oci/oci-waf-security-review

Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill oci-waf-security-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review OCI Well-Architected security posture across IAM, compartments, network exposure, encryption, logging, Cloud Guard, Security Zones, vulnerability scanning, and compliance guardrails.

SKILL.md

2.3 KB, as published. Nobody here has run it

OCI WAF Security Review

Purpose

Review OCI Well-Architected security posture with source-grounded checks for IAM, network exposure, encryption, logging, Cloud Guard, Security Zones, Vulnerability Scanning, and evidence-labeled findings.

Use When

  • 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

  • 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

  • references/oci-waf-security-review-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.

Response Contract

Return verdict, evidence_level, blockers, safe_next_actions, and open_questions. Be blunt when evidence is insufficient.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.