CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wps-pixie-dust

WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.

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

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

An actionable, well-gated offensive-security runbook: concrete executable commands for every phase, an explicit RoE checkpoint before the loud fallback, and compact non-obvious domain detail (chipset vulnerabilities, lockout behavior). Minor room to trim the PIN-math explanation and to show failure-mode output alongside the success example.

Suggestions

Show what failed Pixie-Dust output looks like (e.g., reaver hanging on M5/M6 or random nonces in -vv output) so the fallback trigger in Step 3 is a concrete signal, not a judgment call.

Trim the PIN-space arithmetic ('10^8 but the last digit is a checksum... Total: ~11,000 attempts') to one line — Claude already knows the WPS PIN split.

Add a brief verification step after PSK recovery (e.g., confirm with wpa_supplicant or a controlled client association) so the workflow closes with an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is lean: flags are annotated as inline comments, the chipset table is compact, and the genuinely non-obvious domain knowledge (vulnerable chipsets, years, lockout behavior) earns its tokens. The PIN-space math paragraph (10^8, checksum digit, ~11,000 attempts) explains something Claude already knows, making this anchor 4 ('minor instances of over-explanation') rather than 5, and well above anchor 3.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — 'sudo wash -i <mon-iface> --ignore-fcs', 'sudo reaver -i <mon-iface> -b <BSSID> -c <CHANNEL> -K 1 -vv -N', 'sudo bully <mon-iface> -b <BSSID> -c <CHANNEL> -d -v 3', plus '-p <known_PIN>' re-extraction — with every flag explained inline and expected success output shown ('[+] WPS PIN: ... [+] WPA PSK: ...'). Common cases (scan, primary attack, fallback, known-PIN recovery) are all covered — anchor 5.

5 / 5

Workflow Clarity

A clear four-step sequence with an explicit HARD STOP gate before the destructive/loud online brute, lockout handling via '--lock-delay=60', and a defined fallback branch ('If Pixie-Dust fails (nonces are random), fall back'). It falls short of anchor 5 because the pixie-dust failure-mode output is not shown (only success output), and there is no step verifying the recovered PSK actually authenticates; it is clearly above anchor 3 since gating and error-recovery checkpoints are present.

4 / 5

Progressive Disclosure

A single self-contained SKILL.md with well-organized, clearly headed sections and easy navigation; no bundle files exist, so nothing is buried or nested. Anchor 4 rather than 5 because the chipset vulnerability table and external reference links could live in a separate reference file, and standalone pixiewps usage (shown in ZFP as 'pixiewps -e <ES1> -r <ES2> ...') is not surfaced as its own step or pointer.

4 / 5

Total

17

/

20

Passed

Description

75%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 strong, highly specific description with excellent distinctiveness and good trigger terms, but it omits an explicit 'Use when...' trigger clause, which caps its completeness. Trigger guidance exists only in the separate metadata.when_to_use field, not in the description itself.

Suggestions

Append an explicit trigger clause to the description, e.g., 'Use when WPS is enabled on a target AP, the user mentions Pixie Dust, reaver, bully, wash, WPS PIN attacks, or when handshake capture has failed.'

Add one or two natural user phrasings to the description such as 'WPS locked' or 'crack the WiFi password' to broaden trigger coverage beyond tool names.

Keep the 'without capturing a handshake' differentiator — it effectively prevents mis-triggering against the wpa2-psk handshake-capture skill.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions with tool names and flags — 'offline nonce attack (reaver -K / pixiewps)', 'fallback online PIN brute (bully)', 'recover the AP's WPA PSK' — with comprehensive coverage of what the skill does. Anchor 5 fits better than 4 because there are no meaningful gaps in the stated capabilities.

5 / 5

Completeness

The 'what' is clearly and concretely answered, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is fully clear; it cannot be 4 because the 'when' is absent rather than merely implicit or less specific.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'WPS Pixie-Dust', 'reaver', 'pixiewps', 'bully', 'WPA PSK', 'handshake'. A few natural terms users might say are missing (e.g., 'WPS locked', 'wash', 'crack WiFi password'), which places it at anchor 4 rather than 5, and clearly above anchor 3 since coverage is broad rather than partial.

4 / 5

Distinctiveness Conflict Risk

A clear niche (WPS Pixie-Dust) with distinct tool triggers, and 'without capturing a handshake' explicitly distinguishes it from the adjacent handshake-capture/WPA-cracking skill. Minimal conflict risk — anchor 5.

5 / 5

Total

17

/

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/wps-pixie-dust/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.