AI automation
Otto Content: a video pipeline as code
The system we edit our YouTube videos with: research, script, storyboard, edit, and package, all driven from one repo with a code-based motion engine.
The problem
Content dies from friction. Every video meant juggling research tabs, script docs, an editing timeline, and packaging checklists across five different tools.
The result was slower output and a look that drifted from video to video.
What we built
Otto Content runs the pipeline end to end: niche research over real channel data, scripting, storyboarding, then editing through an HTML/CSS motion engine, with packaging at the end.
The method already edits the videos on our channel, and the whole system installs into any repo as a plugin.
The result
The edit lives in a repo, not a timeline
7
pipeline stages, idea to publish
1
repo to run it all from