Content
76%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An extremely lean, command-first runbook with an unusually executable Lambda exfiltration path and good section organization. Weaknesses are procedural: validation checkpoints between phases are missing, there is no error-recovery guidance for the common failure modes, and a couple of Phase 1 commands contain ARN/version assumptions that will fail on real accounts.
Suggestions
Insert explicit verification checkpoints between phases, e.g. confirm the iam:PassRole statement's Resource matches the chosen target role ARN before create-function, and inspect the Lambda result/logs (`aws logs get-log-events`) when invoke returns an error or times out.
Add brief error-recovery guidance for the dominant failure mode: PassRole being denied on the chosen role (function creation fails with an unauthorize/PassRole error) — pick the next enumerated target rather than retrying.
Fix Phase 1 commands: resolve the policy's DefaultVersionId via `aws iam get-policy` instead of hardcoding `--version-id v1`, and use the customer-policy ARN namespace `arn:aws:iam::ACCT:policy/name` instead of `arn:aws:iam::aws:policy/`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is almost entirely executable commands, a dense permission table, and terse inline comments ("# who are you?", "# SSH into it; whoami is TARGET_ROLE") — zero concept explanation and no padding. This matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place"); it is not 4 because there are no over-explained passages to trim. | 5 / 5 |
Actionability | Mostly copy-paste-ready: the Lambda path is complete end-to-end (heredoc payload, zip, create-function, invoke, read output) and EC2/Glue/SageMaker snippets are concrete. It falls to anchor 4 ("minor gaps") rather than 5 because Phase 1's policy command assumes `--version-id v1` without resolving DefaultVersionId, uses the AWS-managed-policy ARN namespace `arn:aws:iam::aws:policy/` where a customer policy ARN is meant, and the `cut -d/ -f2` extraction breaks on role paths. | 4 / 5 |
Workflow Clarity | The phases are clearly sequenced (Enumerate → identify PassRole targets → execute as higher-priv role → cross-account chains → privesc classes → OPSEC), but validation checkpoints are implicit at best — no step verifies that PassRole's Resource matches the target ARN before create-function, and no error recovery exists for the most common failure (invoke failing or timing out). This matches anchor 3 ("sequence present but checkpoints missing or implicit"); it is not 4 because key checkpoints are absent rather than minor, and the state-changing create operations lack verification guidance, consistent with the destructive/batch cap. | 3 / 5 |
Progressive Disclosure | A single well-organized file with clear section headers, no nested references, and a signaled external tool pointer (Pacu link); the References section is compact. This matches anchor 4 ("Good structure; most content is appropriately placed; minor organization gaps") — it is not 5 because at ~120 lines the Phase 4 permission table and reference detail could live in a one-level-deep references/ file for a leaner main skill, and the under-50-line simple-skill exception does not apply. | 4 / 5 |
Total | 16 / 20 Passed |