Content
72%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 token-efficient, highly actionable AD/internal-domain attack cheatsheet that assumes Claude's expertise and surfaces current tactical context, but it is structured as a monolithic code block with no explicit workflow sequence or validation checkpoints for destructive operations.
Suggestions
Break the single code block into markdown sections (## Recon, ## Kerberos, ## ADCS, ## NTLM Relay, ## Domain CVEs, etc.) so techniques are navigable rather than a wall of text.
Add an explicit attack-chain workflow with validation checkpoints (e.g. verify relay success before escalating, confirm DCSync retrieved krbtgt before forging Golden Ticket) to lift workflow clarity above the destructive-operation cap of 3.
Expand the shorthand technique notes (e.g. ESC1, NoPac, PrintNightmare) into full copy-paste-ready commands or move detailed syntax into a reference file referenced one level deep.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean cheatsheet that assumes Claude's competence — it names tools, CVEs, and tactics ("certipy find -vulnerable", "secretsdump -just-dc → krbtgt hash→Golden Ticket") without explaining what BloodHound or Kerberoast are, and every line carries non-obvious tactical context such as "(比PtH重要,PtH常被EDR拦)". | 5 / 5 |
Actionability | It cites concrete executable tools and subcommands ("ntlmrelayx -t ldap --escalate-user", "certipy shadow", "responder抓NetNTLMv2→hashcat", "CONFIG SET dir写SSH key"), but several entries are shorthand ("ESC1指定SAN申域管证书") lacking the exact full command syntax, leaving minor gaps. | 4 / 5 |
Workflow Clarity | The body is a categorical catalog (recon → Kerberos → ADCS → relay → coerce → DACL → DCSync → CVEs → IPv6 → LLMNR → Linux) rather than an explicitly sequenced, numbered workflow, and contains no validation/verification checkpoints for these destructive attack operations, which caps the score at 3 per the destructive-operations guideline. | 3 / 5 |
Progressive Disclosure | The content is a single monolithic code block with emoji/pipe markers providing some categorical structure, but no markdown section headings and no split into separate reference files; while it is under 50 lines, the lack of well-organized sections keeps it below the simple-skill exception's 5 anchor. | 3 / 5 |
Total | 15 / 20 Passed |