Menu
Health check for Raspberry Pi lanes, runtime, connectivity, processes, memory, recent logs
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Commit-safe Rust-first dev-lane branch/SHA deploy to Raspberry Pi
Restart the active YoYoPod dev lane service on Raspberry Pi
Tail YoYoPod runtime/service logs from Raspberry Pi
Manual fallback for fetching CI Rust artifacts onto the Pi (prefer /yoyopod-deploy)
Capture a screenshot of the active YoYoPod display from Raspberry Pi
Sync a committed branch / SHA to the Raspberry Pi dev lane
| name | yoyopod-status |
| description | Health check for Raspberry Pi lanes, runtime, connectivity, processes, memory, recent logs |
| disable-model-invocation | true |
| allowed-tools | ["Read","Bash(yoyopod target:*)"] |
Use deploy/pi-deploy.yaml as the shared deploy contract and
deploy/pi-deploy.local.yaml for machine-specific overrides such as
host, SSH user, dev lane checkout, and branch. The tracked dev default
is /opt/yoyopod-dev/checkout; prod slots live under /opt/yoyopod-prod.
yoyopod target merges the files directly, and yoyopod target config edit is the preferred way to create or update the local override.
If the file does not exist yet, run yoyopod target config edit first.
That command creates deploy/pi-deploy.local.yaml automatically before
opening it.
Check lane state first.
yoyopod target mode status
Run the runtime status command.
yoyopod target status
Present the result. Prefer a compact summary with:
yoyopod-runtime is running, plus its PIDIf yoyopod-runtime is not running, explicitly suggest the
lane-specific action:
Run `yoyopod target mode activate dev` for mutable PR testing, or
`yoyopod target mode activate prod` for the packaged slot lane.