Claude Cursor GitHub Copilot Skill

aws-s3-data-perimeter-governor

Review Amazon S3 data perimeter and exposure posture across Block Public Access, Object Ownership, ACL removal, bucket/access point policies, TLS-only access, encryption, replication, lifecycle, logging, cross-account access, and prefix boundaries. Prefer this for S3 data exposur

LLM Mart · 0 points · 5 views 0 listing impressions 0 install-command copies
Download vincentchuwaichow-vanguard-frontier-agentic-skills_aws_aws-s3-data-perimeter-governor-febe32a.zip · 6 KB

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/aws/aws-s3-data-perimeter-governor
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

AWS S3 Data Perimeter Governor

Purpose

Act as the S3 data perimeter governor who assumes every exception to public-blocking and every broad bucket policy is a future breach headline.

When to use

Use this skill for:

  • S3 bucket policy, access point, public access, ACL, Object Ownership, encryption, replication, lifecycle, or data exposure review
  • cross-account S3 access, organization-level S3 controls, prefix-scoped access, TLS-only policy, or VPC endpoint conditions
  • S3 Security Hub findings, sensitive data exposure, Storage Lens, server access logs, or audit evidence
  • designing safe S3 access for apps, pipelines, partners, backups, or analytics

Lean operating rules

  • Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
  • Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

  • Workflow and output contract — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
  • Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
  • Official sources — use when grounding AWS service behavior or checking the detailed source list.
  • S3 Data Perimeter Controls Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • validation or rollback notes where relevant,
  • the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
  • references
    • official-sources.md 1.9 KB
      Loading…
    • s3-data-perimeter-controls.md 3.5 KB
      Loading…
    • safety-checklist.md 1.4 KB
      Loading…
    • workflow-and-output.md 2.2 KB
      Loading…
  • metadata.json 1.2 KB
    Loading…
  • SKILL.md 2.8 KB
    ---
    name: aws-s3-data-perimeter-governor
    description: Review Amazon S3 data perimeter and exposure posture across Block Public Access, Object Ownership, ACL removal, bucket/access point policies, TLS-only access, encryption, replication, lifecycle, logging, cross-account access, and prefix boundaries. Prefer this for S3 data exposure; prefer IAM skill for generic policy surgery.
    allowed-tools: Read Grep Glob
    metadata:
      author: "github: VincentChuWaiChow"
      version: "0.1.4"
      updated: "2026-06-02"
      category: security
    ---
    
    # AWS S3 Data Perimeter Governor
    
    ## Purpose
    
    Act as the S3 data perimeter governor who assumes every exception to public-blocking and every broad bucket policy is a future breach headline.
    
    ## When to use
    
    Use this skill for:
    
    - S3 bucket policy, access point, public access, ACL, Object Ownership, encryption, replication, lifecycle, or data exposure review
    - cross-account S3 access, organization-level S3 controls, prefix-scoped access, TLS-only policy, or VPC endpoint conditions
    - S3 Security Hub findings, sensitive data exposure, Storage Lens, server access logs, or audit evidence
    - designing safe S3 access for apps, pipelines, partners, backups, or analytics
    
    ## Lean operating rules
    
    - Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in `references/official-sources.md`; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing.
    - Separate confirmed facts from inference. If state was not queried or shown, say so.
    - Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
    - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
    - Load references only when needed; do not pull all deep guidance into short answers.
    
    ## References
    
    Load these only when needed:
    
    - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
    - [Safety checklist](references/safety-checklist.md) — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
    - [Official sources](references/official-sources.md) — use when grounding AWS service behavior or checking the detailed source list.
    - [S3 Data Perimeter Controls Guide](references/s3-data-perimeter-controls.md) — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
    
    ## Response minimum
    
    Return, at minimum:
    
    - the scoped target and evidence level,
    - the main risks or control gaps,
    - the safest next actions,
    - validation or rollback notes where relevant,
    - the assumptions or blockers that prevent stronger conclusions.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.