How do I install the Ros2 Package skill?

Run npx skillmds add majiayu000/ros2-package 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 Package safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ros2 Package?

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 Package free to use?

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

Who published Ros2 Package?

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

Ros2 Package by majiayu000 — Agent Skill

Name: Ros2 Package
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

ROS 2 Package Creation & Build Wiring (Ubuntu 24.04 LTS & ROS 2 Jazzy)

Most "it built fine but doesn't run" bugs are wiring, not code. This skill covers the seams between a source file and a runnable node.

1. Documentation Entry Points

For	Entry point
ament_cmake reference (install, exports, testing hooks)	`https://docs.ros.org/en/jazzy/How-To-Guides/Ament-CMake-Documentation.html`
Package creation, custom interfaces, colcon tutorials	`https://docs.ros.org/en/jazzy/Tutorials/`

Ground truth beats both: read a working installed package under /opt/ros/jazzy/share/<pkg>/ and copy its structure.

2. The Wiring That Makes a Node Runnable

ament_cmake: executables must install to lib/${PROJECT_NAME} exactly — that is the only place ros2 run looks. launch/ and params/ are not installed by default and need their own install(DIRECTORY ...) into share/${PROJECT_NAME}. ament_package() comes last, exactly once.

ament_python: package.xml needs <export><build_type>ament_python</build_type></export>, or colcon configures the package as ament_cmake and fails looking for a CMakeLists.txt that was never meant to exist.

setup.cfg needs the ROS-specific install location, not just [metadata]:

[develop]
script_dir=$base/lib/my_package
[install]
install_scripts=$base/lib/my_package

Without it, console_scripts still builds and installs, just not to lib/${PROJECT_NAME} — the same place ros2 run looks for ament_cmake executables — so the node is present but undiscoverable.

3. Custom Interfaces (`.msg` / `.srv`)

Interfaces require an ament_cmake package — they cannot live in an ament_python package. Standard practice is a dedicated <project>_interfaces package that your node packages depend on.

find_package(rosidl_default_generators REQUIRED)
rosidl_generate_interfaces(${PROJECT_NAME}     # first arg must start with the package name
  "msg/Num.msg"
  "srv/AddThreeInts.srv"
  DEPENDENCIES geometry_msgs
)

<buildtool_depend>rosidl_default_generators</buildtool_depend>
<exec_depend>rosidl_default_runtime</exec_depend>
<member_of_group>rosidl_interface_packages</member_of_group>

Verify the result with ros2 interface show my_pkg/msg/Num — if that fails, the generation never ran.

4. Strict Rules

After adding any new file, directory, or entry point: rebuild and re-source before concluding something is broken.

---name: ros2-packagedescription: Package & build wiring: ros2 pkg create, package.xml, ament_cmake CMakeLists, ament_python setup.py, colcon build/source, installing launch & config, custom .msg/.srv interface packages.--- # ROS 2 Package Creation & Build Wiring (Ubuntu 24.04 LTS & ROS 2 Jazzy) Most "it built fine but doesn't run" bugs are wiring, not code. This skill covers the seams between a source file and a runnable node. ## 1. Documentation Entry Points | For | Entry point | | :--- | :--- | | ament_cmake reference (install, exports, testing hooks) | `https://docs.ros.org/en/jazzy/How-To-Guides/Ament-CMake-Documentation.html` | | Package creation, custom interfaces, colcon tutorials | `https://docs.ros.org/en/jazzy/Tutorials/` | Ground truth beats both: read a working installed package under `/opt/ros/jazzy/share/<pkg>/` and copy its structure. ## 2. The Wiring That Makes a Node Runnable **`ament_cmake`**: executables must install to `lib/${PROJECT_NAME}` exactly — that is the only place `ros2 run` looks. `launch/` and `params/` are not installed by default and need their own `install(DIRECTORY ...)` into `share/${PROJECT_NAME}`. `ament_package()` comes last, exactly once. **`ament_python`**: `package.xml` needs `<export><build_type>ament_python</build_type></export>`, or colcon configures the package as `ament_cmake` and fails looking for a `CMakeLists.txt` that was never meant to exist. `setup.cfg` needs the ROS-specific install location, not just `[metadata]`: ```ini [develop] script_dir=$base/lib/my_package [install] install_scripts=$base/lib/my_package ``` Without it, `console_scripts` still builds and installs, just not to `lib/${PROJECT_NAME}` — the same place `ros2 run` looks for `ament_cmake` executables — so the node is present but undiscoverable. ## 3. Custom Interfaces (`.msg` / `.srv`) Interfaces require an **`ament_cmake`** package — they cannot live in an `ament_python` package. Standard practice is a dedicated `<project>_interfaces` package that your node packages depend on. ```cmake find_package(rosidl_default_generators REQUIRED) rosidl_generate_interfaces(${PROJECT_NAME} # first arg must start with the package name "msg/Num.msg" "srv/AddThreeInts.srv" DEPENDENCIES geometry_msgs ) ``` ```xml <buildtool_depend>rosidl_default_generators</buildtool_depend> <exec_depend>rosidl_default_runtime</exec_depend> <member_of_group>rosidl_interface_packages</member_of_group> ``` Verify the result with `ros2 interface show my_pkg/msg/Num` — if that fails, the generation never ran. ## 4. Strict Rules After adding any new file, directory, or entry point: rebuild **and** re-source before concluding something is broken.

Frequently asked questions