Radar Collision Warning

v1.0.0

雷达防撞预警 — 调用树莓派上 ROS2 节点的雷达预警服务。当用户说"雷达防撞预警"、"开启雷达监控"、"检查障碍物"等时使用。通过 rosbridge WebSocket 向树莓派发送 ROS2 Service 请求,获取最近障碍物距离并给出预警。依赖 Node.js 18+(内置 WebSocket,无需安...

0· 81·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description say it will call a ROS2 service on a Raspberry Pi via rosbridge. Required binary (node) and included files (a Node.js client, a ROS2 Python node, and a Pi start script) match that purpose. No unrelated credentials or external services are requested.
Instruction Scope
SKILL.md instructs adding the Pi IP to a workspace doc or setting RADAR_HOST/RADAR_PORT env vars, running the local Node client for single queries or background monitoring, and how to deploy the Python ROS2 node on the Pi. The instructions do not ask the agent to read unrelated system files or exfiltrate data. They do tell the user to start rosbridge on port 8080 and run the lidar/node processes on the Pi, which is expected for this use case.
Install Mechanism
No network downloads or package installs are performed by the skill itself; it is instruction-only with bundled scripts. The skill relies on existing Node.js and ROS2 on the Pi, so there is no risky install mechanism in the skill bundle.
Credentials
The skill does not require secrets or environment variables beyond optional RADAR_HOST and RADAR_PORT to reach the user's Pi. The single declared binary dependency (node) is appropriate for the included Node.js client. No extraneous credentials or config paths are requested.
Persistence & Privilege
always is false, the skill is user-invocable and does not request permanent platform presence or modify other skills. It does not write to system-wide config or claim elevated privileges.
Assessment
This skill appears coherent with its stated goal, but review the following before installing: - Network exposure: the skill uses rosbridge over an unsecured ws:// connection (default port 8080). By default rosbridge accepts unauthenticated requests on the network. Only run this with the Raspberry Pi on a trusted LAN or protect rosbridge (firewall, VPN, or authentication) to avoid unauthorized access. - Physical-safety risk: the ROS node publishes (commented-out) flight control commands and exposes a service that could be extended to issue control messages. Before deploying on any robot or vehicle, inspect and test the code in a safe environment and ensure control topics are appropriately restricted. - Local deployment: you must install and run the Python ROS2 node and rosbridge on the Pi (the SKILL.md explains how). The Node.js client runs locally and only connects to the Pi IP you supply (RADAR_HOST / RADAR_PORT). Confirm you control that Pi and network. - Minor code issues: there are small non-security bugs (e.g., a -d test where -f was intended in the start script) and the service uses response.success to indicate a collision state (true == danger), which is a semantic choice to be aware of. If you understand and accept the network and physical-safety implications, the skill is coherent and implementable. If you plan to expose the Pi to broader networks, add authentication and firewalling for rosbridge first.

Like a lobster shell, security has layers — review code before you run it.

latestvk97e81bqgwhcms10mkmt2gtmph83rh0mradarvk97e81bqgwhcms10mkmt2gtmph83rh0mroboticsvk97e81bqgwhcms10mkmt2gtmph83rh0mrosvk97e81bqgwhcms10mkmt2gtmph83rh0m

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📡 Clawdis
Binsnode

Comments