← ClaudeAtlas

grow-youtubelisted

Runs one autonomous YouTube Shorts growth tick — reply, measure, refill, publish, then watch what spreads. Use when the user asks to "유튜브 키워", "쇼츠 성장 루프", "유튜브 성장 틱", "grow the YouTube channel", or wants the growth loop running. One tick replies to inbox comments (golden hour first), snapshots channel and video analytics, refills the publish queue by authoring a new short end to end through autoproduce when it runs dry, publishes queue-marked videos in the plan's slots, and samples a fresh video's live view counter to see whether it is breaking out — all inside the standing authorization in data/[channel]/growth/youtube/growth-plan.md. Recur with /loop [interval] /social-flow:grow-youtube [channel]. First run needs the init argument.
ttalkkaklab/social-flow · ★ 0 · AI & Automation · score 75
Install: claude install-skill ttalkkaklab/social-flow
# YouTube growth loop — one autonomous tick Growth skills are **split per platform** (same skeleton as grow-threads: plan = standing authorization · tick ≠ publish · idempotent state). State paths are scoped under `growth/youtube/`. ``` /social-flow:grow-youtube <channel> init # once — fix the plan (HITL) /loop 1h /social-flow:grow-youtube <channel> # resting cadence /loop 15m /social-flow:grow-youtube <channel> # while a fresh video is under watch (§2b) ``` **One difference from Threads sets this skill's structure** — a Short is a video. Making one takes research, authoring, images, voice, and a build. So publishing happens **only from the queue**, and what enters the queue is the crux of this loop. There are two ways to fill it. - **A human fills it** — build with `/social-flow:storyboard → produce` and stamp `queue: ready` in storyboard.md. - **The loop fills it** — with plan `autoproduce.enabled: true`, the moment the queue runs dry the tick builds an episode itself and stamps the marker (§2.5). Topics, subject scope, and the per-episode cost cap are all written in the plan, and only episodes that pass the machine gates enter the queue. **Hourly is the resting cadence** — slot publishing and comment replies both live fine at that resolution, and authoring only happens when the queue is empty anyway. **The velocity watch is the one thing that hourly can't hold.** The tick samples a video's view counter only as often as the tick runs, so a watch left o