Content
80%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.
An exceptionally actionable, token-efficient methodology body whose main weaknesses are structural: destructive flash/write operations proceed without validation checkpoints, and the entire multi-domain playbook is inlined in one large file rather than split across one-level-deep reference files. Both issues are fixable without touching the strong command content.
Suggestions
Add explicit validation checkpoints around destructive operations: verify the flash dump (compare size/entropy, `flashrom --verify`) before any MTD write or re-flash, and re-read back partitions after `mtd_debug write` to confirm the image landed correctly.
Add a post-exploitation verification step to the Quick Workflow and Engagement Checklist (e.g., confirm shell persistence and document state changes) so each destructive step has a feedback loop.
Split the large subdomain playbooks (Wireless Protocols, ICS/OT Protocols, RTOS/MCU, Companion App/Cloud API) into one-level-deep reference files under references/ with clearly signaled links from SKILL.md, keeping the main file as a workflow-oriented overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-dense and nearly every line delivers niche knowledge Claude lacks ('8-pin SOIC = SPI NOR; BGA = eMMC', 'Always try root/<serial number>', 'GoAhead, Boa, mini_httpd — abandoned codebases'); it assumes competence and avoids explaining known concepts. | 5 / 5 |
Actionability | Nearly every section has copy-paste-ready commands (flashrom, binwalk, openocd, gatttool, mosquitto_sub, mitmproxy, a pymodbus snippet, rtl_433) plus concrete specifics like default-credential lists and the Touchlink master key; the fault-injection block is procedural, which is inherent to hardware timing attacks. | 5 / 5 |
Workflow Clarity | The Quick Workflow and Engagement Checklist give a clear, coherent sequence, but destructive operations — MTD writes ('mtd_debug erase/write ... implant.bin'), re-flashing, and chip-off desoldering — lack validation/verification checkpoints (no dump-verify before write, no post-write check), capping this dimension per the destructive-operations rule. | 3 / 5 |
Progressive Disclosure | No bundle files exist and ~430 lines covering distinct subdomains (wireless protocols, ICS/OT, RTOS, companion app/cloud) are all inlined in SKILL.md — content that clearly belongs in separate reference files; good section headers keep it navigable, which lifts it above the 'minimal structure' anchor. | 3 / 5 |
Total | 16 / 20 Passed |