OpenParable
Skip to content
← Back to skills

Simpleaible

Apps & Automation
simpleaible

Simpleaible is an Agent Skill for apps & automation published in the simpleble/simpleble repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use the SimpleAIBLE MCP server to scan, connect, and interact with Bluetooth devices. This skill provides guidance on the recommended flow (scan -> connect -> services -> read/notify) and handles platform-specific differences like UUIDs on macOS vs MAC addresses on Linux. Use when the user wants to interact with BLE hardware or debug Bluetooth connections.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/simpleble/simpleble/blob/HEAD/simpleaible/src/simpleaible/skills/simpleaible/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/simpleaible, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

SimpleAIBLE

SimpleAIBLE is an AI-friendly BLE toolkit powered by SimpleBLE. This skill provides instructions for using the SimpleAIBLE MCP server to interact with Bluetooth Low Energy (BLE) devices directly from the host machine.

Quick Start Flow

Always follow this sequence for BLE interactions:

  1. Scanning: Call scan_for (default 5s) to find nearby peripherals.
  2. Connection: Call connect using the address from the scan results.
  3. Exploration: Call services to list available GATT services and characteristics.
  4. Interaction: Use read for one-time values, write_request/write_command to send data, or notify/indicate + get_notifications + unsubscribe for streaming data.
  5. Cleanup: Always call disconnect when finished to release the device.

Core Instructions

  • Scanning: Prefer scanning immediately before connecting to ensure the device is in the internal cache.
  • Addressing: Be aware that macOS/iOS uses UUIDs for addresses, while Linux/Windows uses MAC addresses.
  • Data Handling: Binary data is returned as data_hex (always reliable) and data_utf8 (convenience field). If the data is not valid UTF-8, invalid bytes are skipped, so data_utf8 may be incomplete or empty. Use data_hex for protocol analysis and data_utf8 for human-readable strings.
  • Notifications/Indications: Use notify or indicate to subscribe, get_notifications to retrieve buffered data, and unsubscribe when done.
  • Bluetooth Status: Assume Bluetooth is enabled by default. Only check bluetooth_enabled when an operation fails.

Additional Resources