Skillv1.0.2

ClawScan security

ros2-engineering-skills · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 17, 2026, 8:41 AM

Verdict: Benign
Confidence: medium
Model: gpt-5-mini
Summary: The skill's files, runtime instructions, and included scripts are coherent with a ROS 2 engineering guide; there are no disproportionate environment/credential requests or suspicious install mechanisms, but the repository source is not linked in the registry and you should inspect scripts before executing them locally.
Guidance: This skill appears coherent for ROS 2 engineering work, but you should: 1) Verify the source before cloning or running code — the registry entry has no homepage and README points to a GitHub user (confirm the repository and maintainer). 2) Review the included scripts (create_package.py, launch_validator.py, qos_checker.py, rosbag2_qos_checker.py) for any shell execution, network calls, or filesystem operations before running them locally. 3) If you plan to run tests or Docker flows, do so in an isolated environment (CI runner or sandbox) to avoid unexpected system changes. 4) Prefer installing from an official or well-known repository and verify commit history/signatures or vendor-provided checksums when possible. If you want, I can scan the contents of specific script files for obvious risky patterns (shell.exec, subprocess calls, remote downloads) and summarize them.

Review Dimensions

Purpose & Capability: okName, description, SKILL.md, README, reference documents, utility scripts, and tests all align with a comprehensive ROS 2 engineering guide. The included scripts (create_package.py, launch_validator.py, qos_checker.py, rosbag2_qos_checker.py) and 20+ reference files are reasonable for the stated purpose.
Instruction Scope: okSKILL.md instructs the agent to route to domain-specific reference files and to apply core engineering principles. It does not direct the agent to read unrelated system files, capture secrets, or exfiltrate data. The reference files contain normal developer guidance and command examples (docker, ros2 doctor, ros2 CLI, apt, etc.) which are expected for ROS 2 workflows.
Install Mechanism: noteNo install spec is declared in the registry (instruction-only skill); the package includes code and README installation examples that suggest cloning from a GitHub repo. Cloning or running included scripts would write files and execute code locally — that's normal for this type of skill but users should inspect code before executing or cloning from untrusted sources.
Credentials: okThe skill declares no required environment variables, credentials, or config paths. The content references environment variables commonly used in ROS/Docker examples (ROS_DOMAIN_ID, CYCLONEDDS_URI) only as usage examples; no unexplained SECRET/TOKEN variables are requested.
Persistence & Privilege: okSkill metadata does not request always:true and uses normal defaults (user-invocable, agent-autonomous invocation permitted). It does not indicate modifying other skills or system-wide agent settings. The default autonomous invocation is noted but not combined with other red flags.