メニュー
Capture a verification video from the vivid virtual camera through the streamlib processor pipeline and send to Telegram. Use when the user asks for a verification video, test video, or wants to confirm the encode pipeline works.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run one reconciler pass of the standing milestone-loop — the turn procedure each `/work-on-milestone` firing invokes. Use when a loop firing (or the owner directly) needs to move the focused milestone one bounded step toward "merged, or waiting on the owner or on blockers." Checks the kill switch, probes rig capability, launches the milestone-loop workflow, and surfaces anything needing the owner. To START the loop on a milestone rather than run a single pass, use work-on-milestone.
Drive a whole milestone to done with the standing loop — resolve the milestone, set the goal, and register the recurring reconciler that runs passes until every issue is merged or parked. Use when the owner says "work on <milestone>", "start the loop on <milestone>", "close out <milestone>", or wants the loop running without hand-typing a /loop invocation. Also the place to stop or re-target a running milestone driver.
Take one ticket end-to-end in the current session with the owner present — the interactive counterpart to the standing loop. Use when they say "work on issue N", "let's do this ticket", "pick up X and I'll answer questions as you go", or want to drive a single issue to a PR now. Same workflow, same composed stages, same verifier as the loop — but questions come inline instead of parking.
Render the milestone-loop's current picture into one status board — what it's acting on, what's waiting on the owner (oldest first), what it's watching, recent outcomes, and spend. Use when asked "what's the loop doing", "loop status", "what's waiting on me", or before deciding whether to nudge or pause the loop. Read-only — it reports, it never acts.
Architecture-first entry point — recon the current code with the relevant domain experts, then produce a design brief for the owner (mermaid diagram, trade-offs, decisions taken, and an explicit decisions-for-owner list) posted to the issue. Use before building anything engine-zone, when a feature needs a shape decided, or when the owner asks to "design X first" or "draft the approach for this issue". Nothing builds until they approve in a comment.
Write a brand-new processor from source and submit it into a running StreamLib node as a fresh instance, optionally wiring its ports to existing processors in one transactional step, then confirm it landed and is producing. Use when adding a new stage to a live pipeline during development — a new filter, sink, or generator — without restarting the app. Wraps `streamlib submit` then `graph` + `tap` to confirm.
| name | verify-video |
| description | Capture a verification video from the vivid virtual camera through the streamlib processor pipeline and send to Telegram. Use when the user asks for a verification video, test video, or wants to confirm the encode pipeline works. |
| user_invocable | true |
| arguments | [{"name":"codec","description":"h264 or h265 (default: h265)","required":false},{"name":"duration","description":"seconds to capture (default: 5)","required":false}] |
Capture a verification video using the streamlib processor pipeline (Camera → Encoder → MP4Writer) and send it to the user via Telegram. Use this when the user asks to verify the video pipeline, requests a test video, or wants confirmation that encoding works.
codec: First argument — h264 or h265. Default: h265duration: Second argument — seconds to capture. Default: 5Delete any previous output:
rm -f /tmp/streamlib_live_h264.mp4 /tmp/streamlib_live_h265.mp4 /tmp/streamlib_test_h265.mp4
Run the streamlib pipeline example (debug build only — release has a known race condition, see #273):
timeout $((duration + 15)) cargo run -p vulkan-video-roundtrip -- $codec /dev/video2 $duration 60
Output: /tmp/streamlib_live_${codec}.mp4
If codec is h265, re-mux with hvc1 tag for Apple device playback:
ffmpeg -y -i /tmp/streamlib_live_h265.mp4 -c:v copy -c:a copy -tag:v hvc1 -movflags +faststart /tmp/streamlib_test_h265.mp4
Send path: /tmp/streamlib_test_h265.mp4
For h264, send path: /tmp/streamlib_live_h264.mp4
Verify the output with ffprobe:
ffprobe -v error -select_streams v:0 -show_entries stream=codec_name,r_frame_rate,nb_read_frames -count_frames -of csv $send_path
Send the MP4 to the user via Telegram using the reply tool. Look up the chat_id from memory (reference_telegram_chat). Include: codec, frame count, duration, and that it was captured from vivid virtual camera via the streamlib processor pipeline.
--release) — release build has a threading race condition (#273)/dev/video2 — outputs animated SMPTE color bars with frame counterv4l2-ctl --list-devicesduration + 2 seconds; the timeout wrapper adds extra margin for compilation