Robotics Agent Skills
Ten robotics skills: ROS 1 and ROS 2, QoS, tests, Docker, robot bringup, perception and security for coding agents
- 393 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The skills consist of instructions and code examples: they run nothing and make no network calls
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/robotics-agent-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills consist of instructions and code examples: they run nothing and make no network calls
This is third-party code. Review the repository files before installing.
What it does
Robotics Agent Skills is a set of ten SKILL.md files that add engineering knowledge of robotics to an agent. General models know ROS syntax well but miss the details that matter on a real robot: QoS compatibility, deterministic startup, bounded callbacks, sensor health checks and safe shutdown. The set has skills for ROS 1 and ROS 2, design principles, architecture patterns, perception, testing, Docker, web integration, robot bringup and security. The `ros2` skill covers `rclpy`, `rclcpp`, DDS, QoS, node lifecycle and components. The perception skill speaks about cameras, LiDAR, calibration and point clouds. The bringup skill describes systemd services, udev rules and watchdogs. The author also gives a comparison on one prompt, where an agent writes a ROS 2 package without the skills and with them. With them the result was a lifecycle node, different QoS profiles for sensors and status, buffers that count dropped data and 601 lines of tests; without them there were no tests. The author stresses that this is a single run, not checked against a real build, and not a benchmark.
Who it is for. For ROS robot developers who write nodes, launch files and tests together with Claude Code, Cursor or another agent that can read SKILL.md.
Good fit when
- An agent writes a ROS 2 package and you need lifecycle nodes, correct QoS profiles and parameters
- You maintain an older ROS 1 project with catkin, rospy, nodelets and XML launch files and plan to migrate it to ROS 2
- The robot must start by itself at power-on: systemd services, udev rules, watchdogs and log rotation
- You need tests for nodes: `pytest` with ROS, `launch_testing`, mock hardware and CI
- ROS 2 packages run in containers, with DDS across them and GPU access
Not a fit when
- You need Nav2 navigation, MoveIt2 manipulation or simulation: the author only plans separate skills for those
- The project has nothing to do with robots or ROS: the set offers no value outside robotics
- You need a ready robot control system: the skills give an agent knowledge and templates, and the agent writes the program
- You need proven improvements by metrics: the author's comparison is a single self-assessed run, an illustration and not a test
Example request
Write a ROS 2 package for recording robot demonstrations: a lifecycle node, QoS for the camera and joints, tests and a launch file.Limitations
The set covers ROS 1 and ROS 2 but not the full range of robotics work. In the roadmap the author lists skills not yet written: Nav2 navigation, MoveIt2 manipulation, ros2-control, simulation, robot description in URDF, debugging, data pipelines and multi-robot systems.
The comparison with and without skills was run once, graded by the author, and neither of the two packages was built against a real ROS 2 distribution. The known build defects are listed in the report evals/EVAL_REPORT.md. Skills go into the project's `.claude/skills/` directory or, for Autohand Code, into `.autohand/skills/`, and in custom frameworks the SKILL.md file is loaded into the system prompt.
The repository calls no outside services, so the set has no restrictions for Russia.
How to disable. Delete the folders of the installed skills from the project's `.claude/skills/` directory or the matching directory of another agent. You can delete the repository clone separately, it does not affect skills already installed.
FAQ
How do I install Robotics Agent Skills in Claude Code?
Clone the repository and run install.sh with your project's `.claude/skills` directory in --target and the skills you want in --skills. Or copy the folders from the skills directory by hand, for example with cp -R skills/ros2 into the project's skills directory.
Which skills are in the set?
Ten: `robotics-software-principles`, `ros1`, `ros2`, `robotics-design-patterns`, `robot-perception`, `robotics-testing`, `docker-ros2-development`, `ros2-web-integration`, `robot-bringup` and `robotics-security`.
Which skills should I take for a robot in service?
The author recommends the Production robot bundle: ros2, robot-bringup, robotics-security and robotics-testing. For a ROS 2 application add the design principles, and for older code take ros1.
Does the set work in Cursor and other agents?
Claude Code, Autohand Code, Cursor and Copilot-style agents understand the SKILL.md format. In custom frameworks the file is loaded into the system prompt, and the README gives a Python code example.
How solid is the evidence that the skills help?
Weak, and the author says so. The comparison is one run on one prompt, graded by the author, and the packages were not built on a real ROS 2. It illustrates the decisions the skills push toward and is not a measurement.
Discussion
No questions or reviews yet.
Related
SkillsA set of independent skills against drift in large codebases: hard-cut, root-cause tracing, lean testing and CI right-sizing.
Dimillian Skills
Skills
A set of 16 engineering skills for agents: Apple platform work, macOS packaging, React performance, code review and refactoring
Builder Skills
Skills for agents
A set of small skills from Builder.io for agent work habits: visual plans and diff recaps, docs-first checks, cross-agent review and clean status updates
Tech Leads Club Agent Skills
Agent Skills
A vetted skill registry with a CLI that installs into twenty-plus agents and an MCP server for on-demand skill lookup
The author's personal set: shared agent rules and dozens of skills for GitHub, the browser, macOS, messaging and releases, plus a sync script
Over 1,100 ready-made skills for Claude Code, Codex, Gemini CLI and Cursor, plus an MCP server that picks a skill for the task
README in short
The README explains why a robotics layer is needed on top of general agents and shows the comparison table, ready bundles of skills for typical tasks and ways to connect them in Claude Code, Autohand Code, Claude projects and custom frameworks. It ends with a roadmap of eight future skills and a link to the contribution rules.
README badge
Original SKILL.md
---
name: ros2
description: >
Comprehensive best practices, design patterns, and common pitfalls for ROS2 (Robot Operating System 2)
development. Use this skill when building ROS2 nodes, packages, launch files, components, or debugging
ROS2 systems. Trigger whenever the user mentions ROS2, colcon, rclpy, rclcpp, DDS, QoS, lifecycle nodes,
managed nodes, ROS2 launch, ROS2 parameters, ROS2 actions, nav2, MoveIt2, micro-ROS, or any ROS2-era
robotics middleware. Also trigger for ROS2 workspace setup, DDS tuning, intra-process communication,
ROS2 security, or deploying ROS2 in production. Also trigger for colcon build issues, ament_cmake,
ament_python, CMakeLists.txt for ROS2, package.xml dependencies, rosdep, workspace overlays, custom
message generation, or ROS2 build troubleshooting. Covers Humble, Iron, Jazzy, and Rolling distributions.
---
# ROS2 Development Skill
## When to Use This Skill
- Building ROS2 packages, nodes, or component containers
- Setting up colcon workspaces, ament_cmake, or ament_python packages
- Writing CMakeLists.txt, package.xml, or setup.py for ROS2
- Defining custom messages, services, or actions
- Writing Python launch files with conditional logic
- Configuring DDS middleware and QoS profiles
- Implementing lifecycle (managed) nodes
- Working with Nav2, MoveIt2, or other ROS2 frameworks
- Debugging DDS discovery, QoS mismatches, or build failures
- Deploying ROS2 to production or embedded systems (micro-ROS)
- Setting up CI/CD for ROS2 packages
## Core Architecture
### 1. Node Design Patterns
**Basic Node (rclpy)**:
```python
#!/usr/bin/env python3
import rclpy
from rclpy.node import Node
from rclpy.qos import QoSProfile, ReliabilityPolicy, HistoryPolicy
from std_msgs.msg import String
class PerceptionNode(Node):
def __init__(self):
super().__init__('perception_node')
# 1. Declare parameters with types and descriptions
self.declare_parameter('rate_hz', 30.0,
descriptor=ParameterDescriptor(
description='Processing rate in Hz',
floating_point_range=[FloatingPointRange(
from_value=1.0, to_value=120.0, step=0.0