peaq-robotics
Core peaq-robotics-ros2 runtime for OpenClaw. Start/stop ROS 2 nodes and call DID, storage, and access-control services. Use when requests are about running an existing peaq ROS2 workspace (not installing/building or sending funds).
Why use this skill?
Seamlessly manage your peaq-robotics-ros2 workspace with OpenClaw. Effortlessly control ROS 2 nodes, DIDs, storage, and access permissions for your robot fleet.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/lavish0000/peaq-roboticsWhat This Skill Does
The peaq-robotics skill provides a standardized runtime interface for the peaq-robotics-ros2 workspace within an OpenClaw agent environment. It is designed to bridge the gap between AI-driven commands and physical robot operations by orchestrating core ROS 2 node lifecycles and interacting with the peaq blockchain services. Specifically, it enables users to trigger core-start/stop commands, manage Decentralized Identifiers (DID), interact with decentralized storage, and handle complex access-control roles and permissions. This skill acts as a stable, production-oriented layer meant for machines that have already completed the initial setup of their ROS 2 workspace.
Installation
To integrate this skill into your OpenClaw agent, execute the following command in your terminal: clawhub install openclaw/skills/skills/lavish0000/peaq-robotics. Ensure that before usage, your PEAQ_ROS2_ROOT environment variable is correctly configured to point to your peaq-robotics-ros2 workspace. Prerequisites include a pre-built ROS 2 environment and a valid peaq_robot.yaml configuration file. If these dependencies are not met, the skill commands will fail as it does not perform automated installation or build tasks.
Use Cases
This skill is perfect for scenarios involving decentralized machine management. For example, a developer can command the agent to read current sensor data stored on the peaq blockchain or dynamically update access-control roles to allow a new operator to command the robot. It is frequently used for on-demand node activation during specific tasks or for auditing machine DID identities to verify the robot's authenticity within a network.
Example Prompts
- "Start the core ROS 2 nodes for my robot using the current workspace config."
- "Read the sensor data currently saved in the blockchain storage named 'sensor_data'."
- "Grant the 'operator' role to the DID 'did:peaq:5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQ' so they can move the robot."
Tips & Limitations
This skill strictly adheres to a low-risk design philosophy. It does not handle automated repo cloning, value transfers (funds), or tethering wallets to prevent accidental financial exposure. It is intentionally decoupled from peaq-robotics-admin to maintain a separation of concerns between operational tasks and administrative/deployment tasks. If you require automation for building or installing packages, please use the admin companion skill instead. Always ensure your ROS 2 environment is initialized in your shell before invoking these commands to avoid runtime errors.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-lavish0000-peaq-robotics": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write, code-execution, external-api