CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wpa-enterprise-eap

WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dense, operationally excellent attack playbook: executable commands, branching decision logic, RoE gating, and verification requirements with almost no wasted tokens. The residual gaps are unspecified supporting artifacts (sycophant config, portal page) and a fully-inline structure with no reference files.

DimensionReasoningScore

Conciseness

Terse operational comments and no concept tutorials; the opening blockquote on MSCHAPv2↔NetNTLM equivalence is engagement-critical framing, not padding. Minor trimming is possible — the comment-only bash block in Step 1 (TLS validation posture) and a few inline explanations could be tightened into prose.

4 / 5

Actionability

Copy-paste-ready commands with real flags throughout (eaphammer --auth wpa-eap --creds --negotiate gtc-downgrade; hashcat -m 5600 with the exact hash-format construction; asleap -C/-R/-W). Not fully executable end-to-end: wpa_sycophant.conf contents and the Step 5 credential-capture portal are left unspecified.

4 / 5

Workflow Clarity

A clean sequence (recon → rogue AP 2A/2B → optional deauth → crack/relay branch → hostile portal) with explicit decision points, a HARD STOP RoE gate, a pre-TX `iw reg get` regulatory check, and ZFP verification outputs. Some mid-workflow checkpoints (e.g., confirming a capture landed before choosing crack vs. relay) remain implicit, keeping it below 5.

4 / 5

Progressive Disclosure

Well-organized sections with one-level-deep references (GitHub tool repos, sibling skills) and no nested pointer chains. No bundle files exist, so all ~220 lines are inline; some material (e.g., the kg_add_node evidence schema) could be split into a reference file, which keeps this below 5.

4 / 5

Total

16

/

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.

A highly specific, trigger-rich description that clearly states what the skill does with minimal conflict risk. Its only real weakness is the missing "Use when…" trigger clause in the description itself — the trigger guidance exists only in metadata.when_to_use.

Suggestions

Append a trigger clause to the description, e.g. "Use when targeting WPA/WPA2/WPA3-Enterprise (802.1X) networks, capturing MSCHAPv2/PEAP credentials, or pivoting wireless captures into AD NetNTLM attacks."

Move or duplicate the most distinctive terms from metadata.when_to_use (e.g. "eaphammer", "hostapd-wpe", "evil twin enterprise") into the description so skill-matching on the description field alone fires reliably.

DimensionReasoningScore

Specificity

"rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay" enumerates multiple concrete operations covering the full attack surface of the niche (capture, downgrade, relay, plus the NetNTLM outcome). Coverage is comprehensive rather than merely several actions, and the voice is third-person descriptive throughout.

5 / 5

Completeness

The "what" is explicit and concrete, but the description contains no "Use when…" clause or equivalent trigger guidance — the trigger list lives in metadata.when_to_use rather than the description field, which caps completeness at 3 per the judging guidelines. The "when" is absent, not merely under-specified.

3 / 5

Trigger Term Quality

"WPA/WPA2/WPA3-Enterprise", "802.1X/EAP", "MSCHAPv2", "PEAP", "evil-twin", "rogue-RADIUS", "NetNTLM" are exactly the natural terms an operator would say when needing this skill, including protocol-version synonyms. No commonly used synonym for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

Enterprise 802.1X/EAP credential capture is a clear niche with distinct triggers (PEAP, MSCHAPv2, rogue RADIUS, GTC downgrade) that would not plausibly fire for generic wireless, Wi-Fi, or Active Directory skills.

5 / 5

Total

18

/

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.

Validation — 14 / 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

Path

packages/decepticon/decepticon/skills/standard/wireless/wpa-enterprise-eap/SKILL.md

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.