Content
71%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 a dense, operator-grade reference with strong actionability — real commands, config blocks, and decision tables rather than prose — and reasonable validation checkpoints (c2lint, ss, error table). Its weakness is structure: everything lives in one monolithic SKILL.md with no reference files, so a large profile example and lookup tables load into context even when not needed.
Suggestions
Split the full Malleable C2 profile example into a references/ file (e.g. references/malleable-profile.md) and link to it from section 4, keeping only the OPSEC-critical settings inline.
Move the Detection Signatures and Tools & Resources lookup tables into a references/ file and link them, leaving the Quick Reference and Decision Gate as the always-loaded overview.
Consider a references/ops-tables.md for the sleep/jitter and process-selection tables to shrink the SKILL.md footprint while keeping one-level-deep navigation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean command/config reference that assumes operator knowledge — almost every section is executable material rather than background explanation. Only the two-sentence intro ("Cobalt Strike is a commercial adversary simulation platform...") and mild overlap between the OPSEC Considerations and Detection Signatures tables could be trimmed, fitting 'efficient; minor instances of over-explanation'. | 4 / 5 |
Actionability | Concrete, mostly copy-paste-ready commands and config throughout ("./teamserver <TEAMSERVER_IP> <SHARED_PASSWORD> ...", "./c2lint /workspace/profiles/amazon.profile", "./build.sh pipe VirtualAlloc 310272 5 false false ...", exact sleep/jitter values). Some blocks are GUI-menu walkthroughs in comments rather than executable commands ("Attacks > Packages > Windows Executable (S)"), keeping it below the fully-executable 5 anchor. | 4 / 5 |
Workflow Clarity | Sections follow a logical setup sequence (teamserver → listeners → payload generation → profile → sleep → injection → arsenal) with explicit checkpoints: profile validation via c2lint ("If c2lint fails, the teamserver will refuse to load the profile"), teamserver verification via `ss -tlnp`, a Decision Gate tree, and an Error Handling table mapping symptoms to resolutions. Not 5 because the flow is presented as a reference rather than an ordered procedure with validate-then-proceed gating. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), and ~430 lines are inlined in SKILL.md — including a full ~75-line Malleable C2 profile example, detection-signature tables, and a tools list that clearly belong in separate reference files. Section headers are clear, so it sits at 'some structure but could be better organized; content that should be separate is inline' rather than the 2 anchor's 'minimal structure'. | 3 / 5 |
Total | 15 / 20 Passed |