wireless-security

Wireless network security reconnaissance — WiFi analysis, Bluetooth assessment, RFID/NFC evaluation, signal capture, protocol analysis, encryption testing, rogue device detection.

Quality

61%

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/recon/wireless-security/SKILL.md

Quality

Content

53%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 an information-dense command catalogue that is mostly token-efficient, but it is a flat reference dump rather than a guided workflow: it contains malformed/non-standard commands and lacks any validation checkpoints for the destructive wireless attacks it describes. With no bundle files, progressive disclosure is minimal.

Suggestions

Add explicit validation/verification checkpoints for destructive and batch operations (e.g. confirm a captured WPA handshake with "hcxpcapngtool" before cracking; verify an evil-twin AP is running before deauth).

Fix malformed/non-standard commands ("airolump-ng"→"aircrack-ng"/"airodump-ng", "airecrack-ng"→"aircrack-ng", remove fictional "rfidtool" in favour of real tools like "proxmark3"/"mfoc").

Move the large tool reference into a separate reference file (e.g. references/TOOLS.md) and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	A dense catalogue of labelled commands that mostly assumes Claude's knowledge of the tools; minor over-explanation could be trimmed (e.g. the inline "# Requires GNU Radio setup" and tool-suite comments), but it is largely efficient.	4 / 5
Actionability	Concrete commands dominate the body, but several are malformed or non-executable as written (e.g. "airolump-ng", "airecrack-ng", "rfidtool --read", "gatttool -p /dev/null"), which leaves gaps between instruction and execution.	3 / 5
Workflow Clarity	Content is grouped by task area rather than sequenced into a workflow, and destructive/batch operations (deauth, evil twin, cloning, cracking) have no validation or verification checkpoints, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and the body is a monolithic ~360-line single-file command reference with no pointers to separate reference material, so content that would benefit from splitting is fully inlined.	2 / 5
	Total	12 / 20 Passed

Description

70%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.

A reasonably specific and distinctive description that names many concrete wireless-security capabilities, but it lacks an explicit "Use when..." trigger clause so it only answers "what" and not "when". Trigger-term coverage is good but could add synonyms like "wireless" and "wardriving".

Suggestions

Add an explicit trigger clause, e.g. "Use when performing wireless security testing, WiFi analysis, Bluetooth assessment, RFID/NFC evaluation, or wardriving."

Include common synonyms and file extensions a user might naturally say ("wireless", "wardriving", ".pcap") to broaden trigger-term coverage.

Consider mentioning the additional protocols covered in the body (Zigbee, Z-Wave, LoRaWAN) in the description for fuller coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas — "WiFi analysis", "Bluetooth assessment", "RFID/NFC evaluation", "signal capture", "protocol analysis", "encryption testing", "rogue device detection" — giving broad coverage with only minor gaps (e.g. Zigbee/LoRaWAN mentioned in the body but not the description).	4 / 5
Completeness	The "what" is clear (wireless security reconnaissance with enumerated activities) but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural user terms like "WiFi analysis", "Bluetooth assessment", "RFID", "NFC", and "signal capture", but misses common synonyms/extensions a user might say (e.g. "wireless", "wardriving" is only in metadata, no file extensions).	4 / 5
Distinctiveness Conflict Risk	Occupies a clear wireless-security niche with distinct triggers (WiFi/Bluetooth/RFID/NFC) and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/recon/wireless-security/SKILL.md
Commit: a04f96b

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