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 content is highly actionable with concrete, executable commands and a clear sequenced methodology backed by validation gates, but it suffers from duplicated blocks across sections and a monolithic single-file structure with no progressive disclosure via bundle files.
Suggestions
De-duplicate the ToolShell 3-step chain, the Picker.aspx recon, and the 'download.aspx is NOT-SSRF' explanation — keep one canonical copy and cross-reference it from the other sections.
Split the long-form material (CVE/build matrix, full Payload & Detection Patterns, and the three Real Impact Examples) into separate reference files under ./references/ and link to them one level deep from SKILL.md to improve progressive disclosure.
Add explicit validate→fix→retry feedback loops at the fragile steps (e.g. Authentication.asmx Mode probe, ToolShell precondition chain) rather than only the final Gate 0 checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is operational and avoids explaining concepts Claude already knows, but contains noticeable redundancy — the ToolShell 3-step curl block, Picker.aspx recon, and the 'download.aspx is NOT-SSRF' caveat are each repeated across methodology steps, the Payload & Detection Patterns section, Gate 0, and the scenario writeups. | 3 / 5 |
Actionability | Provides fully copy-paste-ready curl commands with exact headers, SOAPAction URIs, complete SOAP XML bodies, exact endpoint paths, and decoded expected responses — covering the common SharePoint hunting cases comprehensively. | 5 / 5 |
Workflow Clarity | A clearly sequenced 10-step methodology plus a Gate 0 Validation checklist with repro-time gates and an explicit 'do not deliver the payload' safety rule; however explicit per-step validate→fix→retry feedback loops are limited rather than pervasive. | 4 / 5 |
Progressive Disclosure | No bundle files exist and all content is inlined into a single ~430-line SKILL.md; section headers give good structure, but the CVE/build matrix, full payload-pattern blocks, and three real-impact scenarios clearly belong in separate reference files. | 3 / 5 |
Total | 15 / 20 Passed |