drone-operations

Sterne11

Forks4

Aktualisiert4. Juli 2026 um 12:25

Operational runbook for the Tello/RMTT drone agent — flight, telemetry, and camera via the drone MCP tools.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

sebbycorp

sebbycorp/k8s-iceman

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Elektronikingenieure (außer Computer)Architektur- und Ingenieurberufe·SOC 17-2072

SKILL.md

readonly

name	drone-operations
description	Operational runbook for the Tello/RMTT drone agent — flight, telemetry, and camera via the drone MCP tools.

Drone Operations Runbook

You control a Ryze RoboMaster TT (RMTT) quadcopter over the Tello SDK via the drone MCP tools. The MCP server owns the drone's UDP link directly.

Facts

Drone static IP 172.16.10.168; SDK protocol v30. Command UDP 8889, state 8890, video 11111.
Battery drains while powered on (even idle on WiFi) and only charges while OFF. Takeoff below 15% is refused by the driver. Treat <30% as "land soon".
It is an RMTT, so EXT commands work via send_command (LED matrix, top LED, ToF): e.g. EXT mled s r heart, EXT mled r b 0.5 HI.

Tools

get_state — connected flag + telemetry (bat %, h height cm, pitch/roll/yaw, baro, temph). Start here to confirm the drone is connected and check battery.
Flight: takeoff, land, emergency (motor cut — real emergencies only), move(direction, distance_cm) (up/down/left/right/forward/back, 20-500), rotate(direction, degrees) (cw/ccw, 1-360), flip(direction) (f/b/l/r).
Camera: take_photo (returns the image — you can see and describe it), start_recording / stop_recording (mp4), list_media, get_media(name).
LED matrix: set_led_text(text, color, direction, rate) scrolls any message across the 8x8 matrix (color r/b/p, direction l/r/u/d, rate 0.1-2.5); clear_led blanks it.
send_command(command) — raw SDK passthrough for anything else, including other EXT.

Operating notes

Before flying, call get_state to confirm connected: true and read bat.
After any takeoff, be ready to land. Fly in small move increments.
If get_state shows connected: false or tools time out, the drone is powered off or off-network — say so rather than retrying blindly.
To "look around", take_photo and describe what you see; use move/rotate between shots.

Mehr aus diesem Repository

gleiches Repository

agentevals-website-contribution

sebbycorp/k8s-iceman

Contribution workflow for the agentevals-agent — branch naming, Hugo front matter, adding/editing docs pages, and PR conventions for the agentevals-dev/website repo.

2026-06-2911

kubernetes-troubleshooting

sebbycorp/k8s-iceman

Step-by-step diagnostics for a Kubernetes agent — CrashLoopBackOff, Pending pods, image pull failures, OOMKills, and high-latency investigation.

2026-06-2911

f5-bigip-operations

sebbycorp/k8s-iceman

Operational runbook for the F5 BIG-IP agent — safe procedures for draining pool members, HA-aware writes, certificate expiry checks, and diagnosing offline members.

2026-06-0911

fortigate-firewall-operations

sebbycorp/k8s-iceman

Operational runbook for the FortiGate agent — safe device blocking, firewall policy audits, overly-permissive rule detection, and wireless client troubleshooting.

2026-06-0911

vault-operations

sebbycorp/k8s-iceman

Operational runbook for the vault-agent — safe secret handling, mount-deletion safety, PKI best practices, and how Vault feeds this cluster via External Secrets.

2026-06-0911

name	drone-operations
description	Operational runbook for the Tello/RMTT drone agent — flight, telemetry, and camera via the drone MCP tools.

Drone Operations Runbook

You control a Ryze RoboMaster TT (RMTT) quadcopter over the Tello SDK via the drone MCP tools. The MCP server owns the drone's UDP link directly.

Facts

Drone static IP 172.16.10.168; SDK protocol v30. Command UDP 8889, state 8890, video 11111.
Battery drains while powered on (even idle on WiFi) and only charges while OFF. Takeoff below 15% is refused by the driver. Treat <30% as "land soon".
It is an RMTT, so EXT commands work via send_command (LED matrix, top LED, ToF): e.g. EXT mled s r heart, EXT mled r b 0.5 HI.

Tools

get_state — connected flag + telemetry (bat %, h height cm, pitch/roll/yaw, baro, temph). Start here to confirm the drone is connected and check battery.
Flight: takeoff, land, emergency (motor cut — real emergencies only), move(direction, distance_cm) (up/down/left/right/forward/back, 20-500), rotate(direction, degrees) (cw/ccw, 1-360), flip(direction) (f/b/l/r).
Camera: take_photo (returns the image — you can see and describe it), start_recording / stop_recording (mp4), list_media, get_media(name).
LED matrix: set_led_text(text, color, direction, rate) scrolls any message across the 8x8 matrix (color r/b/p, direction l/r/u/d, rate 0.1-2.5); clear_led blanks it.
send_command(command) — raw SDK passthrough for anything else, including other EXT.

Operating notes

Before flying, call get_state to confirm connected: true and read bat.
After any takeoff, be ready to land. Fly in small move increments.
If get_state shows connected: false or tools time out, the drone is powered off or off-network — say so rather than retrying blindly.
To "look around", take_photo and describe what you see; use move/rotate between shots.