Repository navigation
v0.1.0 — video pipeline, 6 voice providers, stock media
First tagged release. The kit now goes from a topic to a published 9:16 video without
leaving the repo.
Sample output
claude-fable-5-sample-1080x1920.mp4 — 2 min 12 s, 1080×1920, real Vbee narration,
stock B-roll from Pexels and a live screenshot of the source page. 15 scenes.
It is attached here rather than committed because it is 16 MB. Everything needed to
regenerate it byte-for-byte is in the repo at
examples/ai-video-social/sample-output/:
script.json, media-lock.json (which pins the exact stock clips) and script.txt.
node scripts/video/render.mjs examples/ai-video-social/sample-output/script.jsonclaude-fable-5-sample-voice.mp3 — the narration track on its own, for CapCut.
There is a matching written article from the same source in
examples/ai-news-social/sample-output/
— one source, two formats, which is the point of the kit.
What's in this release
- Video pipeline ported to dependency-free
.mjs: validate → TTS → SFX → resolve media → render → mux - Six voice providers (
omnivoice,elevenlabs,vbee,fptai,viettel, plus a generichttpadapter). Only the local one needs a server - Stock B-roll from Pexels and Pixabay, web screenshots via headless Chrome, uploads to R2 / Cloudinary
- 14 video templates, plus a fetcher for the 146 in the upstream HyperFrames registry
contact-sheet.mjs— one labelled frame per scene, because four real defects shipped that no validator rule could catch- Multi-platform posting through one Make.com webhook
Known limits, stated plainly
- R2, Cloudinary and Viettel AI adapters are
UNVERIFIED— written from official docs, never run against real credentials. They say so themselves inhost-check.mjs --hostsandtts-check.mjs --providers. The R2 SigV4 signer is verified against AWS's published test vector. - Rendering needs a real machine — FFmpeg, Chrome, and a voice. GitHub Actions cannot do it.
- CI does not install crawl4ai; it only compiles
crawl.py.