transilienceai/communitytools

cloud-containers

Cloud and container security testing - AWS, Azure, GCP, Docker, and Kubernetes misconfigurations and exploitation.

First seen Mar 21, 2026

Installation

$ npx skills add transilienceai/communitytools --skill cloud-containers

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from transilienceai/communitytools · top by installs.

npx skills add transilienceai/communitytools

Browse all from transilienceai/communitytools

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 516
License LICENSE
Default branch main
Open issues 8
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,908 B
  • docs SUMMARY.md 138 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 124 installs

SKILL.md

Cloud & Containers

Test cloud infrastructure and container environments for security misconfigurations and exploitation paths.

Techniques

Platform Key Vectors
AWS S3 bucket exposure, IAM misconfig, metadata service, Lambda abuse
Azure Blob storage, RBAC flaws, managed identity, App Service misconfig
GCP Cloud Storage, service account keys, metadata server, IAM
Docker Container escape, privileged mode, socket exposure, image vulnerabilities
Kubernetes RBAC bypass, secret exposure, pod escape, API server access

Workflow

  1. Enumerate cloud resources and services
  2. Test IAM/RBAC configurations
  3. Check storage and secrets exposure
  4. Test container isolation and escape paths
  5. Document findings with cloud-specific evidence

Two lanes — attack vs assess

This skill covers both, and they are different jobs producing different artifacts. Do not mix them in one deliverable.

Lane You have You produce Start at
Offensive a cloud target to attack exploited findings with a PoC [reference/INDEX.md](reference/INDEX.md)
Posture read-only credentials and a "review the configuration" ask one evidenced verdict per control in a pinned catalogue [reference/posture/INDEX.md](reference/posture/INDEX.md)

Reference

  • [reference/INDEX.md](reference/INDEX.md) - Router for platform-specific attack scenarios (AWS, Azure, GCP, Docker, K8s)
  • [reference/posture/INDEX.md](reference/posture/INDEX.md) - Credentialed read-only configuration review (CSPM): run order, verdict vocabulary, the four false-pass traps, pinned catalogues, and the licensing rule for benchmark-derived content