Meshtastic E2E
Closed-loop end-to-end testing of a Meshtastic device and a Meshtastic app (Android, Apple, or the Compose desktop app) together. Use when validating that an action on the radio (send a text, change config, a node beacon, a power-cycle) surfaces correctly in the app UI, or that an action in the app produces the correct on-air/on-device result. Drives the firmware device via the Meshtastic MCP server and the app via the Android CLI (`android` + `adb`), the Apple toolchain (`xcrun simctl` + `idb`), or the Compose Hot Reload MCP server for desktop, then cross-asserts one plane against the other.
Install
npx skills add meshtastic/meshtastic-mcp --skill meshtastic-e2egit clone --depth 1 https://github.com/meshtastic/meshtastic-mcp.git /tmp/meshtastic-mcp
mkdir -p ~/.claude/skills
cp -r /tmp/meshtastic-mcp/src/meshtastic_mcp/skills/meshtastic-e2e ~/.claude/skills/meshtastic-e2ePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Meshtastic Device ↔ App E2E Testing Two independent planes, each with its own **stimulus** and **oracle**. A closed-loop test stimulates one plane and asserts on the *other*. | Plane | Stimulus | Oracle (observation) | |---|---|---| | **Device** (Meshtastic MCP) | `send_text`, `set_config`, `push_fake_nodedb`, `send_input_event`, `uhubctl_cycle`, traceroute | recorder `packets_window` / `telemetry_timeline` / `logs_window` / `events_window`, `device_info`, `list_nodes`, serial logs, `capture_screen`+OCR | | **App — Android** (android CLI + adb) | `adb shell input tap/text/swipe`, `android run` | `android layout --diff`, `android screen capture [--annotate]` | | **App — Android, agent-driven** (Artemis MCP) | `mobile_run_task` runs a whole journey out of context | **none — never its own oracle**; the device plane decides (see `references/journeys.md`) | | **App — Apple** (xcrun simctl + idb) | `idb ui tap/text`, `simctl install/launch` | `idb ui describe-all`, `simctl io screenshot` | | **App — Desktop** (Compose Hot Reload MCP) | `click` / `type_text` / `scroll` (by `nodeId`) | `get_semantic_tree`, `get_logs`, `get_ui_error` | ## Reference files (load the one you need) - `references/topology.md` — two-radio wiring, app-over-TCP, the uhubctl USB switch, preflight. - `references/harness.md` — the hard rules (marker tokens, bounded polling, recorder oracle, adb nav primitives, verdict format). **Read this before any loop.**
Details
- Skill name
meshtastic-e2e- Repository
- meshtastic/meshtastic-mcp
- Path
src/meshtastic_mcp/skills/meshtastic-e2e/SKILL.md- License
- GPL-3.0
- Repo updated
- 18 November 2026
FAQ
What does the Meshtastic E2E skill do?
Closed-loop end-to-end testing of a Meshtastic device and a Meshtastic app (Android, Apple, or the Compose desktop app) together. Use when validating that an action on the radio (send a text, change config, a node beacon, a power-cycle) surfaces correctly in the app UI, or that an action in the app produces the correct on-air/on-device result. Drives the firmware device via the Meshtastic MCP server and the app via the Android CLI (`android` + `adb`), the Apple toolchain (`xcrun simctl` + `idb`), or the Compose Hot Reload MCP server for desktop, then cross-asserts one plane against the other.
How do I install the Meshtastic E2E skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add meshtastic/meshtastic-mcp --skill meshtastic-e2e. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Meshtastic E2E popular?
It lives in meshtastic/meshtastic-mcp, which has 23 GitHub stars and 9 forks.
Related skills
Meshtastic Device Ops
23meshtastic/meshtastic-mcp
Discover, connect to, drive, configure, observe, and flash Meshtastic devices through the Meshtastic MCP server. Use when an agent needs to bring up a radio (serial or TCP), read or change device/channel config, send messages, inspect the node DB, watch live packets/telemetry/logs via the recorder, recover a bricked device, or build/flash firmware. Covers the non-e2e MCP tool surface; for cross-plane device↔app testing use the `meshtastic-e2e` skill.
Meshtastic Org Knowledge
23meshtastic/meshtastic-mcp
Find and answer questions across all Meshtastic GitHub repos — what projects exist, what their docs say, their current status (releases, open PRs/issues, recent commits), and how they relate. Use when a question spans more than one repo, or asks "which project does X", "what's the status of Y", "where is Z documented", or "what changed recently across the org".
Trellis Delivery Controller Zh
44coldwateryi/trellis-skills
Trellis 需求交付总入口和流程控制器。用于用户希望只调用一个 Trellis skill 自动判断当前阶段,并在需求分析、MVP 任务规划、MVP 后差距审计、交付 loop、TDD 实现、系统调试、双阶段评审和最终验收之间进行路由、推进和安全门控制的场景。适合基于 trellis-zero-to-mvp-zh、trellis-mvp-to-delivery-zh、trellis-implement-tdd-zh、trellis-debug-systematic-zh 和 trellis-review-twostage-zh 形成端到端交付闭环。
Trellis Implement TDD
44coldwateryi/trellis-skills
Implement a Trellis subtask using strict TDD (RED→GREEN→REFACTOR), turning acceptance criteria into code one by one. Used when Codex / Claude Code drives a small-parameter model like qwen3.6 35b—transforms "understand and implement requirements" into a mechanical "make this failing test green" loop with objective signals at every step.
Macos Test Triage
49robinebers/skills
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
Trellis Implement TDD Zh
44coldwateryi/trellis-skills
在 Trellis 子任务进入实现阶段时,用严格 TDD(红→绿→重构)逐条把验收标准落成代码。用于 Codex / Claude Code 等在 trellis-zero-to-mvp-zh 或 trellis-mvp-to-delivery-zh 生成主子任务后,按依赖顺序实现某个子任务,尤其当执行模型是 qwen3.6 35b 这类小参数本地模型时——把"理解并实现需求"转成"让这条失败测试变绿"的机械循环,每步都有客观信号。
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.