Provides cloud, container and Kubernetes attack techniques for CTF challenges. Use when a challenge involves AWS, Azure or GCP credentials, instance metadata (169.254.169.254), S3 or blob storage, IAM policies, ECS task roles, Lambda, a Kubernetes service-account token or kubelet, a Docker socket or container escape, a privileged pod, CI/CD runner secrets, or leaked Terraform and cloud-init configuration. Also use when an SSRF reaches a metadata endpoint or cloud credentials appear in an environment, config file or response. Do not use it for plain web application bugs with no cloud layer, native binary memory corruption, or disk and memory forensics.
cp -r cryptoskill/skills/dev-tools/abhay2008-ctf-cloud .claude/skills/clawhub install abhay2008-ctf-cloudCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
unknown
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed