Most ROS2 tutorials skip the security chapter, which is why so many research robots ship with unauthenticated DDS topics that let anyone on the network publish to /cmd_vel. This skill walks you through SROS2 keystore generation, per-node certificate setup, and writing the governance and permissions XML that actually enforces publish/subscribe access control at the DDS layer. It covers the full attack surface from open multicast discovery to unsigned firmware updates, and includes practical launch file snippets for running nodes in Enforce mode. The physical-cyber safety framing is honest: on a robot, a compromised topic isn't just a data leak, it's a collision or worse.

skills.sh installs
115
GitHub stars
400
last updated
May 25, 2026

Install

$ npx -y skills add arpitg1304/robotics-agent-skills --skill robotics-security --agent claude-code

Installs into .claude/skills of the current project.

Files

Robotics Security Skill

When to Use This Skill

  • Enabling SROS2 encryption and access control on ROS2 topics/services
  • Generating keystores, certificates, and security policies for DDS
  • Hardening robot onboard computers (SSH, firewalls, minimal packages)
  • Setting up network segmentation between robot control/data/management planes
  • Managing secrets and credentials across a robot fleet
  • Securing Docker containers running ROS2 nodes
  • Designing e-stop and safety systems that survive cyber compromise
  • Auditing a robot system for security vulnerabilities
  • Implementing secure boot and firmware verification
  • Addressing IEC 62443 requirements for industrial robot deployments

The Robot Attack Surface

Robots are unique: cyber vulnerabilities become physical threats.

Sponsors

Details

Repository
github.com/arpitg1304/robotics-agent-skills
Categories
Security, AI & Agent Building
License
Apache-2.0
First seen
Jun 11, 2026

More from arpitg1304/robotics-agent-skills

All 11

Recommended

More Security
1agentworkforce avatargithub-oauth-nango-integrationagentworkforce/relayIf you're building GitHub OAuth where users log in *and* your app needs repo access, you'll hit the reconciliation problem: OAuth gives...0skills.sh installs
2elastic avatarsecurity-alert-triageelastic/agent-skills>0skills.sh installs
3elastic avatarsecurity-case-managementelastic/agent-skills>0skills.sh installs
4elastic avatarsecurity-detection-rule-managementelastic/agent-skills>0skills.sh installs
5elastic avatarsecurity-generate-security-sample-dataelastic/agent-skills>0skills.sh installs
6elastic avatarcloud-network-securityelastic/agent-skills>0skills.sh installs