JARVIS AI Skills

WarnAudited by ClawScan on May 10, 2026.

Overview

This skill claims to control real robotic arms and grippers, but it provides no reviewed control code and no clear safety or approval limits.

Do not connect this skill to real robotic hardware based on these artifacts alone. First obtain and review the missing control code, verify the OpenClaw SDK provenance, run in simulation, and require explicit human confirmation plus physical safety controls before any movement or gripping command.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If connected to real hardware, mistaken or unintended commands could move a robot arm, grab or release objects, damage property, or injure someone nearby.

Why it was flagged

The skill describes direct physical robot and gripper operations, including sequenced actions, but does not define confirmation prompts, safety interlocks, workspace limits, or force/speed constraints for these high-impact actions.

Skill content
- Robotic arm movement (6-DOF)
- Gripper grab/release operations
- Action sequence execution
...
- "Jarvis, grab the object"
- "Jarvis, move to 10 20 30"
Recommendation

Use only in simulation or a controlled test environment until the skill adds explicit user approval, device allowlisting, emergency-stop guidance, workspace boundaries, and conservative force/speed defaults.

What this means

Users may need to obtain or create the missing control file separately, meaning the actual code that talks to robotic hardware may not be the code that was reviewed here.

Why it was flagged

The package declares a required control module, but the provided manifest contains only skill.json and SKILL.md and there is no install spec, so the core implementation that would control hardware is absent from review.

Skill content
"requiredFiles": ["openclaw_control.py"]
Recommendation

Require the complete implementation, pinned dependencies, and installation instructions to be included and reviewed before using this skill with any real robot.

What this means

A user could over-trust the stated safety features and use the skill around real hardware before verifying that collision detection, limits, and emergency controls actually work.

Why it was flagged

The skill makes broad safety and performance claims for powerful robotic hardware, but the reviewed package does not include the implementation needed to substantiate those claims.

Skill content
- Collision detection and safety
- Hardware auto-detection
...
- Payload: 3-500 kg (model-dependent)
- Speed: 1-7000 mm/s
Recommendation

Treat the safety and performance claims as unverified until tested against the specific robot model with independent safeguards in place.