offensive-bluetooth-ble

Bluetooth Low Energy (BLE) attack methodology — GATT enumeration, characteristic read/write without auth, pairing downgrade (Just Works forced), LE Secure Connections bypass, MITM via active relay, sniffing with Sniffle (TI CC1352) / Ubertooth / Frontline, encryption key extraction (LE Legacy Pairing crackable, LE Secure Connections strong), proximity authentication abuse (cars, locks), and companion-app trust analysis. Use for IoT BLE devices, smart locks, fitness trackers, medical devices, BLE beacons, or any device pairing over BLE.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

76%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 highly actionable, command-rich offensive BLE reference with strong tool coverage and a clear engagement cheatsheet. Its main weaknesses are missing validation checkpoints for destructive operations and some over-explanatory framing prose.

Suggestions

Add explicit validation/verification checkpoints to the engagement workflow (e.g., confirm pairing method before sniffing, verify a write took effect before escalating) to lift workflow_clarity above the destructive-ops cap of 3.

Trim introductory explanations of concepts Claude already knows (e.g., what GATT is, what 16- vs 128-bit UUIDs imply) to improve token efficiency.

Consider offloading the per-device-class sections (smart locks, cars, medical, beacons) into a references/ file linked from the main body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven, but brief framing prose ("BLE devices communicate via GATT — a hierarchy of services...", "Custom 128-bit UUIDs are where vendor-specific commands live — that's your attack surface") explains concepts Claude already knows and could be trimmed.	4 / 5
Actionability	Copy-paste-ready commands across bettercap, bluetoothctl, gatttool, Sniffle, Ubertooth, crackle, and jadx, plus a pairing-method-to-attack mapping table — concrete guidance covering the common cases.	5 / 5
Workflow Clarity	A Quick Workflow (5 steps) and a numbered Engagement Cheatsheet (6 steps) provide a clear sequence, but there are no validation/verification checkpoints for destructive or irreversible operations (unlocking, char writes), which caps this dimension per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clear sections with external reference links, but as a single ~170-line SKILL.md with no bundle files, content such as the per-device-class guidance could be split out; structure is good with minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

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

An exceptionally specific, trigger-rich description that clearly states both the attack capabilities and the device classes that should activate the skill. It uses third-person imperative voice throughout with no over-claims or fluff.

Dimension	Reasoning	Score
Specificity	Lists many concrete attack actions — "GATT enumeration", "characteristic read/write without auth", "pairing downgrade (Just Works forced)", "LE Secure Connections bypass", "MITM via active relay", "sniffing with Sniffle / Ubertooth / Frontline", "encryption key extraction", "proximity authentication abuse", "companion-app trust analysis" — comprehensive and specific.	5 / 5
Completeness	Explicitly answers both what (detailed BLE attack methodology) and when ("Use for IoT BLE devices, smart locks, fitness trackers, medical devices, BLE beacons, or any device pairing over BLE").	5 / 5
Trigger Term Quality	The "Use for IoT BLE devices, smart locks, fitness trackers, medical devices, BLE beacons, or any device pairing over BLE" clause covers natural terms users would actually say, including device-class synonyms.	5 / 5
Distinctiveness Conflict Risk	Clearly niched to BLE offensive methodology with distinct triggers; minimal overlap risk with adjacent skills like offensive-mobile or offensive-iot.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: SnailSploit/Claude-Red
Path: Skills/wireless/offensive-bluetooth-ble/SKILL.md
Commit: 24d7968

Reviewed: ~5 hours ago

Table of Contents

Discovery Implementation Validation

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.