Off-grid radio for sovereign AI. LoRa mesh comms via Meshtastic — no internet required.

Send and receive messages via Meshtastic LoRa mesh network. Use for off-grid messaging, mesh network status, reading recent mesh messages, or sending texts via LoRa radio.

This package appears to implement the Meshtastic bridge you expect, but review a few items before installing: - CONFIG.md contains default MQTT credentials and broker settings — verify and replace them with your own values or set map publishing off if you don't want to relay to public brokers. Treat those as configuration, not secrets provided by the skill. - The skill logs inbound mesh traffic to /tmp/mesh_messages.txt and provides mechanisms (cron, spawned agent sessions, MCP tools) to read, filter, translate, and post those messages to external channels (Telegram, Discord, etc.). If you enable automated delivery, the agent may forward radio traffic off your machine. Make sure you control destination channels and understand potential privacy/legal concerns for relaying third-party radio messages. - The SKILL.md examples for monitoring are intentionally permissive ("Alert me of interesting ones with translations") — consider tightening the rules: explicit keyword lists, stricter filters, and disable automatic 'deliver: true' until you test manually. - The package suggests installing a systemd service that will run a long-lived bridge process. Ensure the service runs as a non-privileged user and check file permissions on /tmp logs and state files so other local users cannot read them if that matters. - The MCP server exposes tools that can operate the device and read logs; only run the MCP server if you trust the local environment and any clients that will connect to it. Audit which MCP clients you register it with (e.g., Claude Desktop) to avoid unintended remote control. If you want to proceed safely: - Audit the CONFIG.md and replace any defaults. - Run the bridge in an isolated environment (dedicated user account, container, or VM) until you are comfortable. - Disable map publishing and external MQTT publish by default. - Test manual commands (mesh.py send/status/messages) before enabling cron/agent automation or MCP exposure. Confidence notes: assessment is based on included SKILL.md and Python scripts; nothing obviously malicious was found, but the skill's automation examples can cause privacy-relevant data to be forwarded if misconfigured, so treat as suspicious until you confirm configuration and intended delivery targets.

Type: OpenClaw Skill Name: meshtastic-skill Version: 0.1.0 The skill is designed for interacting with Meshtastic LoRa mesh networks, providing capabilities for sending/receiving messages, monitoring traffic, and managing the Meshtastic device. All network communication is directed to public Meshtastic MQTT brokers (mqtt.meshtastic.org, mqtt.meshtastic.es) using public credentials, which is aligned with its stated purpose. Local file access to `/tmp/mesh_messages.txt` and other `/tmp` files is for logging and state management. The `SKILL.md` instructions for the AI agent are benign, guiding it to monitor local message logs and generate alerts, without attempting prompt injection for malicious purposes. While the skill involves direct hardware interaction via serial port and systemd service management (requiring `sudo` during setup), these are necessary and explicitly documented for its legitimate functionality, with no evidence of intentional harmful behavior or unauthorized data exfiltration.