yahboom-operator

name	yahboom-operator
description	Use this skill when controlling or troubleshooting a Yahboom Raspbot v2 (or compatible) robot via the Yahboom MCP server.

Yahboom Raspbot v2 Operator Skill

Use this skill when controlling or troubleshooting a Yahboom Raspbot v2 (or compatible) robot via the Yahboom MCP server. For hardware, ROS 2, frames, and integration depth use yahboom-robots-expert.

🛠️ Tool Set

• yahboom(operation, param1, param2, payload) — Single operation. operation one of: health_check, forward, backward, turn_left, turn_right, strafe_left, strafe_right, stop, read_imu, read_battery, read_encoders, start_recording, stop_recording, list_trajectories, config_show. Use param1 for speed/duration where applicable.
• lidar(operation, source, param1, param2, payload) — LIDAR/map: operation one of read, read_raw, read_dreame_map; source one of yahboom, dreame, auto. Yahboom /scan when bridge connected; Dreame D20 Pro scan when DREAME_MAP_URL set.
• yahboom_help(category, topic) — Drill-down help. Categories: motion, sensors, connection, api, mcp_tools, startup, troubleshooting.
• yahboom_agentic_workflow(goal) — High-level goal (SEP-1577). Describe what you want the robot to do in natural language; the LLM plans and runs a sequence of health/motion/sensor steps.

📝 Prompts

• yahboom_quick_start(robot_ip) — Setup instructions for connecting the server to the robot.
• yahboom_patrol(duration_seconds) — Get a patrol plan (e.g. square or figure-8).
• yahboom_diagnostics() — Diagnostic checklist for connection and sensors.
• yahboom_patrol_apartment() — Standard action: full circuit of main rooms, avoid obstacles, return to start.
• yahboom_go_to_recharge() — Standard action: drive to charging station and stop (contactless recharger to be equipped later).

🧭 Workflow Rules

1. Safety First: Always run yahboom(operation='health_check') before motion to confirm bridge and battery.
2. Goal-Oriented: Use yahboom_agentic_workflow for multi-step goals (patrol, inspect, return); use single yahboom calls for one-off commands.
3. Power Management: For low battery (< 20%) avoid long motions; suggest charging.
4. Knowledge Recall: Recording trajectories: start_recording, then motion, then stop_recording with a name.

📄 Reference Scripts

• scripts/check_health.py — Call REST API health/telemetry (no MCP client).
• scripts/run_patrol_square.ps1 — Example: start server in dual mode and open dashboard (user runs agentic workflow from Chat or MCP client).