ClawHub

ROS2 Control Introspection

v1.0.0

Execute ROS 2 Control read-only introspection commands (list, view) in a sandboxed environment. Supports parameter profiles.

⭐ 0· 49·0 current·0 all-time
byBrian Robinson@bigrobinson
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 skill exposes only read-only ros2 control subcommands, requires sourcing a ROS 2 environment and the AMENT_PREFIX_PATH (expected for ROS tools), and stores ROS setup/workspace paths in a local config file — all consistent with its stated purpose.
ℹ
Instruction Scope
Runtime instructions require sourcing ROS 2 setup scripts and running the provided safe wrapper. The wrapper enforces an allowlist of subcommands and executes ros2 via subprocess without shell=True. Note: the wrapper will source the ROS setup.bash (executing that file) to build the environment and can accept a user-supplied --params-file path or named profile (~/.openclaw/...), which will be read if provided; this is expected for parameterized introspection but means you should only provide trusted param files.
✓
Install Mechanism
There is no install spec and only small included scripts; nothing is downloaded or extracted from external URLs. Setup simply checks for ros2 and writes a local config.json — low-risk.
✓
Credentials
No credentials or secret env vars are requested. The script reads AMENT_PREFIX_PATH and discovers the ros2 binary and setup.bash (appropriate for ROS tooling). Allowing a user-specified params-file/profile is proportional to the feature.
✓
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and does not persist credentials or enable itself. It writes a local config.json within the skill tree (expected).
Assessment
This skill appears coherent and limited to read-only ROS 2 Control introspection. Before installing: (1) verify you trust the ROS 2 distribution referenced by the setup.bash path (the wrapper sources that file to build the environment), (2) inspect any parameter profile files you pass (~/ .openclaw/workspace/ros_profiles/<profile>.yaml or a --params-file) — they will be read and used by ros2, and (3) run the provided setup.sh only after sourcing your ROS environment as instructed. Avoid passing untrusted paths as --params-file; otherwise the skill is proportionate to its stated purpose.

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

latestvk97e4bpsgmzc4paem0fbhkma8984d8z5

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments