SKILLEMALL.ai
GitHub ↗ RU Sign in

CF ros2-skill

Controls 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 (list, call), actions (list, send goals), parameters (get, set, presets), nodes, lifecycle management, controllers (ros2_control), diagnostics, battery, system health checks, and more. When in doubt, use this skill — it covers the full ROS 2 operation surface. Never tell the user you cannot do something ROS 2-related without checking this skill first.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: Aditya Kamath v1.0.6 MIT-0 30 files body ≈ 734 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 43/100 · Will not run — References files that are not bundled: scripts/ros2_*.py

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
67/100
safety, quality, tests
Safety 60%
59
Quality 40%
79
Run on models
none yet
Process rating
F
43/100
Will not run
References files that are not bundled: scripts/ros2_*.py
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Instruction override
If you install

The text contains phrases like "ignore previous instructions" or "you are now…". That is an attempt to hijack the agent: it may break your rules, the system limits or company policy.

For the author

An honest skill does not need them: state the role and the rules directly without overriding other instructions. Otherwise catalog scanners and corporate filters will block the listing.

Concealment
If you install

The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 3

  • high Instruction override en-ignore-previous AGENTS.md:517
    Instruction-override phrase ("ignore previous instructions")
    All ROS 2 interactions go through `python3 {baseDir}/scripts/ros2_cli.py`. Never use `ros2 topic`, `ros2 service`, `ros2 action`, `ros2 param`, `ros2 node`, `ros2 lifecycle`, `ros2 control`, `ros2 doc
  • high Concealment en-hide-from-user references/RULES.md:239
    Instruction to hide actions from the user
    **Never tell the user you don't know how to do something** without first checking ros2-skill for a matching command. Common operations that agents sometimes use `ros2 CLI` for unnecessarily:
Medium and low: 1
  • medium Concealment en-hide-from-user SKILL.md:3
    Instruction to hide actions from the user (quoted — discussed, not commanded)
    description: "Controls 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 (list, call), actions (list,
    quoted

Files scanned: 29. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/ros2_*.py
  • note frontmatter-key unknown frontmatter key "user-invokable"

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: scripts/ros2_*.py
  • 0Tools and files. 1 referenced file(s) missing: scripts/ros2_*.py
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 100Steps. 14 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 734 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -319 of 20 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 510: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 14 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.

External checks

ClawHub: suspicious
This ROS 2 skill is mostly purpose-aligned, but it gives an agent broad live-robot control, persistent process control, and Discord file-sending ability with weak user-approval boundaries.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026