z-wave

Z-Wave S0 network-key derivation flaw exploitation, S2 ECDH/DSK analysis, replay attacks against unauthenticated Z-Wave nodes, traffic capture with RTL-SDR, and active fuzzing/replay with EZ-Wave and Z-Force. Covers 868.42 MHz (EU) and 908.42 MHz (US) bands.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/iot/z-wave/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and reasonably concise with a clear phased workflow, but it lacks validation checkpoints for destructive replay/injection operations and keeps all detail inlined rather than split across bundle files.

Suggestions

Insert explicit validation checkpoints before destructive steps (e.g., 'Verify the captured frame's HomeID matches the target before replaying; abort if mismatched').

Move the S0/S2 protocol background, frequency table, and full command-class reference into a references/ bundle file and link from SKILL.md to improve progressive disclosure.

Trim the opening blockquote and inline XOR-triviality comments to reduce over-explanation of concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and code, but the opening blockquote retelling S0/S2 history and inline comments restating that the all-zero XOR is 'trivially reversible' add minor over-explanation Claude already knows.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready commands (rtl_sdr, hackrf_transfer, ezwave.py, zforce inject) with only minor gaps such as the illustrative check_dsk_mismatch depending on captured data not shown.	4 / 5
Workflow Clarity	A clear five-phase sequence exists, but this is a destructive/offensive skill (door-lock replay, key extraction) and it lacks explicit validate→fix→retry checkpoints before replay/injection; the Evidence section adds post-hoc hashing but no in-workflow verification, so the destructive-skill cap of 3 applies.	3 / 5
Progressive Disclosure	Headers give structure, but no bundle files exist (references/scripts/assets absent) and all content — frequency tables, full code, protocol detail — is inlined in a single SKILL.md with only external links, so it sits between minimal structure and well-split references.	3 / 5
	Total	14 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-targeted to the Z-Wave security niche with strong trigger terms and low conflict risk, but it omits an explicit 'Use when...' trigger clause, which caps its completeness at the midpoint.

Suggestions

Add an explicit 'Use when...' clause naming the trigger conditions (e.g., 'Use when assessing Z-Wave smart-home devices, extracting S0/S2 network keys, or replaying frames against unauthenticated nodes').

Surface a user-facing synonym like 'IoT' or 'smart home protocol' so the description matches natural phrasing beyond protocol jargon.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with named tools — 'network-key derivation flaw exploitation', 'S2 ECDH/DSK analysis', 'replay attacks against unauthenticated Z-Wave nodes', 'traffic capture with RTL-SDR', 'active fuzzing/replay with EZ-Wave and Z-Force' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines a missing 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Comprehensive natural terms and synonyms users would say — 'Z-Wave', 'S0', 'S2', 'ECDH', 'DSK', 'EZ-Wave', 'Z-Force', 'replay', 'unauthenticated', 'smart home', '868 MHz', '908 MHz', 'RTL-SDR', 'network key' — covering the niche's vocabulary.	5 / 5
Distinctiveness Conflict Risk	A clear Z-Wave-specific niche with distinct protocol/tool triggers and minimal overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: PurpleAILAB/Decepticon
Path: packages/decepticon/decepticon/skills/standard/iot/z-wave/SKILL.md
Commit: 31e1c8e

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.