peaq-robotics (Core)

What this skill is

Use this skill when a machine already has a working peaq-robotics-ros2 workspace and you want OpenClaw to run core ROS 2 nodes and call peaq services:

• - DID create/read
• Storage add/read
• Access role/permission operations

What this skill intentionally does NOT do

To keep this skill low-risk and easier to approve in registries, core excludes:

• - repo clone/build automation
• value transfer commands
• tether wallet operations
• runtime expansion of trusted setup/json roots via env overrides

If you need install/bootstrap/funding automation, use the companion admin skill (peaq-robotics-admin).

Required prerequisites

Before using core commands, make sure these are already true:

• - ROS 2 is installed and ros2 works.
• INLINECODE3 workspace is already present and built.
• INLINECODE4 points to that repo.
• Config YAML exists (either:

• - ROS environment is already initialized externally for the current shell/session.

Manual setup guide (no installer script required)

Do the repo clone/build/config steps manually outside this skill using upstream peaq-robotics-ros2 docs, then set env for OpenClaw runtime:

CODEBLOCK0

If users want their own custom helper script

Tell them to create their own wrapper with only required setup and explicit config:

CODEBLOCK1

They can then run this directly, or still use this skill's commands for service calls.

Core commands

Node lifecycle:

• - INLINECODE7
• INLINECODE8
• INLINECODE9
• INLINECODE10

Identity:

• - INLINECODE11
• INLINECODE12
• INLINECODE13
• INLINECODE14

Storage:

• - INLINECODE15
• INLINECODE16

Access control:

• - INLINECODE17
• INLINECODE18
• INLINECODE19
• INLINECODE20

Identity card helpers:

• - INLINECODE21
• INLINECODE22
• INLINECODE23

Funding request (message template only, no transfer):

• - INLINECODE24

Behavior and safety notes

• - This skill does not source ROS setup scripts itself; environment initialization must be done externally.
• INLINECODE25 inputs are restricted to built-in roots:

• - JSON arguments are parsed/validated before ROS 2 service calls.
• Service payloads are passed as JSON objects to ros2 service call (no shell YAML interpolation).

One-line human prompts

• - "Start peaq robotics core and create my DID. If I need funds, give me a one-line funding request."
• "Read my DID, store this JSON as agent_state, then read it back."
• "Create role operator, create permission move_robot, assign it, and show the response."

Deep reference

For full service names and fields, see:

• - INLINECODE32