ワンクリックで
yoyopod-screenshot
Capture a screenshot of the active YoYoPod display from Raspberry Pi
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Capture a screenshot of the active YoYoPod display from Raspberry Pi
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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)
Health check for Raspberry Pi lanes, runtime, connectivity, processes, memory, recent logs
Sync a committed branch / SHA to the Raspberry Pi dev lane
| name | yoyopod-screenshot |
| description | Capture a screenshot of the active YoYoPod display from Raspberry Pi |
| disable-model-invocation | true |
| allowed-tools | ["Read","Bash(yoyopod target:*)"] |
| argument-hint | [--readback] |
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. Screenshots target the
currently running lane; dev normally runs from /opt/yoyopod-dev/checkout,
and prod runs from /opt/yoyopod-prod/current. yoyopod target merges
the config files directly.
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.
Parse the arguments string provided after /yoyopod-screenshot:
--readback is present, request LVGL
readback. Otherwise use the shadow buffer.Check lane state.
yoyopod target mode status
Capture the screenshot to a temporary local PNG. Run:
yoyopod target screenshot [--readback] --out <local_temp_path>
Use a temporary local path such as ./pi_screenshot.png.
Display the PNG. Use the agent's local image viewing tool to show the saved screenshot in the conversation.
Explain what was captured. After showing the image:
--readback: "This is the requested LVGL readback path — what
LVGL actually rendered if the native snapshot succeeded."Remind the user they can ask follow-up questions about what they see, such as "why is the status bar missing?" or "what screen is this?"
If the user is debugging screenshot fidelity, verify the capture path in logs. Run:
yoyopod target logs --lines 20
Confirm one of these outcomes:
Saved screenshot via LVGL readback means the readback path succeeded.Saved screenshot via shadow buffer means the capture used the
shadow path instead.Clean up. Delete the temporary local screenshot file after displaying it.