← ClaudeAtlas

video-demo-boothlisted

Use when building the attendee-facing side of an AI video demo activation — a kiosk where someone is photographed, sees themselves inside generated video, and takes it home by QR. Covers the booth UI, client watermarking, and packaging it as one shareable binary with replay and live modes. Trigger with 'demo booth', 'video activation', 'kiosk', 'photo booth', 'package the demo', or after video-model-bakeoff has picked a model.
thepandanlabs/video-gen-demo-booth · ★ 1 · Code & Development · score 64
Install: claude install-skill thepandanlabs/video-gen-demo-booth
# Video demo booth Build the thing an attendee touches, then package it so anyone can run it. ## What you are building ``` booth/ index.html one page, N screens toggled by a CSS class app.js state machine, camera, provider polling style.css the design direction, per client main.go one binary: serves the page, holds the key, delivers the film brand/ client logo, watermark assets scenes/ backplates or product shots demo/ pre-recorded films for replay mode ``` No framework, no build step. One binary and three static files. **The Go server is not optional.** The API key cannot go in the browser, so something server-side has to hold it. That same binary then earns its keep: it delivers the take-home film, burns the watermark, and gives you a preflight check. ## Two modes, one binary | | default | `-live` | |---|---|---| | Calls the provider | never | yes | | Needs a key | no | yes | | Needs ffmpeg | no | for the watermark | | Cost | $0 | per run | | Whose face | pre-recorded | the person at the screen | **Replay is the default because it is the safe one.** It cannot spend money and cannot fail in front of a room. `-live` opts in, and only that path has prerequisites — which it checks and reports all at once before starting, rather than dying one screen into a demo. This shape matters more than it looks. A demo you post to someone must not be able to spend your credit, and a static file server answering `POST /api/subm