Content
81%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.
A highly actionable skill body with executable commands throughout and exemplary dry-run/validate workflows for destructive and batch operations. Its weaknesses are redundancy (Best Practices and Example 1 repeat earlier content) and incomplete bundle navigation (unreferenced scripts/ files, pathless reference links).
Suggestions
Remove the duplication between Step 2/Step 3 and later sections: Best Practices items 2-4 restate the Beast Mode Principles, and Example 1 repeats the bulk-EC2-stop snippet from Step 3 — cutting these tightens the body without losing information.
Add pointers to the scripts/ bundle files (aws-blast.sh, jmespath-templates.json) in the body — e.g., in Step 4 or the Examples section — so Claude can actually discover and use them.
Cite the reference guides by their full relative path (references/compute-mastery.md, etc.) in Step 4 so navigation from SKILL.md is unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly commands with no concept over-explanation, but Best Practices items 2-4 restate the Step 2 Beast Mode Principles (dry-run, server-side JMESPath filtering, waiters, profiles) and Example 1 duplicates the Step 3 bulk-EC2-stop snippet — a full section's worth of self-repetition that should be tightened, fitting the 'could be tightened' anchor better than 'minor instances'. | 3 / 5 |
Actionability | Every example is a complete, copy-paste-ready bash command with real filters, JMESPath queries, and output flags (e.g., the bulk-stop xargs pipeline, the S3 sync with --sse/--storage-class, the IAM simulate-principal-policy loop), covering the common cases exactly as the anchor-5 example does. | 5 / 5 |
Workflow Clarity | Steps 1-4 are clearly sequenced, and destructive/batch operations have explicit validation feedback loops: "Dry-run first: Always validate with --dryrun", "Review output, then remove --dryrun only if satisfied", "Confirm list, then pipe to stop command", and "Confirm IDs, then execute" — matching the anchor-5 validate-then-proceed pattern, so the batch-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | Step 4 clearly signals four one-level-deep reference guides that all exist in references/ with no further nesting, but they are cited by bare filename without a path, and the scripts/ bundle files (aws-blast.sh, jmespath-templates.json) are never mentioned anywhere in the body, leaving them undiscoverable — minor organization gaps rather than the fully well-signaled anchor. | 4 / 5 |
Total | 17 / 20 Passed |