CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ble-gatt

GATT service/characteristic enumeration on BLE peripherals, unauthenticated read/write exploitation, pairing downgrade to Just Works, and over-the-air sniffing with Sniffle or Ubertooth. Covers firmware update channels, hidden debug services, and missing auth on sensitive characteristics.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/iot/ble-gatt/SKILL.md
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 well-structured, operational runbook with copy-paste-ready commands across a logical five-phase workflow and genuine attention to evidence capture and OPSEC. The main improvements are small: define or bundle dump_gatt.py, explain the kg_add_node call's provenance, and add an explicit write-verification step.

Suggestions

Add an explicit validation step after Phase 3 writes — re-read the characteristic (gatttool --char-read or client.read_gatt_char) and compare against the written payload to confirm the change took effect.

Either save the Phase 2 bleak dump as an actual scripts/dump_gatt.py bundle file or change the Evidence section to re-use the inline snippet, since "python3 dump_gatt.py" currently references a file that does not exist in the bundle.

Clarify what kg_add_node is (a project-specific helper, a script in the bundle, or pseudocode) so the Evidence section is executable as written.

DimensionReasoningScore

Conciseness

The body is dominated by lean, commented commands and code with clear section headers, but a few tokens could be trimmed: "Just Works pairing provides no MITM protection" and "gatttool is deprecated but still widely available" explain concepts Claude already knows, and gatttool enumeration is shown twice (interactive and one-liner forms). This matches anchor 4 (efficient with minor over-explanation), not anchor 5, which requires every token to earn its place.

4 / 5

Actionability

Concrete, executable guidance throughout: bleak scan/dump scripts, gatttool and bluetoothctl sequences, bettercap one-liners, Sniffle/Ubertooth capture commands, and an evidence-hashing script. It falls short of anchor 5 because "python3 dump_gatt.py" invokes a script that does not exist in the bundle (the dump code is only shown inline), and "kg_add_node(...)" is an undefined API with no file or definition backing it — minor but real gaps that would break copy-paste execution.

4 / 5

Workflow Clarity

A clear five-phase sequence (passive discovery → GATT enumeration → unauthenticated write → pairing downgrade → sniffing) with several checkpoints: read-error handling in the bleak dump, "After pairing, re-run GATT dump", sha256 evidence hashing, and gating OTA firmware writes on operator approval with a recovery plan. It is not anchor 5 because there is no explicit feedback loop verifying that a write took effect (e.g., re-reading the characteristic after writing), and per the anti-drift check the destructive OTA step's approval gate keeps it above anchor 3.

4 / 5

Progressive Disclosure

The single-file skill is well-organized with distinct phase headers, an evidence section, OPSEC notes, and a clearly labeled References section of external links — no nested or buried references. It matches anchor 4 (good structure, content mostly appropriately placed) rather than 5 only because at ~215 lines some material, such as the characteristic-UUID attack table and the kg_add_node example, could eventually justify a separate reference file as the skill grows.

4 / 5

Total

16

/

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 highly specific, well-scoped description for BLE GATT security testing that names concrete actions, tools, and target classes with minimal conflict risk. Its one substantive weakness is the absence of any 'Use when...' trigger clause, which caps completeness and leaves invocation guidance implicit in keywords alone.

Suggestions

Append an explicit trigger clause, e.g. "Use when testing BLE peripherals, auditing GATT services/characteristics, or when the user mentions Bluetooth Low Energy, Just Works pairing, Sniffle, or Ubertooth."

Spell out "Bluetooth Low Energy" at least once alongside BLE to catch users who type the full name rather than the abbreviation.

Move or mirror the strongest keywords from the metadata when_to_use field into the description itself, since the description is what gets matched for skill selection.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "GATT service/characteristic enumeration", "unauthenticated read/write exploitation", "pairing downgrade to Just Works", "over-the-air sniffing with Sniffle or Ubertooth" — plus coverage targets ("firmware update channels, hidden debug services, and missing auth"), comprehensively matching the anchor for multiple specific concrete actions. It is not a 4 because there are no meaningful gaps in coverage; every clause names an actionable capability.

5 / 5

Completeness

The "what" is explicit and comprehensive (enumeration, exploitation, downgrade, sniffing, coverage areas), but there is no "Use when..." clause or any equivalent explicit trigger guidance in the description — the 'when' is entirely absent, not merely weakly implied. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3; it is not a 2 because the 'what' is clear and detailed.

3 / 5

Trigger Term Quality

Natural terms a BLE-security user would say are present — "BLE", "GATT", "characteristic", "pairing", "Just Works", "Sniffle", "Ubertooth", "firmware update" — giving good keyword coverage. It falls short of anchor 5 because common synonyms like the spelled-out "Bluetooth Low Energy" or plain "Bluetooth" are missing, and it is clearly above anchor 3 since most natural trigger phrasing is covered.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche with distinct triggers — named tools (Sniffle, Ubertooth) and protocol-specific actions (GATT characteristic exploitation, Just Works downgrade) that virtually no other skill would claim. Minimal conflict risk, matching the anchor 5 example's structure of a distinct domain with dedicated triggers.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/iot/ble-gatt/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.