Expert guidance for ROS 2 (Jazzy) development in Python (rclpy) and C++ (rclcpp). Use whenever the user works with ROS 2 nodes, topics, services, actions, QoS, parameters, lifecycle nodes, executors, callback groups, launch files, colcon/ament builds, package.xml/setup.py, tf2, URDF/Xacro, DDS (Fast-DDS, Cyclone DDS), or ros2 CLI tools (run, launch, topic, node, service, param, bag, doctor). Also trigger on implicit cues: "my node can't see the topic", "messages aren't arriving", "callback not firing", "QoS mismatch", "transform lookup failed", "colcon build fails", "launch file not working", "which message type for", "how do I make two nodes talk", "robot not moving", "how to test a ROS node". ALSO use for ROS 2 + Gazebo simulation debugging -- whenever the user mentions Gazebo, gz sim, rosgzbridge, usesimtime, /clock, sim-to-real, or reports "the laser scan drifts when the robot turns", "the map gets corrupted", "odom doesn't match", "the robot tips over in Gazebo", "the scan is stuck", or any case where a ROS 2 graph and a physics simulator disagree -- even if they don't say "ROS 2" explicitly.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryScience & researchStars0
About this skill
Expert guidance for ROS 2 (Jazzy) development in Python (rclpy) and C++ (rclcpp). Use whenever the user works with ROS 2 nodes, topics, services, actions, QoS, parameters, lifecycle nodes, executors, callback groups, launch files, colcon/ament builds, package.xml/setup.py, tf2, URDF/Xacro, DDS (Fast-DDS, Cyclone DDS), or ros2 CLI tools (run, launch, topic, node, service, param, bag, doctor). Also trigger on implicit cues: "my node can't see the topic", "messages aren't arriving", "callback not firing", "QoS mismatch", "transform lookup failed", "colcon build fails", "launch file not working", "which message type for", "how do I make two nodes talk", "robot not moving", "how to test a ROS node". ALSO use for ROS 2 + Gazebo simulation debugging -- whenever the user mentions Gazebo, gz sim, rosgzbridge, usesimtime, /clock, sim-to-real, or reports "the laser scan drifts when the robot turns", "the map gets corrupted", "odom doesn't match", "the robot tips over in Gazebo", "the scan is stuck", or any case where a ROS 2 graph and a physics simulator disagree -- even if they don't say "ROS 2" explicitly.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Expert guidance for ROS 2 (Jazzy) development in Python (rclpy) and C++ (rclcpp). Use whenever the user works with ROS 2 nodes, topics, services, actions, QoS, parameters, lifecycle nodes, executors, callback groups, launch files, colcon/ament builds, package.xml/setup.py, tf2, URDF/Xacro, DDS (Fast-DDS, Cyclone DDS), or ros2 CLI tools (run, launch, topic, node, service, param, bag, doctor). Also trigger on implicit cues: "my node can't see the topic", "messages aren't arriving", "callback not firing", "QoS mismatch", "transform lookup failed", "colcon build fails", "launch file not working", "which message type for", "how do I make two nodes talk", "robot not moving", "how to test a ROS node". ALSO use for ROS 2 + Gazebo simulation debugging -- whenever the user mentions Gazebo, gz sim, ros_gz_bridge, use_sim_time, /clock, sim-to-real, or reports "the laser scan drifts when the robot turns", "the map gets corrupted", "odom doesn't match", "the robot tips over in Gazebo", "the scan is stuck", or any case where a ROS 2 graph and a physics simulator disagree -- even if they don't say "ROS 2" explicitly.
About this listing
Category
Science & research
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.