Ros1 Noetic General
v0.1.1General bilingual ROS1 Noetic skill for ROS questions and ROS project operations across robot dogs, mobile robots, manipulators, perception pipelines, simula...
⭐ 0· 107·1 current·1 all-time
by@lljj123
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (ROS1 Noetic bringup, build, debug, OpenClaw integration) matches the included scripts and references: workspace probing, env checks, launch discovery, start/stop, health checks, interface checks, rosbridge guidance, and a motion script. There are no unrelated env vars, binaries, or install requirements declared.
Instruction Scope
SKILL.md explicitly instructs the agent to run the bundled scripts and to operate on local workspaces and runtime state. This is expected, but several scripts will perform actions with side effects: starting roslaunch/rosrun, launching rosbridge, recording logs/state files under /tmp, and the Python motion script publishes cmd_vel (actual motion). The skill includes safety guidance (ask before running sudo / hardware motion), but callers must still confirm before execution on real hardware.
Install Mechanism
No install spec — instruction-only with bundled scripts. The skill will not download or install external code at install time. The only execution risk is running the included scripts on the host; no external archives or URLs are fetched by an installer.
Credentials
The skill does not request secrets or environment variables. It expects and sources the normal ROS setup (e.g., /opt/ros/noetic/setup.zsh) and may create per-run ROS_HOME and state/log files under a tmp directory. No disproportionate credential access or unrelated config paths are requested.
Persistence & Privilege
always:false (default). The skill is user-invocable and allowed to be invoked autonomously by the agent platform (normal default). It writes its own run/state/log files under a per-run tmp directory but does not modify other skills or system-wide agent config. Note: autonomous invocation plus the ability to start/stop hardware means users should limit automatic runs without manual confirmation.
Assessment
This skill appears to do what it says: local ROS1 Noetic workspace and runtime management. Before installing or running it: 1) Inspect the bundled scripts yourself (they will run roslaunch/rosrun and can publish commands that move robots). 2) Do not run it on production hardware without explicit human confirmation; prefer simulation first. 3) If you intend to expose rosbridge, verify network/firewall rules and whitelist allowed topics/services. 4) Run initial commands in a contained environment (VM/container) or with a safety-estopped robot. 5) If you don't fully trust the source, avoid allowing autonomous invocation or manually review/limit which operations the agent can trigger.Like a lobster shell, security has layers — review code before you run it.
latestvk97967887abfjn0w8kw747nrnd83n4hb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.