offensive-tools/wireless/lswifi/SKILL.md
CLI-centric Windows Wi‑Fi scanning tool exposing richer nearby-network data than built-in commands, including RSSI, security details, information elements, 6 GHz Reduced Neighbor Reports, JSON/CSV export, and event watching. Use when auditing nearby Wi‑Fi networks from Windows, exporting scan data, or scripting Windows-native wireless analysis without monitor-mode tooling.
npx skillsauth add aeondave/malskill lswifiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Windows-native CLI Wi‑Fi scanner for richer AP visibility, filtering, export, and event watching.
Use lswifi when you need:
netsh wlan show networkspython -m pip install lswifi
# basic scan
lswifi
# stronger-signal networks only
lswifi -t -60
# only matching SSIDs
lswifi -include Office
# JSON export-friendly output
lswifi --json
# Information elements for a specific BSSID
lswifi -ies 00:11:22:33:44:55
# Watch roaming / scan / connection events
lswifi --watchevents
# 6 GHz / RNR oriented view
lswifi -rnr
# export scan results
lswifi -export
lswifi is not traditional over-the-air monitor-mode packet capture. It uses Windows Native Wi‑Fi APIs, so treat it as a Windows-native survey/inspection tool, not as a full packet injection platform.
| Skill | Best use |
|---|---|
| lswifi | Windows-centric scan, export, filtering, event watching |
| kismet | Passive multi-sensor / multi-protocol RF visibility |
| aircrack-ng | Linux monitor-mode audit and capture workflows |
| File | When to load |
|---|---|
| references/filtering-export-workflows.md | For practical filters, exports, watch mode, and Windows-specific caveats |
data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
tools
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.