CtrlK
BlogDocsLog inGet started
Tessl Logo

deauth-pmf

Targeted and broadcast 802.11 deauthentication / disassociation, 802.11w/PMF posture detection, and action-frame attack variants. Reusable by wpa2-psk (handshake), wpa3-sae (downgrade), and evil-twin (roaming coercion).

64

Quality

77%

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/deauth-pmf/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 skill body is a strong, actionable reference: executable code throughout, a clearly sequenced workflow with decision checkpoints and RoE gates for destructive actions, and a verification (ZFP) checklist. The only soft spot is mild verbosity in the intro/notes and limited progressive disclosure since everything is inline.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes domain competence, but the opening blockquote and a few explanatory notes (e.g., the mdk4 'does not disconnect clients' aside) could be trimmed; it sits above the midpoint but not fully token-minimal.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands and scripts across the common cases (airodump-ng, aireplay-ng targeted/broadcast, tshark RSN decoding, mdk4 floods, a scapy SA-Query test, and a kg_add_node evidence block), with standard parameterized placeholders.

5 / 5

Workflow Clarity

Five sequenced steps with an explicit PMF-state decision table as a checkpoint, an RoE 'HARD STOP' gate before the destructive broadcast/DoS actions, a single→burst escalation feedback loop, and a ZFP verification checklist; validation is present so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

Well-organized into clear sections (Prerequisites, Steps 1-5, Evidence, ZFP, OPSEC, References) with one-level-deep, clearly signaled cross-skill references and no nested references; no bundle files exist, and most content is appropriately inline, though some material (e.g., the scapy action-frame attack or mdk4 floods) could optionally be split out.

4 / 5

Total

18

/

20

Passed

Description

66%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 a distinct 802.11 deauth/PMF niche with good trigger-term coverage, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding concrete trigger phrasing would raise the score.

Suggestions

Append an explicit 'Use when...' clause with concrete triggers, e.g., 'Use when deauthenticating clients, detecting 802.11w/PMF posture, or when wpa2-psk/wpa3-sae/evil-twin need a reconnect coercion primitive.'

Add common synonyms to the description itself (e.g., 'MFP', 'management frame protection', 'deauth') alongside 'deauthentication' and 'PMF' to improve trigger-term coverage.

Optionally name the mdk4 flood variants (beacon/auth flood) in the description to close the minor specificity gap.

DimensionReasoningScore

Specificity

Lists several concrete action groups ('Targeted and broadcast 802.11 deauthentication / disassociation', '802.11w/PMF posture detection', 'action-frame attack variants'), which is comprehensive for the niche; minor gaps such as not naming the mdk4 flood variants keep it just below a 5.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or explicit trigger guidance; the 'Reusable by wpa2-psk / wpa3-sae / evil-twin' phrasing only weakly implies when, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the natural domain terms a user would say ('deauthentication', 'disassociation', '802.11w', 'PMF'), but is missing a few common synonyms (e.g., 'MFP', 'management frame protection') that appear in the metadata rather than the description.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (802.11 deauth / PMF posture) with minimal conflict risk, but the explicit 'Reusable by wpa2-psk / wpa3-sae / evil-twin' framing signals intentional overlap with those closely related sibling skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

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.