Skip to content
TrustedSkillsbeta
Back to all skills

Cloud Penetration Testing

Listed
zebbern·vlatest·testing·MIT

Simulates cloud environment penetration tests, identifying vulnerabilities and misconfigurations within zebbern's simulated infrastructure.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add zebbern/claude-code-guide --skill cloud-penetration-testing -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

zebbern

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 3 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 4 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: 169.254.169.254, awscli.amazonaws.com, login.microsoftonline.com, sdk.cloud.google.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    awscli.amazonaws.comundeclaredsdk.cloud.google.comundeclaredlogin.microsoftonline.comundeclared169.254.169.254undeclaredmetadata.google.internallocal

    What it found (3 of 10)

    • skills/cloud-penetration-testing/SKILL.md:25contacts awscli.amazonaws.com
      curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
    • skills/cloud-penetration-testing/SKILL.md:29contacts sdk.cloud.google.com
      curl https://sdk.cloud.google.com | bash
    • skills/cloud-penetration-testing/SKILL.md:62contacts login.microsoftonline.com
      curl "https://login.microsoftonline.com/[email protected]&xml=1"
  • No credential access: failed

    Touches credential material in 1 place.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

    What it found

    • skills/cloud-penetration-testing/SKILL.md:352Google Cloud credentials
      sudo cp -r /home/user/.config/gcloud ~/.config
  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 1 place.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • skills/cloud-penetration-testing/SKILL.md:29remote script piped into a shell
      curl https://sdk.cloud.google.com | bash
  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • Pinned to a commit: passed

    Scanned zebbern/claude-code-guide at a2e6ee3bce.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
2 files, 759 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to perform comprehensive cloud penetration testing, simulating real-world attacks to identify security vulnerabilities in cloud infrastructure. It automates the discovery of misconfigurations and weak points across various cloud service providers.

When to use it

  • Conducting pre-deployment security audits for new cloud environments before going live.
  • Validating the effectiveness of existing security controls after configuration changes.
  • Preparing for compliance certifications that require proof of regular vulnerability scanning.
  • Simulating advanced persistent threats (APTs) to test incident response readiness.

Key capabilities

  • Automated scanning of cloud infrastructure for common misconfigurations.
  • Identification of exposed storage buckets and unsecured API endpoints.
  • Simulation of attack vectors specific to major cloud providers like AWS, Azure, and GCP.
  • Generation of detailed reports highlighting critical security gaps and remediation steps.

Example prompts

  • "Run a penetration test on our AWS S3 bucket configuration to find any public access issues."
  • "Identify potential entry points in our Azure Kubernetes Service cluster setup."
  • "Simulate an attack on our GCP load balancer rules to check for exposure vulnerabilities."

Tips & gotchas

Ensure you have explicit authorization from infrastructure owners before running penetration tests, as unauthorized scanning can violate cloud provider terms of service. Always scope the test to specific environments or accounts to avoid accidental disruption of production systems.