Content
78%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 well-structured, lean, highly actionable tiered runbook with genuinely useful troubleshooting and OPSEC content. The main defects are localized executability slips (screen baud loop, U-Boot dump labeling) and a References entry pointing to a file that is missing from the bundle.
Suggestions
Create references/ch341a-soic-wiring.md (or remove the References entry) so the body's only bundle pointer resolves to a real file.
Fix the U-Boot section: `loady` receives a file over XMODEM from the host — replace the mislabeled 'Dump via XMODEM' comment with the actual capture-and-convert flow already shown via `md.b`, and note the `sf read` + `tftp` path (1c) as the preferred full-flash method.
Add a post-acquisition validation step (e.g., `binwalk`/`file` on the final image, and size check against the chip's nominal capacity) before declaring the binary ready for static analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a dense runbook: terse code blocks with instructive one-line comments, and the prose that exists ("flashrom sees 0x00 or 0xFF → chip held in reset by SoC pull-downs", the OPSEC notes) is operational knowledge Claude would not already have. No padding or explanation of known concepts. Not score 4: there are no real instances of over-explanation to trim. | 5 / 5 |
Actionability | Most guidance is copy-paste-ready (arpspoof/mitmproxy chains, flashrom probe→dump→cmp double-read, openocd dump_image, dd + mount loop with computed offset), but a few spots fall short of fully executable: the `screen` baud-probe `for` loop cannot work as written since screen is interactive, the U-Boot block's `loady`/`md.b` sequence is mislabeled as a dump-to-host path, and Tier 3c leans on a vague "nanddump equivalent". Not score 3: the gaps are minor and localized, not pseudocode-level. | 4 / 5 |
Workflow Clarity | The tiered sequence is explicit and justified ("cheapest and least invasive first"), prerequisites are listed, and destructive/batch operations do have verification — checksum-verify before unpacking (0a), a double-read + sha256 + cmp feedback loop with a re-seat-clip recovery action (3a), and lsblk size confirmation before/after dd (4b). Not score 5: Tier 1 (UART hex-capture) and Tier 2 (JTAG/OpenOCD) dumps lack any validation checkpoint, and there is no final image-validity check (e.g., `binwalk`/`file`) before handing off to static analysis. | 4 / 5 |
Progressive Disclosure | Section structure is clean (prerequisites → Tier 0–4 → evidence → OPSEC → references), but the only bundle reference, `references/ch341a-soic-wiring.md` in the References section, does not exist — no references/, scripts/, or assets/ directories are present in the skill bundle, making it a dangling pointer. Scored against the actual bundle structure, a broken cross-file reference is more than a minor organization gap, so this sits below the anchor 4 ("references mostly clear") rather than above anchor 3. | 3 / 5 |
Total | 16 / 20 Passed |