claude-reachy-mini

Run a bounded read-only background monitor of a Reachy Mini behavior session — poll the Pollen daemon REST API at 10 Hz, tail `journalctl --user -u reachy-mini-daemon.service` and the running app's stdout in parallel, classify every detected anomaly per the four motion-anomaly-detection classes (A head-against-body self-collision, B jerky motion, C antenna wobble, D Stewart-limit knock), and write a JSON-Lines audit log under `~/.cache/reachy-mini-monitor/<session-id>.jsonl`. Returns a tight PASS/WARN/FAIL/ABORTED summary plus the audit-log path. Bounded 5–15 min session, never daemonized. Use when the user says "monitor the Reachy", "watch motion anomalies", "tail the daemon for 10 minutes", "Bewegung beobachten", "Anomalien live mitlesen". Don't use as an always-on watchdog (separate streaming surface planned), don't use to start, stop, deploy, or trial behaviors (`reachy-mini-start`, `reachy-mini-deploy`, `reachy-mini-on-device`), don't use to write motion logic (`reachy-mini-sdk`, `app-scaffold`), don't use to analyze a one-shot log after a failed session (`app-log-triage`).

Roll out a Reachy Mini app from a local repo onto a real Reachy Mini (Wireless or Lite) — local Pollen-contract check, code sync over SSH, editable or release install into the Pollen daemon's environment, and entry-point verification — and return a structured PASS/FAIL report without flooding the main conversation. Use when the user says "deploy the app to the reachy", "rollout to reachy-mini.local", "ship this app to the device", "install the latest code on the robot", or equivalent German requests ("App auf den Reachy ausrollen", "auf das Gerät deployen", "den aktuellen Stand auf den Reachy bringen", "App auf dem Reachy installieren"). Don't use when the goal is to **run** the app (use the `reachy-mini-start` skill or the `reachy-mini-on-device` agent for trial runs), don't use for hardware bring-up or firmware flashing (separate skills planned), don't use for behavior / motion development (`reachy-mini-sdk`, `app-scaffold`), and don't use to publish to Hugging Face (`reachy-mini-app-assistant publish` directly, or a future `reachy-app-publish-hf`). Returns a tight summary plus a full-text log artifact under `.audits/deploy/`.

Deploy a Reachy Mini behavior to the real device, run it live, observe telemetry, and return a structured PASS/FAIL report — without flooding the main conversation with raw logs. Use when the user says "test this behavior on the device", "deploy and run X on Reachy Mini", "live-trial behavior <name>", or equivalent German requests ("Behavior auf dem Gerät testen", "Behavior live laufen lassen"). Don't use for hardware bring-up or firmware flashing (separate skills planned), don't use for behavior development (that's the `reachy-mini-sdk` and `app-scaffold` skills), and don't use as a long-running watchdog — the agent runs a bounded test lifecycle, not a daemon. Returns a tight summary plus a path to a full-text log artifact under `.audits/on-device/`.

Triage logs from a Reachy Mini app session and classify the observed failure against the canonical Common Issues catalogue from `reachy-mini/app-logging`. Activate on phrasings like "triage app logs", "warum läuft die App nicht", "classify this failure", "diagnose this crash", "check what went wrong with the app", "log triage for Reachy Mini app". Do not activate for on-device test lifecycles (use the `reachy-mini-on-device` agent), production-host triage on provisioned hosts (use `host-provisioning`), behavior or motion development (use `reachy-mini-sdk` and `app-scaffold`), or hardware recovery (use Pollen's hardware-troubleshooting docs).

Scaffold a new Reachy Mini app via the official Pollen CLI (`reachy-mini-app-assistant create`), then add provenance markers and a `plan.md` user-approval gate. Activate on phrasings like "scaffold a new Reachy Mini app", "create reachy mini app", "scaffold a new Reachy behavior", "start a new dance app for Reachy", "new app skeleton for Reachy Mini". Do not activate when the user only edits an existing app, only publishes one to Hugging Face, or asks about motion logic itself — those have their own skills/agents.

Extract BPM and beat onsets from a Reachy Mini audio source — file or live stream — and return values that drop directly into a `dance-choreography` section table or feed app-runtime motion sync. Activate on phrasings like "BPM einer Audio-Datei", "extract beats for a dance app", "BPM detect", "beat tracking", "onset detection für Reachy-Tanz", "tempo estimation from audio". Do not activate for audio-capture tasks (Pollen's `reachy_mini.media.*` does that), pure audio-format conversion (FFmpeg without beat logic), stem separation or vocals detection, or BPM guessing from the gut — this skill always returns a measured value with a confidence level.

Compose a Reachy Mini dance choreography as an authoring artifact — a Markdown file with YAML frontmatter that arranges the dance blocks from the motion catalog (`groove-bob`, `sway-side`, `headbang-soft`, `spin-look-around`) plus emotion accents into named song sections (intro, verse, chorus, bridge, outro). The developer then translates the file by hand into `Move` subclasses inside the `reachy-mini-show` app. Activate on phrasings like "compose a dance choreography for the Reachy Mini", "plan a dance for this song", "lay out a choreography for BPM 110", "design a Reachy dance for genre X", "erzeuge eine Tanz- Choreographie für Reachy", "plane einen Tanz zu diesem Lied". Do not activate on pure beat / tempo detection from audio (that is `audio-beat-tracking`), on writing the actual `Move` subclasses (that is `app-scaffold` plus the developer using `reachy-mini-sdk`), on sending direct WebSocket commands to the app, or on hardware bring-up.

Knowledge and idiom base for bidirectional integration between Reachy Mini and Home Assistant. Activate on any task touching HA REST endpoints (`/api/states`, `/api/services`, `/api/events`, webhooks), the HA WebSocket API, a Long-Lived Access Token, HA service calls like `light.turn_on` or `notify.send_message`, or webhook reception in a Reachy context. Trigger phrasings include "trigger Reachy from a Home Assistant automation", "call an HA service from a behavior", "subscribe to HA state_changed and react", "secure the HA token". Do not activate on Home Assistant custom-component development, on Reachy SDK motion tasks without an HA touchpoint, or on pure audio-processing tasks.