create-example

Create publish/subscribe ROS2 examples for zenoh-ros2-sdk message types.

26|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/ROBOTIS-GIT/zenoh_ros2_sdk --skill create-example
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-example
Source: https://github.com/ROBOTIS-GIT/zenoh_ros2_sdk/tree/main/.claude/skills/create-example
Command: npx skills add https://github.com/ROBOTIS-GIT/zenoh_ros2_sdk --skill create-example

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers through creating new publish/subscribe examples for the zenoh-ros2-sdk, enabling quick demonstration and testing of additional ROS2 message types.

Core Features & Use Cases

  • Template-driven example creation: generate publisher and subscriber templates for a selected ROS2 message type.
  • Structured project layout: follows the examples/ directory convention with numbered files for publishers (odd) and subscribers (even).
  • Documentation updates: requires updating examples/README.md to reflect new examples.

Quick Start

Create a new example by adding new files in the examples/ directory following the odd/even numbering convention.

Frequently Asked Questions about create-example

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

FAQPage Schema
How do I create new ROS2 publish/subscribe examples for zenoh-ros2-sdk?▼

To create ROS2 publish/subscribe examples for zenoh-ros2-sdk, generate new publisher and subscriber files in the examples directory using a template-driven workflow to test additional ROS2 message types.

What is the file naming convention for ROS2 publisher and subscriber examples?▼

The file naming convention for ROS2 examples assigns odd numbers to publisher files and even numbers to subscriber files within the examples directory to maintain structured project layout.

Do I need to update documentation when adding new ROS2 examples?▼

Yes, adding new ROS2 examples requires updating examples/README.md to reflect the newly created publish/subscribe templates and maintain accurate project documentation.

Can I use this template workflow to extend coverage for additional ROS2 message types?▼

Yes, this repeatable template workflow is designed for developers extending example coverage and testing additional ROS2 message types with the zenoh-ros2-sdk.

What's the best way to structure a ROS2 example project for zenoh-ros2-sdk?▼

The best way to structure ROS2 examples is following the examples/ directory convention with numbered files for publishers and subscribers, ensuring a structured project layout that separates publish and subscribe templates.