Design and run an episodic social video series: pick a series promise, structure episodes for retention, write hooks and episode-ending bridges, and measure whether viewers come back. Triggers on requests to start a video series, plan episodes, grow returning viewers, or fix a series that keeps losing its audience.
./install.sh social-video-seriesname: social_video_series description: Design and run an episodic social video series: pick a series promise, structure episodes for retention, write hooks and episode-ending bridges, and measure whether viewers come back. Triggers on requests to start a video series, plan episodes, grow returning viewers, or fix a series that keeps losing its audience.
Turn one-off videos into a series people follow. This skill covers the format design: what the series promises, how each episode is built, how episodes connect, and how you know the series is working. It is platform-neutral with notes on the native series features in YouTube and TikTok (see references/platform-series-features.md).
Pick one recurring viewer need, not a topic category. "Fixing common indoor portrait lighting problems" works; "weekly videos about photography" does not. Write one sentence stating what every episode delivers:
> "In every episode, I take one weak product page and show how I would improve its copy."
That sentence is your filter. An episode idea that fails the promise does not belong in this series. Draft 5-8 episode ideas that satisfy it before producing anything.
Give every episode the same 3-4 structural landmarks so returning viewers know where they are, without making scripts identical. A useful template:
Check the platform's retention report per episode. The steepest drop usually lands in the first 30 seconds (YouTube labels this "Intro" in key moments). If a recurring section consistently loses viewers, cut it, don't keep it for branding.
The hook's job: confirm "this is for you" in the first seconds and leave one thing unresolved. Use one of these patterns:
Rules: the question must be answerable by the video. A loop the episode never closes buys one view and loses the follow. Never open with a logo animation, a slow pan, or "hey guys, welcome back." These read as filler instantly.
Retention across episodes comes from the bridge, the last 10-15 seconds that give a viewer a reason to watch the next one. Three kinds that work:
Do the bridge in the edit and on the platform: end screens on YouTube, pinned comments and captions like "Part 1" / "Episode 2" / "Day 5", and series hashtags for discovery (see references/platform-series-features.md).
Use a consistent title format, one recurring intro sound or phrase, and the same shooting setup across episodes. Visual consistency builds trust and tells a new viewer they have landed mid-series. Recognizable does not mean identical: vary thumbnails and framing so the feed doesn't look like a wallpaper of the same shot.
One page that holds: the promise, the audience, the episode structure, the hook patterns you will rotate, the bridge style, the publishing cadence, and the kill criteria (when to end or reboot the series). A worked example is in references/episode-blueprint.md. For story-driven series, also note characters, the season arc, and cliffhanger rules. Keep it short enough to actually consult.
Plan 8-12 episodes as the test season. Publish on a fixed cadence so viewers learn when to expect you. Then measure series health, not just views:
Expand only the episodes and bridges that move viewers forward. When flow stalls across two or three episodes, revisit step 1, the promise may be drifting.
Deliver, in order: (1) the one-sentence series promise; (2) 5-8 episode ideas that satisfy it; (3) the episode structure with hook pattern and bridge type chosen per episode; (4) the series bible (one page); (5) a publishing cadence; (6) the measurement plan naming the exact metrics from step 7. The whole package fits in a single message or a short doc, and every recommendation names which episode or metric it applies to.
publisher key 2e43c913833850e6d80f939677e3de76e806d47785c0f1caaca90f9d18c98e1e
No ratings yet — be the first to rate it.