⚠
Purpose & Capability
The skill's purpose (control a Reachy Mini) matches the included scripts (curl to robot REST API, SSH/scp for snapshots, GStreamer capture). However the skill metadata declares no required environment variables or credentials while the scripts clearly rely on REACHY_HOST, REACHY_SSH_USER, and REACHY_SSH_PASS (with defaults). Not declaring these required secrets/binaries is an incoherence: a robot-control skill should explicitly declare the robot host and credential requirements.
⚠
Instruction Scope
SKILL.md and the scripts instruct the agent to call the robot's REST API and to SSH/SCP into the device to capture camera frames. The scripts use sshpass, disable host-key checking (-o StrictHostKeyChecking=no), and perform scp/ssh commands — actions that access remote device credentials and copy files. These instructions stay within the claimed domain (robot control) but include insecure SSH options and implicit credential use that should be explicit and justified.
✓
Install Mechanism
No install spec (instruction-only + shipped scripts). That reduces installer risk because nothing is downloaded at install time. The runtime does depend on external binaries (curl, ssh, scp, sshpass, jq, gstreamer/Python GObject/Gst) but no packages are installed by the skill itself.
⚠
Credentials
The skill metadata lists no required environment variables or primary credential, but SKILL.md and the scripts require REACHY_HOST, REACHY_PORT, REACHY_SSH_USER, and REACHY_SSH_PASS (defaults provided, including a default password 'root'). The scripts will use sshpass if available and will accept a password from REACHY_SSH_PASS. This is disproportionate and under-declared: any skill that performs SSH to a device should declare and justify the credentials it needs and recommend safer alternatives (SSH key, restricted user).
ℹ
Persistence & Privilege
always:false (good). The skill can be invoked autonomously (platform default). Combined with the ability to use provided SSH credentials and call arbitrary API endpoints (the CLI supports raw API calls), autonomous invocation would increase blast radius — but autonomous invocation alone is not a disqualifier.