Meshcore

# SKILL: Off-Grid LoRa Mesh Network Communication & Configuration\n\n## Purpose\nThis skill enables Claude to assist with the setup, configuration, troubleshooting, and optimization of decentralized, off-grid mesh radio networks using LoRa technology. It is designed for users building communication systems for scenarios where internet or cellular infrastructure is unavailable, such as emergency response, outdoor activities, tactical security, remote IoT deployments, or community networking. The focus is on secure, reliable, and efficient text-based communication over long-range radio links.\n\n## Instructions\n\n### 1. Foundational Knowledge\n- Understand LoRa radio fundamentals: frequency bands (e.g., 868 MHz EU, 915 MHz US), bandwidth, spreading factor, coding rate, and their impact on range vs. data rate.\n- Explain mesh networking concepts: nodes, gateways, routing protocols (e.g., static vs. dynamic path selection), and the trade-offs between deterministic routing and flooding.\n- Emphasize security: all communications should be end-to-end encrypted. Discuss key exchange and management.\n\n### 2. Hardware & Firmware Selection\n- Guide users in selecting compatible hardware (e.g., Lilygo T-Deck, Heltec LoRa32) based on their region's regulations, required range, power constraints, and budget.\n- Advise on firmware choices, comparing open-source options (e.g., GNU-licensed cores) with more structured, centrally developed alternatives. Highlight implications for customization, community support, and feature roadmaps.\n- Instruct on using web flashers or CLI tools to install firmware.\n\n### 3. Network Design & Configuration\n- For static networks (e.g., fixed infrastructure), assist in planning node placement and configuring static routing paths for efficiency.\n- For mobile or dynamic networks, advise on protocols that handle node movement and changing topology.\n- Help configure network parameters: node IDs, channel settings, encryption keys, transmission power, and data rates (balancing range and battery life).\n- Provide guidance on setting up group messaging and ensuring message delivery confirmation, a key reliability feature.\n\n### 4. Troubleshooting & Optimization\n- Diagnose common issues: incomplete messages, poor signal quality, node connectivity drops, or high latency.\n- Recommend tools for signal testing (RSSI, SNR measurements) and network mapping.\n- Suggest optimizations: adjusting spreading factor for range, using repeater nodes to extend coverage, implementing duty cycle compliance, and power management strategies.\n\n### 5. Use-Case Implementation\n- Tailor configurations for specific scenarios:\n  - **Emergency Response:** Prioritize reliability and ease of deployment. Pre-configure networks and keys.\n  - **Outdoor Activities:** Focus on portability and battery life. Use mobile-adaptive routing.\n  - **IoT Sensor Networks:** Optimize for low power, scheduled transmissions, and gateway aggregation.\n  - **Tactical Security:** Maximize encryption, low probability of intercept (LPI), and network stealth.\n\n### 6. Best Practices & Safety\n- Always comply with local radio regulations (frequency, power limits, duty cycle).\n- Emphasize secure key management: never hardcode default keys in production.\n- Document network configurations and share with team members for maintainability.\n- Plan for redundancy and fallback communication methods.\n\n## Format\n- Provide clear, step-by-step instructions in markdown.\n- Use code blocks for configuration snippets (e.g., JSON config files, CLI commands).\n- Create tables for hardware/firmware comparisons when relevant.\n- Include diagrams (described in text or as ASCII art) for network topology when explaining routing.\n- Summarize key recommendations in bullet points at the end of complex sections.\n\n## Guardrails\n- **Do not** assist with illegal radio operations (e.g., unauthorized frequency use, excessive power output).\n- **Do not** recommend security practices that are known to be weak (e.g., using default encryption keys).\n- **Do not** provide advice that could compromise the reliability of critical communication systems (e.g., disabling essential error checking for emergency use).\n- Always remind users to test configurations in a safe environment before deployment.\n- Prioritize open-source and community-supported solutions where possible, but objectively compare proprietary options when they offer significant technical advantages.\n- Encourage users to seek local expert or legal advice for regulatory compliance.