Content
63%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.
Highly actionable and well-sequenced with strong validation gates, but the body is a verbose monolithic recipe dump that duplicates its own reference files rather than acting as a progressive overview.
Suggestions
Move the inlined evasion/anti-forensics and persistence recipe sections into the existing references (evasion-cheatsheet.md, attack-playbooks.md) and keep SKILL.md as a lean overview pointing to them.
Trim generic technique-category explanations that restate knowledge Claude already has; retain only the concrete commands and tool mappings.
Consolidate the duplicated tool lists (in-body cheatsheet vs. routing table) into one tool-index reference to cut token overhead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~650-line body over-explains technique categories Claude already knows and inlines large recipe sections (evasion, anti-forensics, persistence, full tool cheatsheet) that duplicate the existing evasion-cheatsheet.md and attack-playbooks.md references rather than deferring to them. | 2 / 5 |
Actionability | Dense with concrete, copy-paste-ready commands and code across recon, exploitation, privesc, lateral movement, and cloud attacks, plus tables mapping techniques to tools and outcomes. | 5 / 5 |
Workflow Clarity | An 'ACTION REQUIRED' sequenced checklist with stage gates and auth.status checks, a decision tree, and the lifecycle-checklist.md reference provide clear sequencing and validation checkpoints, though some in-body gate detail is implicit. | 4 / 5 |
Progressive Disclosure | Section headers and three one-level reference files exist, but the bulk of the technique material is inlined directly in SKILL.md instead of being split out, so the overview is not a lean pointer to detailed materials. | 3 / 5 |
Total | 14 / 20 Passed |