Controls and monitors ROS 2 robots directly via rclpy. This skill provides a unified JSON interface for standard ROS 2 operations and agent-optimized workflows like closed-loop movement and image capture.
publish-until (closed-loop with odom) and publish-sequence (timed).ros2 doctor, manage launch files via tmux, and control ros2_control hardware.package.xml manifests — no live graph required.scripts/ros2_cli.py — this is the only file you should ever run directly.ros2_cli.py → rclpy → ROS 2 Graph{"error": "..."}.> ⚠️ Internal modules — do not run directly.
> All scripts/ros2_.py files other than ros2_cli.py are *internal
> implementation modules**, not standalone scripts. Running one directly
> prints an error to stderr and exits with code 1 — it performs no ROS
> operation. Always invoke commands through ros2_cli.py:
> ```bash
> python3 scripts/ros2_cli.py
> python3 scripts/ros2_cli.py --help # list all commands
> ```
To maintain performance and accuracy, this skill uses Progressive Disclosure:
source /opt/ros/${ROS_DISTRO}/setup.bash
Before any operation, verify the ROS 2 environment is active:
python3 scripts/ros2_cli.py version
Always check for velocity limits and active nodes before issuing movement commands. If a command hangs or the robot moves unsafely, use:
python3 scripts/ros2_cli.py estop
共 4 个版本