Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Version 0.1.7 - Removed legacy configuration helper script: scripts/lib/config.sh. - Updated documentation to clarify that ROS environment setup is now required externally; the skill no longer sources ROS setup scripts. - Updated prerequisites and safety notes to remove references to auto-created workspace-local config and sourcing setup scripts. - Funding command information in documentation now only refers to message template, not balance checking.
What This Skill Does
Runs core ROS 2 nodes and calls peaq network services (DID, storage, access control) on a machine with an existing peaq-robotics-ros2 workspace. Assumes the workspace is already built and the ROS environment is initialized. Does not handle installation, wallet operations, or fund transfers.
Scoping core to read/write service calls keeps the attack surface small enough for registry approval without needing a separate admin skill for everyday operations.
When to use it
- Start and stop the peaq ROS 2 core node
- Create or read a robot DID on the peaq network
- Store and retrieve sensor data via peaq storage service
- Define roles and permissions for robot access control
- Generate a funding request message for a robot agent
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Read my DID, store this JSON as agent_state, then read it back.
- 1Runs core-start to bring up the peaq ROS 2 core node
- 2Calls did-read to retrieve the current DID from the peaq network
- 3Calls store-add with key agent_state and the provided JSON payload
- 4Calls store-read agent_state to confirm the data was written
- 5Returns the DID and storage read results to the user
DID document and stored agent_state JSON printed to output
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.