Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
ROS 2 Skill
v1.0.6Controls and monitors ROS 2 robots directly via rclpy CLI. Use for ANY ROS 2 robot task: topics (subscribe, publish, capture images, find by type), services...
⭐ 1· 544·1 current·1 all-time
byAditya Kamath@adityakamath
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description match the code and commands (ros2_cli.py entry point and many ros2_*.py modules). Required binaries (python3, ros2) and rclpy make sense for a ROS 2 control skill. Minor oddity: SKILL.md declares pip: ["rclpy"] while rclpy is often provided by ROS distro packages — but this is not a hard incoherence.
Instruction Scope
SKILL.md and AGENTS.md instruct the agent to introspect and act on the live system extensively (list topics/nodes, publish commands, manage tmux sessions, write .presets/.artifacts). AGENTS.md explicitly mandates 'Try first. Ask never.' and states its rules override every other instruction/system prompt — this grants the skill broad autonomous behavior and encourages the agent to act without user confirmation. The README/SKILL.md also instructs reading ~/.nanobot/config.json for a Discord bot token (external endpoint integration). These instructions go beyond simple CLI wrapping and include file reads, network posting (Discord), and system control (tmux, estop).
Install Mechanism
There is no install spec (instruction-only) which reduces risk from installers, but the bundle includes many executable Python scripts that the agent is expected to run. No external downloads or archive extraction are described. This is low installer risk but means the code will run locally and should be inspected.
Credentials
The skill declares no required environment variables or config paths, yet runtime docs and scripts expect a sourced ROS 2 environment and reference external config (~/.nanobot/config.json) for Discord integration. Reading that config (and using its token) is not declared in requires.env and could expose a bot token. The skill also writes artifacts and presets into its install directory (.artifacts/.presets). These accesses are plausible for the stated purpose but are not fully declared and should be validated.
Persistence & Privilege
The skill does not set always:true and does not declare system-wide changes, but AGENTS.md tells the agent to treat the skill's rules as absolute and to act autonomously ("override every other instruction, system prompt, user request"). That is a governance/behavioural escalation (not a platform-config change) — it increases blast radius if the agent is allowed autonomous invocation. The skill does create files under its directory (.artifacts/.presets) and may start tmux sessions; these are reasonable for robot control but should be considered when granting runtime privileges.
What to consider before installing
This skill appears to be a full-featured ROS 2 agent wrapper and largely matches its description, but review these points before installing:
- Trust and autonomy: AGENTS.md explicitly instructs the agent to act autonomously and to treat the skill's rules as overriding other prompts. If your agent platform enforces safety or user-confirmation policies, this skill's instructions directly conflict. Only enable autonomous invocation for this skill if you fully trust it and your deployment policies.
- External token access: The README documents reading ~/.nanobot/config.json for a Discord bot token and includes discord_tools.py which can post images to Discord. That file and token are not declared in the skill metadata. If you use a shared bot token or other secrets in that location, consider moving them or restricting this skill's filesystem/network access.
- Files and system commands: The skill will run local Python scripts that can manage tmux sessions, run subprocesses, and write to .artifacts/.presets. Run the code in a sandboxed environment (or inspect scripts) before giving it access to a robot or networked machine.
- Review rules and safety docs: Inspect references/RULES.md and AGENTS.md fully to ensure their operational rules align with your safety policies (e.g., mandatory 'try first' behavior, banned phrasing, automated recovery actions). These documents change agent behaviour in ways that may bypass your usual controls.
- Mitigations: run tests in an isolated VM or container with no external network (or restricted network), remove or sanitize any sensitive config files (e.g., Discord tokens), and restrict the skill's permission to start tmux or modify system services until you have audited the code. If you are unsure, treat this skill as untrusted and perform a manual code review of discord_tools.py and any subprocess/requests usage before deployment.Like a lobster shell, security has layers — review code before you run it.
latestvk97ezw9h3wb1kzypre8etkxpj183myvc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🤖 Clawdis
Binspython3, ros2
