← ClaudeAtlas

rviz2listed

RViz2 visualization for ROS 2: displays, TF frame debugging, markers, saved config files, and the common 'nothing shows up' fixes (fixed frame, QoS, sim time). Use when: 'rviz', 'rviz2', visualizing ROS topics, TF trees, costmaps, or robot models during development. ROS-native desktop debugging tool — for remote/web visualization use foxglove; for ML/data-centric logging use rerun. Pairs with ros2 and nav2.
robium-ai/robium-plugin · ★ 0 · AI & Automation · score 73
Install: claude install-skill robium-ai/robium-plugin
# rviz2 The local-desktop ROS 2 visualization tool: displays for topics, TF frames, markers, and robot models, driven by a saved `.rviz` config file per robot/task. RViz2 ships across every ROS 2 distro back to the earliest releases through **Lyrical Luth** (current LTS) and Rolling — verified via direct fetch of `index.ros.org`'s rviz2 package page this session (the `docs.ros.org` page returned an access-control error rather than content; see References) — so nothing in this skill is distro-gated the way Nav2's binary packages are; the only distro requirement is that `ROS_DISTRO` matches the sourced workspace. It is a standard Qt/OpenGL desktop app with no headless or web mode; for a remote/headless server or sharing a view, use `foxglove` instead (see Platform gotchas). ## When to use this skill - Adding or configuring a display (LaserScan, PointCloud2, RobotModel, TF, MarkerArray, Path, Costmap, Odometry, ...), debugging why a topic isn't rendering, or setting up a saved config for a robot/task. - The trigger phrases in the description: 'rviz', 'rviz2', visualizing ROS topics, TF trees, costmaps, or robot models during development. - A display is blank/nothing shows up — start here with the checklist in Usage patterns before assuming the publishing node itself is broken. - Cross-references — go to the sibling skill instead when the question is: - TF2 concepts themselves (frames, broadcasters, static vs dynamic transforms) or QoS concepts (reliability/durab