Universal Robots 机器人控制技能 - URSim 仿真 + URScript + RTDE
v1.0.1支持Universal Robots仿真与控制,包含URSim仿真、URScript指令发送及RTDE数据通信接口,支持关节与笛卡尔空间运动。
⭐ 0· 65·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 match the included files and instructions: Python SDK, RTDE/URScript examples, URSim Docker guidance and test scripts. Required capabilities (network sockets to robot IPs, Docker image universalrobots/ursim_e-series, ur_rtde Python package) are expected for this purpose.
Instruction Scope
SKILL.md and scripts explicitly instruct the agent/user to run Docker, open sockets to robot IPs (localhost / 192.168.x.x), edit real_robot_config.json, and run many test scripts that send URScript/RTDE messages. This is expected, but it means the skill will open network connections on your LAN and can send commands that move a robot — do NOT run the 'real' tests against a physical robot without safety checks and certified supervision.
Install Mechanism
There is no formal install spec, but some scripts (e.g., check_ur_rtde.py) attempt to install dependencies at runtime via pip (subprocess.check_call to pip). That is a moderate risk operationally (network fetch and package install during execution) even if the pip target (ur_rtde) is legitimate.
Credentials
The skill requests no environment variables, no credentials, and no config paths beyond its own real_robot_config.json. This is proportionate to a robotics control library. No unexpected secrets or cross-service credentials are requested.
Persistence & Privilege
Skill metadata does not request always:true. It does not modify other skills. It contains scripts that may write test_reports and update local files under the skill directory (expected). Autonomous model invocation is allowed (platform default) but not combined with other concerning flags.
Scan Findings in Context
[SUBPROCESS_PIP_INSTALL] unexpected: check_ur_rtde.py calls subprocess.check_call([sys.executable, '-m', 'pip', 'install', 'ur_rtde']) if import fails. Installing packages at runtime is operationally useful but can be surprising; not strictly required by the skill manifest which lists dependencies but has no install spec.
[SOCKET_NETWORK_IO] expected: Many examples and utility functions open TCP sockets to robot IPs (30003/30004 etc.) to send URScript and RTDE messages — this is expected behavior for a robot-control skill.
[EXECUTE_REMOTE_COMMANDS] expected: Scripts send movement/IO commands to remote devices (robots). This is the primary function but is also the main safety risk when run against physical hardware.
Assessment
This skill package and its documentation are coherent with a UR robot control SDK and simulator workflow. Before installing or running it:
- Treat it as software that will open network sockets to robot IPs and can send motion commands — do not run 'real' test scripts against a physical robot unless you have a certified operator present, emergency stop available, and you run at very low speeds. Follow the included safety_check.py and the SKILL.md real-robot warnings.
- Review and control when/where dependencies are installed: some helper scripts will run pip install at runtime. Prefer to install dependencies manually in a contained environment (virtualenv / container) where you control network access and package sources.
- Use URSim (Docker) for testing first, ideally inside an isolated VM or network namespace so accidental scans/commands don't reach other devices. The Docker image referenced (universalrobots/ursim_e-series) is the expected upstream image — pull only from the official registry.
- Note there is no published homepage or repository URL in the manifest and the owner ID is an opaque string; that reduces traceability. If you need higher assurance, ask the publisher for a source repository or signed release artifacts.
- If you will run on real hardware, audit the specific test scripts you plan to run (they contain motion sequences and IO toggles) and confirm safety limits (workspace, speeds, emergency stop) in real_robot_config.json.
If you want, I can: (a) point out every place a network socket is created in the codebase, (b) extract the exact lines that perform pip installs, or (c) produce a short checklist to run the package safely inside a VM before real-robot testing.Like a lobster shell, security has layers — review code before you run it.
automationvk9774wvmvy439jdptwfx5xskc5842fw6latestvk9774wvmvy439jdptwfx5xskc5842fw6robotvk9774wvmvy439jdptwfx5xskc5842fw6rtdevk9774wvmvy439jdptwfx5xskc5842fw6universal-robotsvk9774wvmvy439jdptwfx5xskc5842fw6urvk9774wvmvy439jdptwfx5xskc5842fw6ursimvk9774wvmvy439jdptwfx5xskc5842fw6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
