autoproducelisted

Runs one topic all the way to shipped files with no human gate — the unattended twin of storyboard plus produce. Use when the user asks to "이 주제로 영상 하나 만들어", "주제만 주면 영상까지 만들어줘", "자동으로 쇼츠 만들어", "make a short about X end to end", or when a growth loop needs to refill its publish queue by itself. Researches, writes 3 seven-item scenario candidates and has them judged in one batched reviewer read, authors scenes.js, loops the narration alone to 95 on content and then on wording (three reads each, handed inline), generates 9:16 backgrounds, synthesizes narration, and builds the video plus per-platform text under data/[channel]/episodes/[topic]/output/. Machine gates replace human approval: facts, the batched scenario read, the two narration loops, the style and contract checkers, build report, one content-reviewer read at 95 with zero P0, and a cost cap. Boundary — storyboard plans and stops, produce builds an approved episode, autoproduce does both without stopping.
ttalkkaklab/social-flow · ★ 0 · Data & Documents · score 73

Install: claude install-skill ttalkkaklab/social-flow

# From one topic to a finished video — unattended authoring For pending portal render requests, follow [the six-ratio allocation contract](../storyboard/references/production-mode.md): `portal_render_allocation` read → host LLM reasons over every shot → submit requestId/baseRevisionNo and all assignments → pull. New choices persist `PRODUCTION.renderRatioVersion:1`; neither a pending request nor ratio selection approves spending. Read [story-quality.md](../storyboard/references/story-quality.md) before candidate writing, including skip-research channels. It overrides mandatory closing questions and modern parallels. Write STORY with the story pass; use gate 6f's existing narration read for the four quoted findings. After vocabulary edits revalidate and run `check-story.js storyboard/` before any generation. Missing, failed or stale reviews stop production with queue hold, not merely publication. A closing beat may have `cta:"none"`. An ask stays optional; a forwardable thing does not — an ask requests behaviour from the viewer, while a forwardable thing is one sentence, figure or verdict they can pass on as-is. Asking to be shared is an ask, not a trigger. Runs `storyboard → produce` end to end without human approval. The input is a single topic string; the output is a publishable `output/` set. **This does not replace those two skills.** Contracts, templates, and builders are all used as-is from them — this document decides only two things: **who judges when no human is pr