Vox Editorial

vox-editorial

**A Claude Code skill that turns one researched topic into a finished vertical explainer film** — script, narration, cut-paper artwork, multiplane animation, captions and a music bed, assembled locally with ffmpeg.

Editorial register: it holds attention by being genuinely interesting, not by selling.

---

It made a video about me, which I am definitely not being weird about 😂

I pointed it at my own Twitter account and let it read my Highlights. It came back with a better summary of what I've been building than I'd have written myself, and then made a film out of it. Shameless self-promotion, but in my defence it was the machine's idea.


*Full film: [`docs/jc-builds.mp4`](docs/jc-builds.mp4) · 49s · that's me, [@jc_builds](https://twitter.com/jc_builds) 👋*

The opening line never says who it's about:

*"Turn on airplane mode and every AI app on your phone stops working. His keep going."*

That's the skill's hook rule at work — withhold the subject, open on a premise the viewer can verify from their own pocket, then break it and don't settle the debt until the final line. The question it owes is *how is that possible*, and the closing beat answers exactly that.

It found the through-line on its own, too: almost every "AI app" is a thin wrapper around someone else's server, and I keep shipping the opposite. The 4,096-token model planning a trip with no API calls, the coding agent that writes Swift on-device and repairs its own errors, the photo library matched against 164 landmarks. I didn't feed it any of that.

---

And here's one that isn't about me


*Full film: [`docs/tokyo.mp4`](docs/tokyo.mp4) · 29s*

Tokyo started as a fishing village called Edo. By 1720 it had a million people — the largest city on earth, bigger than London, bigger than Paris. And almost all of it was built of wood and paper. It burned down roughly every twenty years. Each time, they r