zsquadbot
v1.0.0Develop and control quadruped robots with motor commands, sensor fusion, gait generation, diagnostics, and communication protocols for platforms like Unitree...
⭐ 1· 221·0 current·0 all-time
by@wsteve
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the included files: gait generator, motor control, IMU reader, simulator, and exporters. The code operates on serial ports and sim state which is expected for a robot control toolbox. There are no unrelated credentials, network endpoints, or cloud SDKs requested.
Instruction Scope
SKILL.md shows step-by-step examples that are limited to simulator and direct hardware control via serial (e.g., /dev/ttyUSB0, /dev/ttyUSB1). That scope is appropriate for the stated purpose, but examples will talk to serial devices and write motion files to the working directory. Also note some minor inaccuracies in docs vs files (e.g., SKILL.md examples import a top-level 'quadruped' module which isn't present as a package module; some listed helper scripts are placeholders). Running motor-control examples on live hardware can physically move motors — a safety risk.
Install Mechanism
This is an instruction-only skill with bundled source files and no install spec or remote downloads. No external binary installers or archive downloads are present, which minimizes supply-chain risk.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. The code reads and writes local files (motion exports) and accesses serial devices — appropriate for robotics but not requesting excessive system secrets.
Persistence & Privilege
Skill is not always-enabled; it does not request permanent agent presence or modify other skill/system configs. It only contains scripts and runtime examples that run when invoked.
Assessment
This package appears coherent for quadruped development, but review and take precautions before running: 1) Safety first — motor_control.py and related scripts send raw commands over serial and can move real actuators; test in the simulator (sim_state/sim_control) before connecting to hardware and have an emergency stop in place. 2) Dependency check — the code expects pyserial and standard Python libs; install dependencies in a controlled virtualenv. 3) File and module mismatches — SKILL.md examples reference a top-level 'quadruped' import and some listed helper scripts that aren't present; you may need to adjust imports or run scripts with PYTHONPATH set to the skill folder. 4) Run tests in an isolated environment (or without physical devices connected) to verify behavior first. 5) If you plan to use it on a commercial platform (Unitree/ANYmal), confirm compatibility and safety limits; do not assume the code enforces hardware safety limits. If you want, I can point out specific code lines that warrant close review (e.g., serial packet formats, struct packing/unpacking, places that write files), or produce a short checklist to sandbox and smoke-test the skill safely.Like a lobster shell, security has layers — review code before you run it.
latestvk976cfr4t0wcpf50fe6c9n61f982k4yf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.