booth-loop-video
Skill95 starsChanged 6 days agoMITView on GitHub
Use this skill whenever the user asks for a looping booth, kiosk, trade-show, lobby-screen, or silent background video — including requests phrased as "a video loop for our stand", "an animated explainer with no voiceover", "a motion graphic for the monitor", or "turn this pitch into a looping MP4". Generate and run a self-contained Python render script (Pillow + ffmpeg) that outputs a 1920x1080 30fps MP4. Do NOT use this skill for videos that need narration, live footage, or editing of an existing video file.
- Installs packages
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Write a single self-contained script at work/booth_video.py.
- Distinctive: line 24
Only after previews look right, run the full render.
- Distinctive: line 27
All paths are relative to the current working directory:
- Distinctive: line 38
Write intermediate frames to the system temp directory, not the working folder.
- Distinctive: line 44
Use these unless the user supplies a brand palette.
- Distinctive: line 100
Never hardcode a single font path — it will fail on another machine.
- Distinctive: line 179
Never place accent-coloured text on the accent-coloured fill.
- Distinctive: line 180
Check contrast on a preview PNG, not in your head.
- Distinctive: line 221
After the first render, offer to tweak and accept plain-language feedback ("slower orbit", "bigger headline", "green instead of magenta").
- Distinctive: line 224
Never re-render the full video to check a colour change.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Booth / kiosk loop video
Produce a silent, looping MP4 (default 1920x1080, 30 fps, 60-135 s) suitable for a conference stand, a lobby screen, a reception kiosk, a LinkedIn post, or an embedded slide in a deck.
The output is a rendered animation, not a slideshow export. Every frame is painted in Python, so layout, timing, and easing are fully under your control.
Execution model — do the work, don't hand out instructions
You have Python and a shell. Never tell the user to open an editor or run the script themselves. You:
- Write a single self-contained script at
work/booth_video.py. - Install dependencies if missing:
pip install pillow imageio imageio-ffmpeg numpy(imageio-ffmpegships its own ffmpeg binary — no system install needed). - Render preview PNGs and show them to the user.
- Only after previews look right, run the full render.
- Report the output path.
All paths are relative to the current working directory:
{CWD}/
work/
booth_video.py
preview/scene_1.png ...
output/
booth_loop.mp4Write intermediate frames to the system temp directory, not the working folder. Rendering thousands of PNGs into a cloud-synced folder (OneDrive, Dropbox, iCloud) will stall the render and thrash the sync client.
Design defaults
Use these unless the user supplies a brand palette. Ask for their colours if the video is customer-facing; don't invent a brand.
| Canvas | 1920x1080, 30 fps |
| Duration | 60-135 s |
| Background | deep navy #0A1628 |
| Accents | #0078D4 primary, #B4009E secondary |
| Cards | #112244, 18 px corner radius, ~86% alpha |
| Type | humanist sans, generous whitespace |
| Motion | 0.5 s fade in, 0.3 s fade out per scene, smooth-step easing |
Dark, low-saturation background with two saturated accents reads well on a bright show floor and survives poor monitor calibration.
Script architecture
One file. A render_frame(t, total) function that returns a Pillow Image for time
t in seconds, and a scene table:
SCENES = [
(0.0, 8.0, scene_hook),
(8.0, 22.0, scene_problem),
(22.0, 40.0, scene_how_it_works),
# ...
(108.0, 120.0, scene_cta),
]
def render_frame(t, total):
img = Image.new("RGBA", (W, H), BG)
draw = ImageDraw.Draw(img)
for start, end, fn in SCENES:
if start <= t < end:
fn(draw, img, t - start, end - start)
return imgTime-relative scene functions (local_t, duration) make it trivial to reorder or
retime scenes later without touching their internals.
Animation helpers — always include these
def ease_in_out(t): return t * t * (3 - 2 * t)
def lerp(a, b, t): return a + (b - a) * t
def clamp(v, lo, hi): return max(lo, min(hi, v))
def fade(t, start, end): return clamp((t - start) / (end - start + 1e-6), 0.0, 1.0)Combine them: alpha = ease_in_out(fade(local_t, 0, 0.5)) * (1 - fade(local_t, dur - 0.3, dur))
gives a clean in/out envelope for any element.
Cross-platform font loading
Never hardcode a single font path — it will fail on another machine. Probe a candidate list per weight and fall back gracefully:
import os
from PIL import ImageFont
FONT_DIRS = [
"C:/Windows/Fonts", # Windows
"/usr/share/fonts/truetype/dejavu", # Linux
"/usr/share/fonts/truetype/liberation", # Linux
"/System/Library/Fonts/Supplemental", # macOS
"/Library/Fonts", # macOS
]
CANDIDATES = {
"light": ["segoeuil.ttf", "HelveticaNeue.ttc", "DejaVuSans-ExtraLight.ttf", "arial.ttf"],
"regular": ["segoeui.ttf", "Helvetica.ttc", "DejaVuSans.ttf", "LiberationSans-Regular.ttf", "arial.ttf"],
"semibold": ["seguisb.ttf", "DejaVuSans-Bold.ttf", "LiberationSans-Bold.ttf", "arialbd.ttf"],
"bold": ["segoeuib.ttf", "DejaVuSans-Bold.ttf", "LiberationSans-Bold.ttf", "arialbd.ttf"],
"mono": ["consola.ttf", "Menlo.ttc", "DejaVuSansMono.ttf", "cour.ttf"],
}
def get_font(weight, size):
for name in CANDIDATES.get(weight, CANDIDATES["regular"]):
for d in FONT_DIRS:
p = os.path.join(d, name)
if os.path.exists(p):
try:
return ImageFont.truetype(p, size)
except OSError:
continue
return ImageFont.load_default()Print which font actually resolved on the first call. A silent fall back to
load_default() produces a tiny bitmap font and a video that looks broken —
you want to know before the full render, not after.
Z-order rule — the one that bites
Pillow paints in call order: later calls sit on top. Draw connectors before the things they connect.
For any hub-and-spoke, node-and-edge, or step-and-arrow layout, split into two passes:
# Pass 1 — background layer: every connector
for item in items:
draw.line([hub_xy, item.xy], fill=LINE, width=2)
# Pass 2 — foreground layer: every node
draw_hub(draw, hub_xy)
for item in items:
draw_card(draw, item.xy, item.label)Interleaving the two passes draws lines across cards and through label text. This is the single most common defect in generated diagrams-in-motion, and it is invisible until you look at a rendered frame — which is why previews are mandatory.
Scene planning
Design for someone walking past at 3 m who gives you eight seconds.
- Hook (0-8 s) — one bold headline, one idea. No body copy. If a passer-by can't get the point from this scene alone, the video has already failed.
- Body scenes (8 s onward) — one concept per scene, 10-18 s each. Card layouts, animated counters, progress bars, typed-text reveals. Never more than ~25 words on screen at once.
- CTA (last 8-12 s) — what to do next, plus a name, booth number, or short URL.
End the CTA so it cuts cleanly back to the hook — the loop point should be invisible. Either fade fully to background colour, or make the first and last frames identical.
Contrast rules
- Dark card on dark background is unreadable on a show floor. For any chat, answer, or quote UI, put the response on a white or near-white card with dark text.
- Never place accent-coloured text on the accent-coloured fill.
- Check contrast on a preview PNG, not in your head. Show-floor lighting and cheap panels both crush shadow detail.
Preview before rendering
Full renders take minutes. Preview takes seconds. Always:
if PREVIEW:
os.makedirs("work/preview", exist_ok=True)
for i, (start, end, _) in enumerate(SCENES, 1):
mid = (start + end) / 2
render_frame(mid, TOTAL).convert("RGB").save(f"work/preview/scene_{i}.png")
raise SystemExitDisplay every preview inline to the user with markdown image syntax and get confirmation before the full render. URL-encode any spaces in the path.
Render loop
import imageio, numpy as np
writer = imageio.get_writer(
output_path, fps=FPS, codec="libx264",
output_params=["-crf", "18", "-pix_fmt", "yuv420p"],
)
for idx in range(int(TOTAL * FPS)):
t = idx / FPS
writer.append_data(np.array(render_frame(t, TOTAL).convert("RGB")))
if idx % max(1, int(TOTAL * FPS / 20)) == 0:
print(f"{100 * idx / (TOTAL * FPS):.0f}%", flush=True)
writer.close()-pix_fmt yuv420p is not optional — without it the file will not play in QuickTime,
PowerPoint, or most hardware media players, even though VLC handles it fine.
Iteration
After the first render, offer to tweak and accept plain-language feedback ("slower orbit", "bigger headline", "green instead of magenta"). Edit the script, re-render the affected scene as a preview PNG first, then re-render the video. Never re-render the full video to check a colour change.
Quality checklist before delivering
- Resolved a real TrueType font, not
load_default() - No text overflowing a card boundary or the canvas
- No label collisions in radial / orbit layouts
- All connectors drawn before all nodes (z-order)
- Readable contrast on every scene's preview PNG
- Loop point is seamless — last frame flows into first
- Encoded with
yuv420p; plays outside VLC - Reasonable file size (< 200 MB for ~120 s)
- Reported the absolute output path to the user
In this repository199 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- accessibility-passSkill
- acroform-writerSkill
- action-items-todoSkill
- agent-evaluation-designerSkill
- agent-harness-explorerSkill
- agent-performance-triageSkill
- agent-red-teamSkill
- ai-demo-assistantSkill
- ai-first-process-redesignSkill
- ai-usecase-assessmentSkill
- anonymised-case-study-writerSkill
- evidence-gatherSkill
- gap-checkSkill
- readiness-packSkill
- scope-mapSkill
- b2b-outreach-suiteSkill
- blog-content-auditorSkill
- blog-post-structure-passSkill
- brand-template-enforcerSkill
- brand-voice-passSkill
- breathing-roomSkill
- browser-uat-analystSkill
- business-osSkill
- call-for-speakers-digestSkill
- campaign-deck-builderSkill
- chart-builderSkill
- classic-text-adventureSkill
- clipchamp-videoSkill
- clt-hr-assistantSkill
- commenting-contentSkill
- competitive-battlecard-builderSkill
- conditional-chat-reminderSkill
- conference-session-abstract-packSkill
- contradiction-flagSkill
- insight-briefSkill
- provenance-checkSkill
- research-retrieveSkill
- trend-compareSkill
- content-quality-auditorSkill
- copilot-agent-advisorSkill
- copilot-studio-adaptive-card-builderSkill
- copilot-studio-agent-testSkill
- copilot-studio-harness-pickerSkill
- copilot-studio-knowledge-readinessSkill
- copilot-studio-mcp-readinessSkill
- copilot-studio-topic-blueprintSkill
- cowork-plugin-engineerSkill
- cowork-use-case-one-pagerSkill
- create-copilot-adoption-dashboardSkill
- context-assembleSkill
- handoff-packetSkill
- inquiry-intakeSkill
- knowledge-retrieveSkill
- resolution-draftSkill
- doc-format-converterSkill
- bom-impactSkill
- ecn-draftSkill
- ecr-ingestSkill
- standards-checkSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

