Tencent SkillHub · Communication & Collaboration

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.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

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.

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: CONFIG.md, README.md, SKILL.md, references/SETUP.md, references/claude_desktop_config.json, scripts/mcp_server.py

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 0.1.0

Provenance

Publisher: lukevr
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 19 sections Open source page

Meshtastic Skill

Control a Meshtastic node via USB for off-grid LoRa mesh communication.

Prerequisites

Meshtastic-compatible hardware (RAK4631, T-Beam, Heltec, LilyGo, etc.) USB connection to host machine Python 3.9+ with meshtastic and paho-mqtt packages See references/SETUP.md for full installation guide

Configuration

Edit CONFIG.md with your node details, MQTT settings, and alert destinations.

Architecture

┌─────────────────────────────────────────────────────────────┐ │ MQTT Bridge │ ├─────────────────────────────────────────────────────────────┤ │ RECEIVE: mqtt.meshtastic.org (global JSON traffic) │ │ PUBLISH: optional map broker (protobuf) │ │ SOCKET: localhost:7331 (commands: send, status, toggle) │ ├─────────────────────────────────────────────────────────────┤ │ Files: │ │ • /tmp/mesh_messages.txt - received messages log │ │ • /tmp/mesh_nodes.json - cached node positions │ └─────────────────────────────────────────────────────────────┘ ┌─────────────┐ USB ┌─────────────┐ │ LoRa Node │◄────────────►│ Bridge.py │ │ (Radio) │ │ - Serial │ └─────────────┘ │ - Socket │ │ - MQTT │ └──────┬──────┘ │ ┌────────────────────────┼────────────────────────┐ │ │ │ ▼ ▼ ▼ localhost:7331 /tmp/mesh_* MQTT Broker (send commands) (message logs) (mesh traffic)

Send Messages

# Via socket (preferred - works while bridge running) echo '{"cmd":"send","text":"Hello mesh!"}' | nc -w 2 127.0.0.1 7331 # Direct message to specific node echo '{"cmd":"send","text":"Hey!","to":"!abcd1234"}' | nc -w 2 127.0.0.1 7331 # Check status echo '{"cmd":"status"}' | nc -w 2 127.0.0.1 7331 # List RF nodes (seen via radio) echo '{"cmd":"nodes"}' | nc -w 2 127.0.0.1 7331

Map Visibility (if configured)

# Toggle map publishing on/off echo '{"cmd":"map"}' | nc -w 2 127.0.0.1 7331 # Explicitly enable/disable echo '{"cmd":"map","enable":true}' | nc -w 2 127.0.0.1 7331 echo '{"cmd":"map","enable":false}' | nc -w 2 127.0.0.1 7331 # Force immediate position report echo '{"cmd":"map_now"}' | nc -w 2 127.0.0.1 7331

Read Messages

# Recent messages (last 20) tail -20 /tmp/mesh_messages.txt # Filter common noise tail -50 /tmp/mesh_messages.txt | grep -v -E "(Hello!|hey|mqtt-test)"

Message Log Format

Bridge Service

# Status sudo systemctl status meshtastic-bridge # Restart sudo systemctl restart meshtastic-bridge # View logs sudo journalctl -u meshtastic-bridge -f # Stop (needed for direct CLI access) sudo systemctl stop meshtastic-bridge

Option 1: Cron Job (Recommended)

cron.add({ name: "mesh-monitor", schedule: { kind: "every", everyMs: 300000 }, // 5 min sessionTarget: "isolated", payload: { kind: "agentTurn", message: "Check /tmp/mesh_messages.txt for new messages. Filter out noise (test messages, 'Hello!', 'hey'). Alert me of interesting ones with translations if non-English.", timeoutSeconds: 60, deliver: true, channel: "telegram" // or your channel } })

Option 2: Digest Summary

cron.add({ name: "mesh-digest", schedule: { kind: "cron", expr: "0 8,14,20 * * *", tz: "Europe/Madrid" }, sessionTarget: "isolated", payload: { kind: "agentTurn", message: "Read /tmp/mesh_messages.txt. Create a digest of interesting messages from the last 6 hours. Translate non-English, guess country from distance. Post summary.", timeoutSeconds: 120, deliver: true, channel: "telegram" } })

Option 3: Spawned Monitor Agent

sessions_spawn({ task: "Monitor /tmp/mesh_messages.txt every 30 seconds. Alert me for interesting messages (not noise). Run for 1 hour.", label: "mesh-monitor", runTimeoutSeconds: 3600 })

Distance Reference

Approximate distances for country guessing (adjust for your location): DistanceTypical Regions<500kmNeighboring countries/regions500-1000kmMedium range1000-1500kmLong range1500-2000kmVery long range (likely MQTT relay)>2000kmMQTT-bridged traffic

Privacy Notes

Map reports can use fuzzy positioning (~2km precision) Position publishing can be toggled off entirely Local RF messages are logged but not shared externally by default Never broadcast precise location in messages

Supported Hardware

DeviceNotesRAK4631Recommended, reliable USBT-BeamPopular, has GPSHeltec V3Budget optionLilyGo T-EchoE-paper display See references/SETUP.md for hardware-specific setup.

Regional Frequencies

RegionFrequencyTopic RootEurope868 MHzmsh/EU_868/2/jsonAmericas915 MHzmsh/US/2/jsonAustralia/NZ915 MHzmsh/ANZ/2/json

Files

~/.openclaw/skills/meshtastic/ ├── SKILL.md # This file ├── CONFIG.md # Your configuration ├── scripts/ │ └── mesh.py # CLI wrapper └── references/ └── SETUP.md # Installation guide

Troubleshooting

"Resource temporarily unavailable" Only one process can use serial port at a time Stop bridge before direct CLI: sudo systemctl stop meshtastic-bridge No messages appearing Check MQTT subscription topic matches your region Verify firewall allows outbound port 1883 Check journalctl -u meshtastic-bridge for errors Can't send messages Ensure bridge is running (socket server) Check serial port path in config Try: echo '{"cmd":"status"}' | nc -w 2 127.0.0.1 7331 Considering BLE instead of USB? Don't. USB is far more reliable on Linux. BLE on Linux (BlueZ/bleak) has notification bugs, pairing inconsistencies, and random disconnects. See references/SETUP.md for detailed findings.

Package contents

Included in package

4 Docs1 Scripts1 Config

SKILL.md Primary doc
CONFIG.md Docs
README.md Docs
references/SETUP.md Docs
scripts/mcp_server.py Scripts
references/claude_desktop_config.json Config