wireless-hardware-attack

无线/硬件:WiFi PMKID/WPS/Evil Twin,BLE,Zigbee,NFC,SDR,UART/JTAG/SPI,侧信道,故障注入。Use when attacking WiFi, BLE, RFID, SDR, or hardware interfaces.

Quality

75%

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 ./skills/wireless-hardware-attack/SKILL.md

Quality

Content

66%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 content is token-efficient and names specific tools, but it functions as a flat reference table rather than a sequenced workflow, with no validation steps for destructive attacks and no section structure for navigation.

Suggestions

Add a multi-step attack workflow with explicit validation checkpoints (e.g., verify a captured handshake exists before cracking, confirm firmware dump integrity after SPI read) so destructive operations cannot proceed unverified.

Break the monolithic code block into markdown sections with headers (WiFi / BLE / NFC / Hardware) to improve navigability and progressive disclosure.

Expand key tool entries with copy-paste command syntax (e.g., full hcxdumptool and hashcat invocation) rather than just tool names to lift actionability toward fully executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is a lean, high-density cheat sheet that assumes Claude's competence and explains no background concepts; every token earns its place.	5 / 5
Actionability	Concrete tools and techniques are named ("aircrack-ng/PMKID(hcxdumptool+hashcat)", "binwalk -Me", "SPI flash dump"), but most entries lack full copy-paste command syntax, leaving minor gaps.	4 / 5
Workflow Clarity	The body is a flat reference table with no multi-step sequence and no validation checkpoints for destructive operations (firmware dump, fault injection); the destructive-operations cap and absent sequence pull this well below midpoint.	2 / 5
Progressive Disclosure	No bundle files exist and the content is a single monolithic code block with categorical prefixes but no markdown section headers or navigation, giving only modest structure.	3 / 5
	Total	14 / 20 Passed

Description

83%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 dense, specific, and includes an explicit trigger clause covering both what and when, using third-person voice. It is slightly jargon-heavy and has minor overlap with general pentest skills.

Dimension	Reasoning	Score
Specificity	Names many concrete attack techniques and tools ("WiFi PMKID/WPS/Evil Twin", "UART/JTAG/SPI", "侧信道,故障注入"), but they are domain items rather than explicit verb-action phrases, leaving a minor framing gap versus the comprehensive-action anchor.	4 / 5
Completeness	A clear "what" (enumerated wireless/hardware attack surfaces) is paired with an explicit "when" trigger clause using concrete phrases, satisfying both halves.	5 / 5
Trigger Term Quality	"Use when attacking WiFi, BLE, RFID, SDR, or hardware interfaces" provides good natural keyword coverage, though a few common synonyms (e.g. Bluetooth, 802.11) are absent.	4 / 5
Distinctiveness Conflict Risk	The wireless/hardware attack niche is distinct with specific triggers, but there is minor overlap risk with broader penetration-testing or red-team skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: Ed1s0nZ/CyberStrikeAI
Path: skills/wireless-hardware-attack/SKILL.md
Commit: 893f134

Reviewed: 2 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.