Content
76%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 tight, highly actionable reference for NTLM relaying with excellent conciseness and concrete commands. The main gap is the absence of validation/verification checkpoints in destructive relay workflows, which caps workflow clarity.
Suggestions
Add explicit validation checkpoints after each destructive chain (e.g., verify the S4U2Proxy TGS grants access before declaring takeover; confirm msDS-KeyCredentialLink was written before auth-as-victim).
Inline or briefly summarize the ADCS relay chain instead of only deferring to the ad-certipy-esc-chain skill, so the primary relay-to-cert path is self-contained.
Consider moving the detailed per-chain command recipes and the mitigation/bypass table into reference files to improve progressive disclosure for a skill of this size.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and operational; assumes Claude's knowledge of AD/NTLM concepts with no 'what is NTLM' padding, and every line (matrices, commands, OPSEC notes) earns its place. | 5 / 5 |
Actionability | Provides copy-paste-ready, executable commands with real flags across the common chains; the ADCS chain is deferred to a sibling skill rather than shown inline, a minor gap. | 4 / 5 |
Workflow Clarity | Chains are sequenced (listener -> coerce -> S4U2Proxy), but this destructive/batch offensive skill has no validation checkpoints (e.g., confirm relay success, verify the ticket grants DA), so the destructive-operations cap of 3 applies. | 3 / 5 |
Progressive Disclosure | Well-organized single file with clear section headers and a one-level-deep external references list; no bundle files exist, but some per-chain recipes and the mitigation table could arguably split into reference files, and cross-skill pointers are textual rather than linked. | 4 / 5 |
Total | 16 / 20 Passed |