Content
65%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-sectioned, command-rich body that gives an operator concrete entry points for Zigbee, Thread, and Matter attacks. Its main weaknesses are the absence of validation checkpoints for destructive operations (capping workflow clarity), one elided code example, and no progressive disclosure structure in a 165-line single file.
Suggestions
Add explicit validation checkpoints to the workflow, e.g., 'Confirm the pcap contains the transport-key-encrypted network key before attempting recovery' and 'Verify the recovered network key decrypts existing captures in Wireshark before injecting ZCL commands' — required because factory_reset_request and device-theft steps are destructive.
Replace the elided scapy frame 'Dot15d4FCS()/Dot15d4Data()/ZigbeeNWK(...)/ZigbeeAppDataPayload(...)/ZCLDoorLock(...)' with a complete, executable frame construction including real field values (source/destination addresses, profile, cluster, sequence).
Move the Thread and Matter sections and the hardware table into separate reference files (e.g., references/thread-matter.md, references/hardware.md) and keep SKILL.md as a lean overview pointing to them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and command-driven with little padding, but a few sentences restate background Claude already knows (e.g., 'Matter unifies Zigbee/Thread/Wi-Fi device onboarding under one commissioning model', the opening mesh-protocol overview), which could be trimmed. It is noticeably above the 'mostly efficient' midpoint anchor, fitting 'efficient; minor instances of over-explanation'. | 4 / 5 |
Actionability | Mostly executable guidance: zbstumbler/zbdump/zbid, z3sec commands with real flags, and scapy imports are concrete and runnable. However, the flagship ZCL door-lock frame is elided ('ZigbeeNWK(...)/ZigbeeAppDataPayload(...)/ZCLDoorLock(...)') and cheatsheet step 5 says only '(custom scapy-dot15d4 + zbee_nwk frames)', which are gaps that keep it below fully copy-paste ready. | 4 / 5 |
Workflow Clarity | The sequence is clearly laid out twice (Quick Workflow and the numbered Engagement Cheatsheet), but there are no validation or verification checkpoints anywhere — e.g., confirming the captured join exchange actually contains the encrypted network key before attempting decryption, or verifying the recovered key decrypts traffic before issuing ZCL commands. The rubric caps destructive/batch workflows without validation at 3, and this skill's core steps include factory resets and device theft. | 3 / 5 |
Progressive Disclosure | The single file has clear section headers, but at ~165 lines everything is inline — hardware tables, Thread and Matter specifics, the Touchlink derivation detail, and a references list — with no bundle files or split references, so content that could live in separate files is inlined and organization is only partially realized. | 3 / 5 |
Total | 14 / 20 Passed |