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.
81
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aws-penetration-testing/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and domain-relevant trigger terms that security professionals would naturally use. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The description is well-scoped to a clear niche, making it highly distinguishable from other skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about AWS penetration testing, cloud security assessments, red teaming AWS infrastructure, or exploiting AWS services like IAM, S3, or Lambda.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence techniques. These are well-defined, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific techniques, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain context, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'penetration testing', 'AWS', 'IAM', 'privilege escalation', 'SSRF', 'S3 bucket', 'Lambda', 'red team'. These cover the domain well and match how security professionals would phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: AWS cloud penetration testing and red team operations. The combination of AWS-specific services (IAM, S3, Lambda) with offensive security techniques makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and highly actionable AWS penetration testing skill with executable commands throughout and good structural organization. Its main weaknesses are the lack of validation checkpoints in multi-step workflows (especially for destructive operations like CloudTrail deletion or privilege escalation) and some unnecessary verbosity in explanatory text that Claude already understands. The progressive disclosure is well-handled with advanced content properly referenced.
Suggestions
Add explicit validation/verification steps after critical actions (e.g., 'Verify policy attached: aws iam list-attached-user-policies --user-name my_username' after privilege escalation steps)
Remove explanatory sentences Claude already knows, such as 'Systems Manager allows command execution on EC2 instances' and the Purpose section that duplicates the description
Add feedback loops for error recovery in the core workflow, especially around permission enumeration failures and credential extraction steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity like the 'Purpose' section restating the description, the 'When to Use' boilerplate at the end, and some explanatory text that Claude wouldn't need (e.g., 'Systems Manager allows command execution on EC2 instances'). The tool table installation column and some section headers could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable bash commands and Python code throughout, with specific CLI syntax, real flag names, and concrete examples. Commands are copy-paste ready with clear placeholders for variable values. | 3 / 3 |
Workflow Clarity | The core workflow has numbered steps (1-3) but lacks validation checkpoints between steps. For destructive/risky operations like disabling CloudTrail, modifying Lambda code, or attaching admin policies, there are no verification steps or feedback loops to confirm success before proceeding. The constraints section mentions documentation but doesn't integrate verification into the workflow itself. | 2 / 3 |
Progressive Disclosure | The skill provides a well-structured overview with clear sections, a quick reference table, and appropriately defers advanced topics (Lambda/API Gateway, Secrets Manager, container security, etc.) to a single referenced file. Navigation is clear with one level of depth. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
43280f9
- Reviewed
Table of Contents
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.