BUILDERLOG · CHANNEL AUTOMATION PACK 02
YouTube Shorts Pack — an unattended Shorts factory
Fills 2–6 slots a day per channel with nobody watching. Topics come from a public Shorts search benchmark and a policy-news radar; the script goes codex → claude → gemini → local, one call each. Before any TTS spend a gate checks the script (5–7 items ≤ 26 chars, narration ≤ 320 chars, every number must appear in a fetched source quote). After render it checks 1080×1920, duration and stray preview audio, then schedules the upload in Studio.
₩990 · Single-user license · unlimited channels
Pipeline
6 slots (05:00–18:00) supervisor: worker lock, 2300 s deadline, resource check → next-slot → pick format (list / narrated, narrated daily cap) → benchmark every 20 h · radar · one local summary a day · feedback from top-retention hooks → script.json (engine chain; local ⇒ review_required + NO_UPLOAD) → pre-production gate → make (ElevenLabs + Edge fallback, images Gemini → Pexels → local, motion / list-card / CSS templates / Remotion, ffmpeg) → QA → scheduled Studio upload (logged-in profile) → ledger → 03:05 · 14:30 analytics CSV → feedback, design 50:50 → 75:25, portfolio → 23:20 retro · 23:35 report · Monday 04:00 weekly trends (yt-dlp frames + whisper + local VL)
What's inside
- bin/ auto-short.sh (supervisor), shorts_control.py (lock, deadline, slot, format, context, generate, checkpoints), gate.py (all rules), make.py (TTS, images, render, QA), ledger.py, performance.py (CSV → feedback, design policy), retro.py, Studio upload recipe, shared router, guard, local agent
- prompts/ list script, narrated script, context summary, feedback, retro judgement
- config/ channel (slots, caps, duration range, bench queries), automation (timeouts, engine order, prompt cap), design-policy (50:50 → 75:25 conditions), portfolio-policy, theme
- jobs/ main and second channel, health (10 min), recovery (hourly), performance, retro, report, weekly, with the real cron strings
- skills/ shorts-pipeline-build · shorts-run-today · shorts-report-review · studio-upload-aside
Human steps
- Check the numbers in any local-written script before upload
- Approve design and format changes (the policy file only shifts traffic)
- Log in to the browser profile; request the API audit if you want API uploads
Where it comes from
This is the exact channel operation Builderlog runs unattended every day, with account and channel details removed. Not a tutorial: the scripts, schedules, gates, prompts and human checklist of a pipeline in production. The shared parts (engine router, resource guard, local agent) are identical across the three packs.
Requirements
- macOS or Linux, Python 3.11, uv, ffmpeg
- At least one of Claude Code, Codex, Gemini CLI (the router tries them in order); Ollama as the local fallback
- A logged-in browser automation (Aside CLI recommended) for platform screens
- Scheduler: dagu (recommended), or launchd, cron, GitHub Actions
What it will not do
- Log in or pass verification for you (you log in once)
- Auto-publish core content written only by the local model (always held for a human)
- Work around platform policy. Quotas, reviews and copyright are listed as human steps in the README
Pairs with
Automation Kit (hooks, MCP, deploy guard) and Prompt Dex Skills (content prompts) complete the chain: build → content → operate. All ₩990.