CtrlK
BlogDocsLog inGet started
Tessl Logo

wireless-overview

Top-level index for the Decepticon 802.11 wireless attack suite. Routes the WirelessOperator to the correct leaf skill based on the target AP's crypto column (PSK / SAE / MGT / WPS) and engagement posture. BLE, Zigbee, Z-Wave, LoRaWAN, and sub-GHz live under iot/ by design — link provided below to prevent duplication.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/wireless/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured routing index that is lean, actionable, and uses progressive disclosure effectively by deferring detail to leaf skills. Workflow clarity is strong with a mode-enforcement gate, though some destructive-operation validation is delegated to the leaves rather than restated.

DimensionReasoningScore

Conciseness

Lean and efficient: tables and decision trees carry the content with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Concrete, executable guidance throughout (airodump-ng invocation, plan/roe.json path, ssh dropbox pattern, explicit column-to-leaf mapping), with minor gaps such as the truncated airodump-ng flags and leaf-skill links that must be followed for full commands.

4 / 5

Workflow Clarity

Clear sequence (mode check -> airodump -> read columns -> select leaf -> check deauth/krack) with the mode-enforcement gate ('none -> refuse, return outcome=blocked') as a validation checkpoint and a post-selection check; minor validation gaps remain since destructive-op verification largely lives in the leaf skills.

4 / 5

Progressive Disclosure

Exemplary overview-index pattern: the body routes to one-level-deep leaf skills (wpa2-psk/SKILL.md, etc.) via a clearly signaled playbook table, with detail appropriately split into the leaves and easy navigation.

5 / 5

Total

18

/

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 well-targeted, specific routing description with strong distinctiveness, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Trigger-term coverage is good though a few natural phrasings are missing from the description text.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g. 'Use when targeting Wi-Fi/802.11 networks for PSK, SAE, enterprise EAP, WPS, evil-twin, or deauth operations').

Surface a few common user phrasings currently only in metadata.when_to_use (Wi-Fi, evil-twin, deauth) into the description itself.

Briefly state the engagement-posture routing in trigger terms so the 'when' covers posture context, not just crypto type.

DimensionReasoningScore

Specificity

Names the domain and several concrete routing actions keyed off the target AP's crypto column (PSK / SAE / MGT / WPS) and engagement posture; only minor coverage gaps for an index skill.

4 / 5

Completeness

The 'what' is clearly stated (routes to the correct leaf skill by crypto column and posture), but there is no explicit 'Use when...' clause or equivalent trigger guidance in the description, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Good coverage of natural/technical terms (802.11, wireless attack, PSK, SAE, MGT, WPS, BLE, Zigbee, Z-Wave, LoRaWAN, sub-GHz), but a few common user phrasings like Wi-Fi, evil-twin, and deauth are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

Clear niche (802.11 wireless attack routing) with an explicit boundary statement that BLE/Zigbee/Z-Wave/LoRaWAN/sub-GHz live under iot/ to prevent duplication, minimizing conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 7 missing

Warning

Total

13

/

16

Passed

Repository
PurpleAILAB/Decepticon
Reviewed

Table of Contents

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.