aws-penetration-testing

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/aws-penetration-testing/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, command-dense reference with good section structure and an appropriate external reference for advanced material. Its main weakness is workflow clarity: destructive operations lack explicit validation checkpoints despite a strong pre-flight confirmation gate.

Suggestions

Insert explicit validation checkpoints into destructive workflows (e.g. verify extracted credentials with `aws sts get-caller-identity` before escalating; confirm a snapshot was created before attaching it).

Remove the verbatim 'Purpose' restatement of the description and the redundant 'Quick Reference' table to tighten token use.

Add a short 'Validate / clean up' step at the end of destructive sections (CloudTrail disabling, EBS snapshot attacks) to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly lean, command-driven content with little concept padding, but the 'Purpose' section restates the description verbatim and the 'Quick Reference' table duplicates already-shown commands — minor trim opportunities.	4 / 5
Actionability	Copy-paste-ready executable AWS CLI and boto3 commands throughout, with concrete worked examples (SSRF-to-admin walkthrough, Lambda code injection) covering the common cases.	5 / 5
Workflow Clarity	An initial Core Workflow sequence exists and a mandatory confirmation gate precedes destructive actions, but the destructive/batch operations (CloudTrail disabling, key creation, persistence) lack validate-then-proceed checkpoints, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-sectioned body with a clearly signaled, one-level-deep reference (references/advanced-aws-pentesting.md, verified present) for advanced topics; the main file is fairly dense and could split further, keeping it just below a 5.	4 / 5
	Total	16 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, distinctive description listing concrete AWS pentesting actions, but it lacks an explicit 'when to use' trigger clause which caps completeness. Third-person/imperative voice is correctly used throughout.

Suggestions

Add an explicit 'Use when...' clause naming the trigger situations (e.g. 'Use when performing authorized AWS penetration tests, red team engagements, or cloud security assessments').

Include natural synonyms users say, such as 'AWS pentesting' or 'cloud security assessment', alongside the current technical terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence techniques' — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	The 'what' is clear and detailed, but there is no explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Strong natural terms ('penetration testing', 'AWS cloud environments', 'red team operations', 'privilege escalation', 'SSRF') that a user would plausibly say, but missing common synonyms/extensions like 'AWS pentesting' or 'cloud security assessment'.	4 / 5
Distinctiveness Conflict Risk	AWS-specific technique set (IMDS SSRF, Lambda extraction, S3 exploitation) carves a clear niche with minimal overlap against generic cloud or code skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/aws-penetration-testing/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.