This skill exposes a CLI-driven interface for interacting with ROS and ROS2 robots through rosbridge. It provides commands to list topics, publish and subscribe to messages, call services, inspect nodes, change parameters (ROS2), and send actions. All outputs are JSON-formatted to make agent integration straightforward.
Use when an agent must inspect robot state, read sensor data, publish control messages, call services, or run actions on ROS/ROS2 systems reachable via rosbridge (default WebSocket port 9090). Suitable for diagnostics, automation, and remote robot control workflows — with caution for destructive commands.
ros_cli.py (command reference is in references/COMMANDS.md)websocket-client, launching rosbridge for ROS1/ROS2, connection examples, global flags (--ip, --port, --timeout), and many practical workflow examples (explore system, move robot, read sensors, services, params, actions). The skill highlights safety notes for destructive commands like publishing movement messages.Best for agents that can run Python CLIs and consume JSON output (e.g. OpenClaw agents, Copilot/Codex harnesses).
ROS/ROS2 robot control skill via rosbridge WebSocket CLI. Well-structured single-script tool covering topics, services, nodes, params, and actions with comprehensive command coverage. Script failed to run due to missing websocket-client dependency. No security issues found — no hardcoded credentials, no destructive commands, no data exfiltration. Network calls are only to user-specified rosbridge hosts.
websocket-clientClean skill with no security concerns. All WebSocket connections go to user-specified IP/port (defaults to localhost). No curl|bash, no hardcoded secrets, no telemetry, no auto-update. The skill can control physical robots (publish velocity commands) but this is its intended purpose and it includes safety notes about stopping robots after movement. Niche but well-executed for the ROS audience.