← ClaudeAtlas

visualizationlisted

Choose and apply robotics visualization: selection guidance for rviz2 vs Foxglove vs Rerun, plus best practices — what to visualize at each dev stage, live vs recorded, local vs remote. Use when: 'visualize', 'see what the robot sees', 'debug visually', 'plot the trajectory', 'dashboard for the robot', choosing a viz tool, or recording data for later inspection. Umbrella skill — after selecting, load the matching tool skill: rviz2 (ROS-native debugging), foxglove (remote/web + MCAP recording), rerun (ML/data-centric logging). Not for: tool-specific how-to (the per-tool skills).
robium-ai/robium-plugin · ★ 0 · AI & Automation · score 73
Install: claude install-skill robium-ai/robium-plugin
# visualization The visualization-selection umbrella for robium. "I can't see what the robot is doing" is one of the fastest ways a debugging session stalls, and picking the wrong tool for the context (a local-display tool on a headless server, a ROS-native tool for a non-ROS ML pipeline) wastes more time than the debugging itself. This skill decides which of rviz2, Foxglove, or Rerun fits a given context, and states the cross-cutting practice of *what* to visualize at each build stage. It does not teach any one tool's UI, panels, or API — that is each tool's own skill. ## When to use this skill - A viz tool hasn't been chosen yet for the current context (local desktop, headless remote server, or an ML/data pipeline outside ROS). - The trigger phrases in the description: 'visualize', 'see what the robot sees', 'debug visually', 'plot the trajectory', 'dashboard for the robot'. - Deciding whether to look at data live or record it for later inspection, before wiring up either path. - Cross-references — go straight to the tool skill, skipping this one, once the tool is already chosen and the question is tool-specific: - RViz2 panel configuration, displays, or plugins on a local Linux desktop → `rviz2`. - Foxglove layouts, the Foxglove Bridge, or MCAP recording/playback → `foxglove`. - Rerun logging API, blueprints, or timeline views for ML/perception data → `rerun`. - Whether headless/remote is the deployment target at all (as opposed to which viz