How do I install the Ros2 Troubleshooting skill?

Run npx skillmds@latest add leehyunbin0131/ros2-troubleshooting in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ros2 Troubleshooting safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ros2 Troubleshooting?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ros2 Troubleshooting free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ros2 Troubleshooting?

Leehyunbin0131 (@leehyunbin0131) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ros2 Troubleshooting by leehyunbin0131

Name: Ros2 Troubleshooting
Rating: 4.666666666666667 (3 reviews)
Author: Leehyunbin0131

Ros2 Troubleshooting

Diagnose ROS 2 Jazzy faults that reading the code cannot settle: QoS mismatch, sensor-mount and frame errors (REP 103/105), and odometry calibrated against CAD instead of the floor. Ships four runnable pass/fail checks.

File contents

ROS 2 troubleshooting

Most of this skill is scripts that turn a suspicion into an exit code. Run one before reasoning about the symptom.

Bundled checks

scripts/ sits next to this file — resolve the path from this skill's own directory, not the user's CWD. Under a plugin install that is ${CLAUDE_PLUGIN_ROOT}/skills/ros2-troubleshooting/scripts/.

They are plain scripts: invoke with python3 and a real path. There is no package to ros2 run, and inventing one is a known failure mode. Exit code 0 = PASS, 1 = FAIL, 2 = no data. Tell the user the command you ran.

source /opt/ros/jazzy/setup.bash
python3 <this-skill>/scripts/check_qos_compat.py --topic /scan

Script	Answers
`check_qos_compat.py --topic /scan`	Why a healthy publisher delivers nothing to this subscriber
`check_tf_tree.py --sensors laser_frame,imu_link`	Does `map->odom->base_link` resolve, and does each sensor's mount RPY match the hardware
`check_imu_gravity.py [--topic /imu/data]`	Is the IMU mounted the way the URDF claims — gravity ~+9.81 on +Z at rest
`check_odom_direction.py [--topic /odom]`	Does odometry agree with the direction the robot physically moved

check_tf_tree.py prints VERIFY PHYSICALLY for any ~180° roll or yaw even when that mounting is deliberate. It asks for a comparison against the hardware; it is not a verdict. Report it that way.

References

Load the one the symptom points at.

references/frames.md — REP 103/105 axis conventions, and the misalignment symptoms that follow from getting them wrong. CLAUDE.md treats this file as ground truth for any frame or TF question.
references/runtime.md — what a QoS mismatch actually looks like on Jazzy, the two other policies that fail the same way, and why ros2 topic echo cannot detect any of them.
references/calibration.md — correcting diff_drive_controller wheel radius and separation against a tape measure, in the order that works. Read when odometry is consistent but wrong by a ratio.

---name: ros2-troubleshootingdescription: Diagnose ROS 2 Jazzy faults that reading the code cannot settle: QoS mismatch, sensor-mount and frame errors (REP 103/105), and odometry calibrated against CAD instead of the floor. Ships four runnable pass/fail checks.---# ROS 2 troubleshootingMost of this skill is scripts that turn a suspicion into an exit code. Run onebefore reasoning about the symptom.## Bundled checks`scripts/` sits next to this file — resolve the path from this skill's owndirectory, not the user's CWD. Under a plugin install that is`${CLAUDE_PLUGIN_ROOT}/skills/ros2-troubleshooting/scripts/`.They are plain scripts: invoke with `python3` and a real path. There is nopackage to `ros2 run`, and inventing one is a known failure mode. Exit code**0 = PASS, 1 = FAIL, 2 = no data**. Tell the user the command you ran.```bashsource /opt/ros/jazzy/setup.bashpython3 <this-skill>/scripts/check_qos_compat.py --topic /scan```| Script | Answers || :--- | :--- || `check_qos_compat.py --topic /scan` | Why a healthy publisher delivers nothing to this subscriber || `check_tf_tree.py --sensors laser_frame,imu_link` | Does `map->odom->base_link` resolve, and does each sensor's mount RPY match the hardware || `check_imu_gravity.py [--topic /imu/data]` | Is the IMU mounted the way the URDF claims — gravity ~+9.81 on +Z at rest || `check_odom_direction.py [--topic /odom]` | Does odometry agree with the direction the robot physically moved |`check_tf_tree.py` prints `VERIFY PHYSICALLY` for any ~180° roll or yaw **evenwhen that mounting is deliberate**. It asks for a comparison against thehardware; it is not a verdict. Report it that way.## ReferencesLoad the one the symptom points at.- **`references/frames.md`** — REP 103/105 axis conventions, and the misalignment symptoms that follow from getting them wrong. `CLAUDE.md` treats this file as ground truth for any frame or TF question.- **`references/runtime.md`** — what a QoS mismatch actually looks like on Jazzy, the two other policies that fail the same way, and why `ros2 topic echo` cannot detect any of them.- **`references/calibration.md`** — correcting `diff_drive_controller` wheel radius and separation against a tape measure, in the order that works. Read when odometry is consistent but wrong by a ratio.

Frequently asked questions