offensive-tools/wireless/bluez/SKILL.md
BlueZ Bluetooth stack and CLI workflow for Linux, covering bluetoothctl-driven discovery, pairing, BLE inspection, and low-level troubleshooting utilities. Use when scanning Bluetooth Classic or BLE devices, validating adapter state, enumerating services/characteristics, or building Bluetooth reconnaissance workflows on Linux.
npx skillsauth add aeondave/malskill bluezInstall 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.
Linux Bluetooth stack and operator toolkit for Bluetooth Classic and BLE discovery, connection, and debugging.
Use BlueZ as the baseline Bluetooth skill when you need:
# verify controller state
bluetoothctl list
bluetoothctl show
# interactive discovery
bluetoothctl
[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# default-agent
[bluetooth]# scan on
bluetoothctl scan on
bluetoothctl
[bluetooth]# pair AA:BB:CC:DD:EE:FF
[bluetooth]# trust AA:BB:CC:DD:EE:FF
[bluetooth]# connect AA:BB:CC:DD:EE:FF
btmon
Use btmon when pairing, advertising visibility, or GATT behavior is unclear.
BlueZ is the foundation. Prefer it before niche scanners because:
Older tooling such as gatttool or some deprecated tools may still appear in guides, but modern workflows should prefer current BlueZ client tooling where possible.
| Skill | Best use |
|---|---|
| bluez | Core Linux Bluetooth discovery, pairing, monitoring |
| kismet | Passive multi-RF visibility including Bluetooth with supported hardware |
| sparrow-wifi | GUI/agent Bluetooth awareness plus Wi‑Fi/HackRF/Ubertooth workflows |
| File | When to load |
|---|---|
| references/scan-read-debug-workflow.md | For bluetoothctl, BLE scanning, service inspection, and monitor-first debugging workflows |
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.