Skip to content
Back to skills

Bluetooth

ASecurity

Discover, connect, and control Bluetooth devices with automatic profile learning, cross-platform tools, and device management.

  • 17 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
toolspythonshellnodesecurity

Works with

  • cli

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add clawic/skills --skill bluetooth --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Bluetooth?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Bluetooth
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/clawic-bluetooth/badge)](https://www.skillsdirectory.com/skills/clawic-bluetooth)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Bluetooth
slug: bluetooth
version: 1.0.0
description: Discover, connect, and control Bluetooth devices with automatic profile learning, cross-platform tools, and device management.
homepage: https://clawic.com/skills/bluetooth
metadata:
  clawdbot:
    emoji: 📶
    displayName: Bluetooth
---

## Core Workflow

1. **Scan** — Discover nearby devices
2. **Identify** — Match against known profiles or learn new device
3. **Connect** — Establish link with appropriate protocol
4. **Execute** — Send commands, read data, manage state
5. **Learn** — Update device profile based on interaction success/failure

---

## Quick Reference

| Need | Load |
|------|------|
| CLI commands by platform | `tools.md` |
| Device profile management | `profiles.md` |
| Security rules and warnings | `security.md` |
| Patterns by use case | `use-cases.md` |

---

## Workspace

Store device profiles and interaction history:

```
~/Clawic/data/bluetooth/
├── profiles/         # Known device configs (one file per device)
├── history.md        # Interaction log with success/failure
└── pending.md        # Devices discovered but not profiled
```

---

## Critical Rules

1. **Never auto-connect** to unknown devices — require explicit user confirmation
2. **Whitelist first** — only interact with pre-authorized devices
3. **Log everything** — every connection attempt, command, result
4. **Fail gracefully** — if device unreachable, retry with backoff, then report
5. **Profile learning** — when something works, save it; when it fails, note why

---

## Platform Detection

| OS | Primary Tool | Fallback |
|----|--------------|----------|
| Linux | `bluetoothctl` | `hcitool`, `gatttool` |
| macOS | `blueutil` | `system_profiler`, CoreBluetooth |
| Windows | WinRT/PowerShell | `pnputil` for enumeration |
| Cross-platform | Bleak (Python) | Noble (Node.js) |

---

## Device Interaction Pattern

```
1. Check ~/Clawic/data/bluetooth/profiles/ for device
2. If known → load profile, use saved commands
3. If unknown → scan characteristics, discover capabilities
4. Execute requested action
5. Verify result (read state, check acknowledgment)
6. Update profile: what worked, what failed, timing
```

Files in this skill

  • SKILL.md2.2 KB
  • _meta.json170 B
  • profiles.md3.1 KB
  • security.md3.3 KB
  • tools.md3.1 KB
  • use-cases.md4.2 KB

Attribution

clawicView sourceSee grades on GitHubMore from clawic

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…