TM Robot Control

Control and monitor OMRON TM collaborative robots with motion commands, status feedback, safety controls, camera support, and IO handling.

This package largely matches its stated purpose (OMRON TM robot control) and contains real control, parser and camera code — but exercise caution before running anything: - Do NOT run the included fix_*.py scripts without reviewing them. They contain hard-coded Windows paths (C:/Users/JMO/...) and will overwrite tm_robot.py at that path if executed. These look like developer cleanup tools left in the tree and are not required to use the skill. - The test and example scripts will open sockets to 192.168.1.13:5890/5891 and may send motion commands (including stop/reset/zero). Running them on a network with a real robot can move hardware; always ensure the robot is isolated and in a safe environment before executing motion scripts. - Change the default ROBOT_IP in config.py before use, and inspect all scripts for hard-coded IPs or paths. Search the codebase for absolute paths and any write operations (open(..., 'w')). - If you will install into a shared workspace, consider cloning to an isolated environment and running static analysis (or grep) for file writes, external network destinations, or subprocess/exec usage. - Verify the upstream repository/homepage links and the author (RobotQu). If you need higher assurance, ask the author for a signed release, git history, or a canonical GitHub release to confirm provenance. Given these developer-tool leftovers that can modify files and the physical safety implications of robot-control scripts, I rate the package as suspicious — not clearly malicious, but containing unexpected artifacts you should audit and remove/disable before running.

Type: OpenClaw Skill Name: tm-robot Version: 1.0.0 The bundle is a comprehensive and well-documented toolkit for controlling OMRON TM (Techman) collaborative robots via the techmanpy library and a custom SVR socket parser. It includes extensive features for motion control, state monitoring, and camera integration, supported by numerous diagnostic scripts and integration tests. While several files (e.g., fix_all.py, fix_indent.py, and various extraction scripts in the scripts/ directory) contain hardcoded absolute paths specific to the author's local Windows environment (C:/Users/JMO/...), these appear to be unintentional development artifacts rather than malicious indicators. No evidence of data exfiltration, unauthorized remote execution, or prompt injection was found.