zsquadbot
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill matches its quadruped-robot purpose, but it can enable and command real motors with little safety gating, so it needs careful review before use.
Install only if you intentionally want quadruped robot-control code. Start with the simulator, keep real robots supported or disconnected during testing, verify serial ports and motor IDs, add explicit approval before any hardware motion, and review dependencies/import paths before running the shell scripts.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If an agent or user runs this while a robot is connected, motors may move unexpectedly and could damage the robot or injure someone.
The script enables every motor on connection and allows direct, unbounded position commands to connected hardware.
for motor_id in range(1, 13): ... motor.enable() ... elif cmd.startswith('pos'): pos = float(cmd.split()[1]); robot.motors[mid].set_position(pos)Use the simulator first; require explicit user approval before running hardware-control scripts; verify port and motor IDs; add motion limits, confirmations, and a tested emergency-stop procedure.
Tests may import code outside the installed skill or fail because the path does not exist.
The test script adds a hardcoded developer workspace to Python's import path, which creates provenance ambiguity if that path exists and may fail on other systems.
export PYTHONPATH="/Users/liuxing/.openclaw/workspace/skills/quadruped:$PYTHONPATH"
Remove hardcoded developer paths, use package-relative imports, and install required Python dependencies from trusted sources.