Content
57%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.
The body is information-rich with strong concrete commands and good section structure, but it is verbose, lacks validation feedback loops for destructive network-device operations, and keeps all detail inline with no reference files.
Suggestions
Add explicit validate/verify-retry checkpoints to the emulation guidance (e.g., verify config diff and validate reachability before proceeding after router/SPAN changes).
Move the large TTP-by-tactic mapping, malware signature table, and detection rules into separate reference files (e.g., TTPS.md, TOOLING.md, DETECTION.md) and link to them one level deep.
Tighten the intro paragraph and de-duplicate campaign/tool mentions that recur across the Attribution, Campaigns, and Tooling sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and avoids explaining basics Claude already knows, but the long intro prose and repetition of campaigns/tools across sections add padding that could be tightened. | 3 / 5 |
Actionability | Concrete, executable commands appear throughout (guestshell enable, monitor capture ... eq 49, no vstack, copy bootflash:tac.pcap ftp://..., double-encoded WSMA paths), with minor gaps where steps reference 'the payload-builder' abstractly. | 4 / 5 |
Workflow Clarity | The emulation plays are sequenced by tactic with concrete per-step commands, but the section lacks explicit validate/verify-retry checkpoints and involves destructive network-device operations, which caps workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | Headers organize the content well, but no bundle files exist and the large TTP table, malware catalog, and detection detail are all inlined rather than split into one-level-deep reference files. | 3 / 5 |
Total | 13 / 20 Passed |