Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable body with concrete build/config/command examples, but it is somewhat verbose (general EDR concept padding and a repeated Ekko explanation), lacks validation checkpoints in the build/deploy workflow, and keeps content that could be externalized inline.
Suggestions
Tighten conciseness by removing general EDR/background explanations ('Most EDRs hook NtAllocateVirtualMemory...') that Claude already knows, and consolidate the Ekko explanation so it appears once.
Add an explicit validation checkpoint in the build workflow — e.g. after starting the teamserver, verify the listener is up before building/dropping the Demon — to lift workflow_clarity.
Move the Havoc-vs-Sliver-vs-Mythic-vs-CS comparison table and the OPSEC deep-dive into separate reference files (e.g. COMPARISON.md, OPSEC.md) referenced one level deep from SKILL.md to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient Havoc-specific detail, but includes general EDR concept explanations Claude already knows ('Most EDRs hook NtAllocateVirtualMemory...') and repeats Ekko twice (build steps and OPSEC section). | 2 / 3 |
Actionability | Provides copy-paste-ready build commands, a complete HCL profile example, a numbered Demon-build sequence, and concrete operator commands — fully executable guidance. | 3 / 3 |
Workflow Clarity | A clear setup→configure→build→deploy sequence exists, but there are no validation checkpoints (e.g. verify the teamserver/listener is live before building the Demon, confirm a check-in). | 2 / 3 |
Progressive Disclosure | Well-organized into sections, but everything is inline in one file — the comparison table, the OPSEC deep-dive, and the full profile reference could be split into one-level-deep reference files rather than living in SKILL.md. | 2 / 3 |
Total | 9 / 12 Passed |