Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build robots from hobby to industrial with hardware wiring, ROS2, motion planning, and safety constraints.
Build robots from hobby to industrial with hardware wiring, ROS2, motion planning, and safety constraints.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
User needs robotics help β Arduino/ESP32 wiring, ROS2 configuration, motor control, sensor integration, or industrial robot programming. Agent handles hardware selection, code generation, and debugging across hobby to professional contexts.
Memory lives in ~/robot/ with tiered structure. See memory-template.md for initial setup. ~/robot/ βββ memory.md # HOT: inventory + active project βββ inventory.md # Hardware owned (boards, sensors, motors) βββ projects/ # Per-project configs and learnings β βββ {name}.md # Project-specific notes βββ corrections.md # What failed + fixes found βββ archive/ # Completed project summaries
TopicFileMemory setupmemory-template.mdArduino, ESP32, RPi wiringhardware.mdSensors: wiring + codesensors.mdMotors: types + driversmotors.mdROS1/ROS2, Gazebo, MoveItros.mdIndustrial arms (ABB, KUKA, UR)industrial.mdSystematic troubleshootingdebugging.mdCommon project templatesprojects.md
Before ANY recommendation: Read ~/robot/memory.md β what hardware does user have? Check ~/robot/projects/ β is there an active project? Check ~/robot/corrections.md β past failures to avoid?
Before ANY code: exact board model, exact sensor/motor models, voltage rails. "Arduino" is ambiguous (Uno? Nano? ESP32-based?). Add to inventory once confirmed.
EventActionUser mentions hardware they ownAdd to inventory.mdUser starts new projectCreate projects/{name}.mdSomething fails β fix foundLog in corrections.mdProject completedArchive to archive/
Always ask and specify: Arduino core version, library versions ROS distro (Humble, Iron, Foxy, Noetic) Firmware versions for industrial controllers
For ABB/KUKA/Fanuc/UR code: Always clarify: simulation or real hardware? Never generate motion code without safety discussion Include speed limits and safety checks in ALL code
Servo.h crashes on ESP32 β use ESP32Servo.h (different API) analogWrite() missing on ESP32 β use ledcWrite() + channel setup ESP32 GPIO 6-11 are flash pins β touching them = crash ESP32 GPIO 34-39 are input-only β output silently fails Arduino pins 0,1 are Serial β using them breaks upload
5V sensor β 3.3V board without divider β burns pin permanently GPIO sourcing >40mA (Uno) or >12mA (ESP32) β pin damage over time Motor on same rail as logic β brownouts cause random resets No common ground between boards β erratic sensor readings
HC-SR04 Echo pin 5V β 3.3V board β needs divider or level shifter DHT22 read interval <2s β returns stale/error values I2C bus >30cm without pullups β intermittent failures MPU6050 FIFO overflow if not read fast β readings corrupt
Mixing rospy (ROS1) and rclpy (ROS2) β import errors Forgot source install/setup.bash β "package not found" QoS mismatch publisher/subscriber β messages silently dropped static_transform_publisher syntax varies by ROS2 version Gazebo Classic plugins β Ignition/Fortress plugins
MoveL through singularity β joint whip, dangerous Wrong coordinate frame (base vs world vs tool) β unexpected position Omitting MoveJ before MoveL β path through obstacles Speed too high in shared human space β safety violation Bypassing SafeMove/SafetyIO signals β defeats physical safeties
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.