aws-penetration-testing-v2

name	aws-penetration-testing-v2
description	AWS Penetration Testing workflow skill. Use this skill when the user needs Provide comprehensive techniques for penetration testing AWS cloud environments. Covers IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence techniques for red team operations and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
version	0.0.1
category	testing-security
tags	["aws-penetration-testing-v2","aws-penetration-testing","provide","comprehensive","techniques","for","penetration","testing"]
complexity	advanced
risk	caution
tools	["codex-cli","claude-code","cursor","gemini-cli","opencode"]
source	community
author	zebbern
date_added	2026-04-19
date_updated	2026-04-25

AWS Penetration Testing

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/aws-penetration-testing from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments. # AWS Penetration Testing

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Purpose, Inputs/Prerequisites, Outputs/Deliverables, Essential Tools, Privilege Escalation Techniques, S3 Bucket Exploitation.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: Provide comprehensive techniques for penetration testing AWS cloud environments. Covers IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence....
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

Situation	Start here	Why it matters
First-time use	metadata.json	Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review	ORIGIN.md	Gives reviewers a plain-language audit trail for the imported source