Content
86%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 lean, well-structured operator index that routes on concrete airodump column values, gates execution on hardware mode with an explicit blocked outcome, and cross-references OPSEC posture per technique. The only shortcomings are minor: the elided airodump command and the absence of error-recovery guidance after a failed capture or check.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense routing signal — a playbook table, a column-to-leaf decision tree, a hardware-mode gate, a node-contract table, and an OPSEC matrix — with zero padding and no explanation of concepts Claude already knows (no "what is WPA2" prose). Every section earns its place, matching the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | Concrete, executable routing logic throughout: "airodump-ng --write-interval 1 --output-format csv ... Read the ENC/CIPHER/AUTH columns", explicit mappings like "ENC=WPA3, AUTH=SAE → wpa3-sae", and a real config path "plan/roe.json:machine_enforcement.wireless.mode" with per-mode behavior. It falls short of fully copy-paste-ready only because the airodump invocation is elided with "..." and "ssh <dropbox> -- '<cmd>'" is a placeholder pattern — minor gaps, so anchor 4 rather than 5. | 4 / 5 |
Workflow Clarity | A coherent sequence with explicit checkpoints: pre-flight verification ("Verify the configured hardware mode and authorized wireless scope before using a leaf skill"), a refuse gate ("'none' → refuse, return outcome=blocked"), and a post-selection checklist ("After selecting the primary leaf, always check: deauth-pmf... krack-fragattacks"). Missing error-recovery feedback loops (e.g., what to do when the WPS column is empty or monitor mode fails) keeps it below the anchor-5 bar; the checkpoints are explicit, so it is above anchor 3. | 4 / 5 |
Progressive Disclosure | This is a pure index with well-signaled, one-level-deep references: each of the seven leaf skills is linked once from the playbook table (e.g., "[wpa2-psk](wpa2-psk/SKILL.md)") with its trigger and MITRE mapping, no detail is inlined that belongs in a leaf, and non-802.11 RF is delegated to the iot/ suite. No bundle files exist in this skill, and navigation via the trigger table is trivial — a clear match for the anchor-5 example of an overview with clean one-level references. | 5 / 5 |
Total | 18 / 20 Passed |