Content
82%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 strong, actionability-first audit playbook: executable greps, slither commands, runnable Foundry PoCs, and a remediation template with no filler. Minor gaps are slight duplication (Parity told twice), an implicitly rather than explicitly sequenced workflow, and inline PoC/exemplar material that could be split into a references file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and code-first, assuming Claude already knows proxy mechanics ('Proxies separate storage (proxy) from logic (implementation)'), matching the 'efficient; minor instances of over-explanation that could be trimmed' anchor. It is not 5 because of small duplications — the Parity incident appears in both section 1 ('Parity multisig 2017 — $280M frozen') and the exemplars ('Parity multisig (Jul + Nov 2017): $30M stolen, $280M frozen'), and prose sometimes restates what code comments already say ('admin set in constructor, proxy reads 0x0'); it is not 3 because nearly all content is domain-specific value (incident details, exact commands) rather than explanation of known concepts. | 4 / 5 |
Actionability | Every section gives executable guidance: grep commands ('grep -rn '_authorizeUpgrade' src/'), tool invocations ('slither-check-upgradeability V1.sol V2.sol --proxy-name MyProxy'), copy-paste-ready Foundry PoC tests ('vm.prank(attacker); proxy.upgradeTo(malicious);'), and complete vulnerable/safe code pairs plus a remediation template. This matches the 'fully executable; copy-paste ready code or commands; specific examples cover the common cases' anchor — it is not 4 because the commands and tests are complete and runnable as written, with no missing key details. | 5 / 5 |
Workflow Clarity | A sequenced audit checklist (sections 1-8) each with its own verification command, followed by PoC templates for confirmation, a CVSS severity stage, and remediation with CI gates ('forge test --match-contract Test_Upgrade', 'slither-check-upgradeability V1 V2 in CI') — matching 'clear sequence with most checkpoints present; minor validation gaps'. It is not 5 because the checklist → PoC → CVSS → remediation progression is implied by layout rather than explicitly stated, and there is no guidance on what to do when a check hits vs. misses; it is not 3 because each check has an explicit verification command and the PoC templates serve as confirmation checkpoints. | 4 / 5 |
Progressive Disclosure | A single-file skill with no bundle directories (references/, scripts/, assets/ are absent) whose content is organized under clear headers ('Audit checklist', 'PoC template (Foundry)', 'CVSS', 'Defender remediation', 'Known exemplars') — matching 'good structure; most content is appropriately placed; minor organization gaps'. It is not 5 because at ~245 lines the PoC templates and incident exemplars are separable material that could live in a references file, keeping some detail inline that a well-split bundle would externalize; it is not 3 because no section is an oversized dump requiring extraction and navigation is easy. | 4 / 5 |
Total | 17 / 20 Passed |