ros-supervisor

Diagnoses and stabilizes ROS 2 workspaces by analyzing structure, build data, and live graphs.

1|Updated Mar 16, 2026

Search Tags:#workflow #debug #diagnose #ros2 #ros #bringup

Ready to run

npx skills add https://github.com/00PrabalK00/claude-skills --skill ros-supervisor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ros-supervisor
Source: https://github.com/00PrabalK00/claude-skills/tree/main/skills/ros-supervisor
Command: npx skills add https://github.com/00PrabalK00/claude-skills --skill ros-supervisor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Safely understand, diagnose, and improve ROS 2 systems by analyzing repository structure, package manifests, launch/config files, the active ROS graph, ros2 CLI output, logs, bag metadata, and runtime errors.

Core Features & Use Cases

Safe workspace analysis: verifies environment setup, package visibility, and bringup entry points.
Live graph diagnosis: inspects the running graph, topics, services, actions, QoS, and TF to identify misconfigurations.
Targeted fixes: proposes smallest safe edits and validates them with focused rebuilds.

Quick Start

Begin by running ROS environment and workspace checks, then inspect the ROS graph to propose a minimal safe fix.

Frequently Asked Questions about ros-supervisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose a ROS 2 workspace that fails during bringup?▼

To diagnose a failing ROS 2 workspace bringup, analyze the repository structure, package manifests, and launch configuration files. Verifying environment setup and package visibility helps identify misconfigurations preventing successful system startup.

What is the best way to debug a live ROS 2 graph with parameter drift and QoS issues?▼

Debugging a live ROS 2 graph involves inspecting active topics, services, actions, QoS profiles, and TF trees to pinpoint misconfigurations. Analyzing live graph data alongside ros2 CLI outputs and runtime logs allows you to classify and resolve parameter drift effectively.

How do I stabilize ROS 2 workspaces after detecting runtime errors?▼

Stabilize ROS 2 workspaces by proposing the smallest safe edits to your code and configuration. Validate these targeted fixes by performing focused rebuilds to ensure the parameter drift or QoS misconfiguration is resolved without introducing new issues.

What do I need to inspect a running ROS 2 graph for TF and topic issues?▼

You need access to the repository layout, package manifests, ros2 CLI outputs, logs, and optionally live graph data to inspect a running ROS 2 graph. This data allows the diagnostic workflow to snapshot the graph and classify TF and topic issues accurately.

Can I use terminal commands to fix ROS 2 launch and configuration misconfigurations?▼

Yes, you can fix ROS 2 launch and configuration misconfigurations via the terminal by following a structured workflow. The process checks the environment, surveys the workspace, snapshots the graph, proposes small fixes, and validates them with targeted rebuilds.