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.
An actionable, well-gated offensive-security runbook: concrete executable commands for every phase, an explicit RoE checkpoint before the loud fallback, and compact non-obvious domain detail (chipset vulnerabilities, lockout behavior). Minor room to trim the PIN-math explanation and to show failure-mode output alongside the success example.
Suggestions
Show what failed Pixie-Dust output looks like (e.g., reaver hanging on M5/M6 or random nonces in -vv output) so the fallback trigger in Step 3 is a concrete signal, not a judgment call.
Trim the PIN-space arithmetic ('10^8 but the last digit is a checksum... Total: ~11,000 attempts') to one line — Claude already knows the WPS PIN split.
Add a brief verification step after PSK recovery (e.g., confirm with wpa_supplicant or a controlled client association) so the workflow closes with an explicit checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean: flags are annotated as inline comments, the chipset table is compact, and the genuinely non-obvious domain knowledge (vulnerable chipsets, years, lockout behavior) earns its tokens. The PIN-space math paragraph (10^8, checksum digit, ~11,000 attempts) explains something Claude already knows, making this anchor 4 ('minor instances of over-explanation') rather than 5, and well above anchor 3. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout — 'sudo wash -i <mon-iface> --ignore-fcs', 'sudo reaver -i <mon-iface> -b <BSSID> -c <CHANNEL> -K 1 -vv -N', 'sudo bully <mon-iface> -b <BSSID> -c <CHANNEL> -d -v 3', plus '-p <known_PIN>' re-extraction — with every flag explained inline and expected success output shown ('[+] WPS PIN: ... [+] WPA PSK: ...'). Common cases (scan, primary attack, fallback, known-PIN recovery) are all covered — anchor 5. | 5 / 5 |
Workflow Clarity | A clear four-step sequence with an explicit HARD STOP gate before the destructive/loud online brute, lockout handling via '--lock-delay=60', and a defined fallback branch ('If Pixie-Dust fails (nonces are random), fall back'). It falls short of anchor 5 because the pixie-dust failure-mode output is not shown (only success output), and there is no step verifying the recovered PSK actually authenticates; it is clearly above anchor 3 since gating and error-recovery checkpoints are present. | 4 / 5 |
Progressive Disclosure | A single self-contained SKILL.md with well-organized, clearly headed sections and easy navigation; no bundle files exist, so nothing is buried or nested. Anchor 4 rather than 5 because the chipset vulnerability table and external reference links could live in a separate reference file, and standalone pixiewps usage (shown in ZFP as 'pixiewps -e <ES1> -r <ES2> ...') is not surfaced as its own step or pointer. | 4 / 5 |
Total | 17 / 20 Passed |