Run any Skill in Manus with one click

meshsa-add-transport

Stars1

Forks0

UpdatedJune 20, 2026 at 23:00

Use when: adding a meshsa transport, radio driver, Meshtastic path, TAK transport, HaLow/IP link, reconnect logic, transport registry entry, or Transport Protocol implementation.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ianshank

ianshank/GCP-Drone-Comms-Unit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	meshsa-add-transport
description	Use when: adding a meshsa transport, radio driver, Meshtastic path, TAK transport, HaLow/IP link, reconnect logic, transport registry entry, or Transport Protocol implementation.
argument-hint	Transport name, medium, config fields, and expected send/receive behavior

Add a MeshSA Transport

When to Use

Add a new radio, serial, TCP, UDP, HaLow, LoRa, TAK, or IP transport.
Change send/receive behavior, reconnect supervision, or transport config.
Register a new TransportConfig.type value.

Procedure

Read ../../../AGENTS.md and ../../../packages/meshsa/AGENTS.md.
Add implementation under packages/meshsa/src/meshsa/transports/.
Prefer subclassing AbstractTransport when an async inbox and stream() are enough; otherwise implement the Transport Protocol exactly.
Register the factory with @transport_registry.register("name") and accept name, queue_maxsize, and **options where appropriate.
Keep operational values configurable through TransportConfig.options and Pydantic config. Do not hide ports, intervals, or backoff values in the router.
Write tests with injected fakes: fake connectors, fake pubsub, LoopbackBus, FakeClock, and SeqIdFactory. Do not require real hardware in unit tests.
Update packages/meshsa/README.md and docs/ARCHITECTURE.md if the new transport changes user-facing setup or the module map.
Verify with python -m pytest, mypy src, ruff check ., and ruff format --check . from packages/meshsa.

References

packages/meshsa/src/meshsa/protocols.py
packages/meshsa/src/meshsa/transports/base.py
packages/meshsa/src/meshsa/transports/loopback.py
packages/meshsa/src/meshsa/transports/tak.py
packages/meshsa/src/meshsa/transports/meshtastic_radio.py
packages/meshsa/tests/test_transports.py
packages/meshsa/tests/test_meshtastic.py
packages/meshsa/tests/test_tak.py

More from this repository

same repository

jetson-perception

ianshank/GCP-Drone-Comms-Unit

Use when: working in packages/jetson_yolo_gcs — adding a detector backend (YOLO/Hailo/ONNX/TensorRT), a tracker backend (Norfair/SORT), GStreamer camera/egress pipeline, the MAVLink LANDING_TARGET bridge, precision-landing safety, or the perception pipeline failure policy.

2026-07-161

pre-pr-validator

ianshank/GCP-Drone-Comms-Unit

Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing.

2026-07-161

meshsa-inference

ianshank/GCP-Drone-Comms-Unit

Use when: working on the optional NVIDIA Nemotron inference bridge — meshsa.inference, NemotronClient/InferenceService/NemotronConfig, MESHSA_INFERENCE_* env vars, aiohttp session reuse, [AI Insight] feedback-loop filter, or the aioresponses test mocks.

2026-07-081

meshsa-observability

ianshank/GCP-Drone-Comms-Unit

Use when: adding or changing metrics/health export — RouterMetrics, render_prometheus, per-transport counters, the /metrics or /healthz route, HealthConfig fields, or a Grafana golden-signal dashboard.

2026-07-081

meshsa-commanding-safety

ianshank/GCP-Drone-Comms-Unit

Use when: touching the supervised two-way command path (Initiative C) — meshsa.command.*, flightctl/run_commander.py, arm/disarm/RTL/set_mode, COMMAND_INT/ACK, force-disarm, operator confirmation, command audit log, or arm preconditions.

2026-06-301

spec-driven-change

ianshank/GCP-Drone-Comms-Unit

Use when: starting a roadmap/initiative feature, new milestone work, a transport/codec/backend that adds behavior, or any change big enough to need a design. Author or update a spec under docs/specs first; code cites the spec by section.

2026-06-301

name	meshsa-add-transport
description	Use when: adding a meshsa transport, radio driver, Meshtastic path, TAK transport, HaLow/IP link, reconnect logic, transport registry entry, or Transport Protocol implementation.
argument-hint	Transport name, medium, config fields, and expected send/receive behavior

Add a MeshSA Transport

When to Use

Add a new radio, serial, TCP, UDP, HaLow, LoRa, TAK, or IP transport.
Change send/receive behavior, reconnect supervision, or transport config.
Register a new TransportConfig.type value.

Procedure

Read ../../../AGENTS.md and ../../../packages/meshsa/AGENTS.md.
Add implementation under packages/meshsa/src/meshsa/transports/.
Prefer subclassing AbstractTransport when an async inbox and stream() are enough; otherwise implement the Transport Protocol exactly.
Register the factory with @transport_registry.register("name") and accept name, queue_maxsize, and **options where appropriate.
Keep operational values configurable through TransportConfig.options and Pydantic config. Do not hide ports, intervals, or backoff values in the router.
Write tests with injected fakes: fake connectors, fake pubsub, LoopbackBus, FakeClock, and SeqIdFactory. Do not require real hardware in unit tests.
Update packages/meshsa/README.md and docs/ARCHITECTURE.md if the new transport changes user-facing setup or the module map.
Verify with python -m pytest, mypy src, ruff check ., and ruff format --check . from packages/meshsa.

References

packages/meshsa/src/meshsa/protocols.py
packages/meshsa/src/meshsa/transports/base.py
packages/meshsa/src/meshsa/transports/loopback.py
packages/meshsa/src/meshsa/transports/tak.py
packages/meshsa/src/meshsa/transports/meshtastic_radio.py
packages/meshsa/tests/test_transports.py
packages/meshsa/tests/test_meshtastic.py
packages/meshsa/tests/test_tak.py