AUBO Robot
v1.0.1通过 Python 和 RTDE 协议实现对 AUBO 协作机器人关节与笛卡尔空间运动的控制与状态实时反馈。
⭐ 0· 36·0 current·0 all-time
byRobot_Qu@qujingyang28
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name, description, SKILL.md and the Python driver all describe RTDE-based control of AUBO robots (connect to an IP:port, subscribe/publish RTDE channels, send motion scripts). There are no requested environment variables, unrelated binaries, or opaque external services required that would be inconsistent with robot control. Minor metadata issues exist (manifest/package.json claim different test/status info and a 'default_password' in manifest for the VM), but these are documentation inconsistencies rather than indicator of unrelated capabilities.
Instruction Scope
SKILL.md only instructs on setting up an ARCS VM, importing OVF, obtaining an IP, installing the AUBO SDK, and connecting via RTDE — all expected for a hardware/simulation integration. It does not tell the agent to read arbitrary host files, export secrets, or contact unknown web endpoints. The instructions assume local network access to a robot/VM and instruct using the AUBO developer/download URLs (expected).
Install Mechanism
No install spec is present (instruction-only skill + included driver file). The SKILL.md suggests pip installing an 'aubo-sdk' or downloading from the official AUBO site — both reasonable and traceable. No remote arbitrary archive downloads, URL shorteners, or extraction actions were found in the package metadata.
Credentials
The skill requires no environment variables, secrets, or cloud credentials. Its network access is limited to connecting to an IP:port (RTDE on port 30010) which is appropriate for robot control. One minor note: the manifest includes a 'default_password' field for the simulation VM (value 'q'), which is an insecure default for a VM but not a cloud credential; reviewers should treat that as a configuration hygiene issue.
Persistence & Privilege
always:false and there is no install script that modifies other skills or system-wide agent settings. The driver registers itself via a register_skill() function (normal). The skill can be invoked autonomously by the model (platform default) but does not request permanent elevated privileges.
Assessment
This skill appears to do what it says (RTDE-based control of AUBO robots) and does not ask for unrelated secrets. Before installing: 1) Verify the source/author (the package metadata references robotqu/RobotQu but 'Source' is unknown). 2) Prefer to run and test in an isolated network or sandboxed VM before allowing connections to real robots (network access to IP:30010 is required). 3) Obtain the AUBO SDK only from the official AUBO site and avoid third-party binary blobs. 4) Inspect the full driver file (the provided driver uses simple parsing, returns zeros in some getters, and contains minor bugs/typos such as 'chanel' in JSON recipe keys) — treat it as a developer preview, not production-ready. 5) Fix or review manifest/package discrepancies and change any default VM passwords before exposing the VM to a wider network. If you need higher assurance about provenance or integrity, request a canonical upstream source (git URL, signed release) or additional review of the code.Like a lobster shell, security has layers — review code before you run it.
latestvk97f1hpw1fn12pyppdkvb918t1847by8latest aubovk97eyfk67xm69j1hjw5fs3bqgd846dqz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.