Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

ops-deploy-base-node

Estrellas1

Forks0

Actualizado20 de junio de 2026 a las 23:00

Use when: updating base node deployment, meshsa-base systemd service, Raspberry Pi 5 setup, mesh-up.sh, FreeTAKServer bridge install, env files, field runbooks, or ops scripts.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

ianshank

ianshank/GCP-Drone-Comms-Unit

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Administradores de redes y sistemas informáticosOcupaciones informáticas y matemáticas·SOC 15-1244

SKILL.md

readonly

name	ops-deploy-base-node
description	Use when: updating base node deployment, meshsa-base systemd service, Raspberry Pi 5 setup, mesh-up.sh, FreeTAKServer bridge install, env files, field runbooks, or ops scripts.
argument-hint	Target node type, deployment path, service change, and validation available

Deploy or Update a Base Node

When to Use

Change ops/base-service install docs, env examples, or systemd unit.
Change ops/pi5-node provisioning scripts or mesh setup.
Document field deployment of the Meshtastic to FreeTAKServer bridge.

Procedure

Read ../../../ops/AGENTS.md.
Keep service, install guide, and env example in sync.
Use meshsa-base as the installed entry point; do not reference deleted root scripts or old meshsa_framework paths.
Keep credentials, PSKs, host-specific callsigns, and tokens out of tracked files. Use placeholders in .env.example files.
Preserve graceful shutdown (KillSignal=SIGINT) for the asyncio bridge.
For Pi scripts, prefer idempotent setup steps and explicit package names.
Update root README deployment links if paths change.
State whether validation was docs-only, syntax-only, or hardware-tested.

References

ops/base-service/INSTALL_base_node.md
ops/base-service/base.env.example
ops/base-service/meshsa-base.service
ops/pi5-node/README_pi5_node.md
ops/pi5-node/mesh-up.sh
ops/pi5-node/setup_pi5_node.sh

Más de este repositorio

mismo repositorio

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	ops-deploy-base-node
description	Use when: updating base node deployment, meshsa-base systemd service, Raspberry Pi 5 setup, mesh-up.sh, FreeTAKServer bridge install, env files, field runbooks, or ops scripts.
argument-hint	Target node type, deployment path, service change, and validation available

Deploy or Update a Base Node

When to Use

Change ops/base-service install docs, env examples, or systemd unit.
Change ops/pi5-node provisioning scripts or mesh setup.
Document field deployment of the Meshtastic to FreeTAKServer bridge.

Procedure

Read ../../../ops/AGENTS.md.
Keep service, install guide, and env example in sync.
Use meshsa-base as the installed entry point; do not reference deleted root scripts or old meshsa_framework paths.
Keep credentials, PSKs, host-specific callsigns, and tokens out of tracked files. Use placeholders in .env.example files.
Preserve graceful shutdown (KillSignal=SIGINT) for the asyncio bridge.
For Pi scripts, prefer idempotent setup steps and explicit package names.
Update root README deployment links if paths change.
State whether validation was docs-only, syntax-only, or hardware-tested.

References

ops/base-service/INSTALL_base_node.md
ops/base-service/base.env.example
ops/base-service/meshsa-base.service
ops/pi5-node/README_pi5_node.md
ops/pi5-node/mesh-up.sh
ops/pi5-node/setup_pi5_node.sh