---
name: yt-content-planner
description: "Build a weekly YouTube upload plan: long-form vs YouTube Shorts mix, posting cadence, per-slot title and thumbnail pairing, hook angle, community-tab posts between uploads, and a goal balance across CTR, retention, and subscribes. Maps Shorts as top-of-funnel that points at long-form, and long-form as the loyalty and watch-time engine. Use to plan a week or a content calendar instead of shipping ad hoc. Not for writing a single title, description, or hook (use the dedicated yt skills)."
title: yt-content-planner
canonical_url: https://skilld.dev/gh/sergebulaev/youtube-skills/yt-content-planner
last_updated: 2026-10-29T10:46:08.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/example-week.md](https://skilld.dev/api/skills-raw/sergebulaev/youtube-skills/yt-content-planner/references/example-week.md), [references/pillars-framework.md](https://skilld.dev/api/skills-raw/sergebulaev/youtube-skills/yt-content-planner/references/pillars-framework.md).
>
> If the user asked to install this Skill, run `npx skilld install sergebulaev/youtube-skills/yt-content-planner`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/yt-content-planner`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/sergebulaev/youtube-skills/yt-content-planner) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/yt-content-planner`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/yt-content-planner --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/yt-content-planner --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# YouTube Content Planner

Turns a channel theme, an audience, and content pillars into a structured week:
what to upload, when, in which format, and how the title and thumbnail pair on
each slot. It plans; the dedicated skills write each piece.

## When to use

- User says "plan my week of YouTube content" or "build me a content calendar"
- User wants a long-form vs Shorts mix and a cadence they can hold
- User wants each slot pre-paired (format, title angle, thumbnail angle, hook)
- User wants the community-tab posts scheduled between uploads

## What it produces

- A **weekly grid**: each slot has a format (long-form or Short), a working title
  angle, a thumbnail angle, the hook formula, the pillar, and a posting window.
- A **long-form vs Shorts ratio** sized to the channel's stage and capacity.
- **Community posts** placed on the non-upload days to keep the channel warm.
- A **goal balance check**: across the week, are you spread across CTR-first,
  retention-first, and subscribe-first pieces, not all one note.

## Steps

1. **Gather inputs.** The channel theme/niche, the audience, 3 to 5 content
   pillars, the target audience timezone, how many videos per week the user can
   realistically make, and the current stage (new channel vs established). If a
   channel URL is given, parse it with `lib/url_parser.py` and ask the user to
   paste their recent titles and rough view counts.
2. **Set the mix.** Size the long-form vs Shorts ratio to capacity and stage. A
   common growing-channel rhythm is 1 long-form per week plus 3 to 5 Shorts, but
   consistency over 12 weeks beats volume. Confirm a cadence the user can hold.
3. **Assign pillars to slots** so the week is varied, not five takes on one
   topic.
4. **Pair each slot.** For every upload, set:
   - format (long-form or Short)
   - working title angle (which Y1-Y6 formula)
   - thumbnail angle (what it carries that the title does not)
   - opening hook formula (Y7-Y10), matched via the pairing table
   - primary goal (CTR / retention / subscribes)
   - posting window in the audience timezone
5. **Place community posts** on the non-upload days (a poll, a tease, a question).
6. **Run the goal balance check.** If every slot is CTR-bait or every slot is a
   deep tutorial, rebalance. Shorts skew top-of-funnel reach; long-form skews
   watch-time and loyalty. Make sure both jobs are covered.
7. **Hand each slot to the right skill.** The planner does not write the final
   title, description, hook, or thumbnail; it routes each slot to
   `yt-title-optimizer`, `yt-description-writer`, `yt-hook-scripter`, and
   `yt-thumbnail-brief`.
8. **Optional approval + schedule.** If the user has videos ready, each one
   publishes through its own skill via `lib.publish(...)`; the planner only sets
   the calendar.

## Hard rules

Global voice rules: see root `SKILL.md` Voice rules. Additional skill-specific
rules:

- Cadence must be one the user can hold for at least 12 weeks. Sustainable beats
  ambitious.
- Every upload slot is pre-paired: format, title angle, thumbnail angle, hook,
  goal, and time. No naked "post a video" slots.
- Shorts and long-form must have a through-line (Shorts point at the library),
  not two disconnected audiences.
- Spread the week across CTR, retention, and subscribe goals. Not all one note.
- Measure long-form watch-time and returning viewers separately from Shorts
  views. Do not let Shorts reach inflate the read on growth.

## Anti-patterns (skill will refuse)

- An over-ambitious cadence the user cannot sustain (daily long-form for a solo
  creator).
- Five slots that are all the same pillar and the same goal.
- Shorts with no connection to the long-form library.
- "Post more" as a plan, with no per-slot pairing.
- Em dashes above the cap (about one per 100 words) in any drafted title or hook line.

## Resources

- `../../references/algorithm-heuristics.md` - long-form vs Shorts strategy, timing, signals
- `../../references/hook-formulas.md` - title and hook formulas to assign per slot
- `references/pillars-framework.md` - turning a niche into pillars and a balanced mix
- `references/example-week.md` - a fully worked weekly grid

## Related skills

- `yt-title-optimizer` - write the title for each planned slot
- `yt-thumbnail-brief` - brief the thumbnail for each planned slot
- `yt-hook-scripter` - script the opening for each planned slot
- `yt-description-writer` - write the description for each planned slot
- `yt-community-post-writer` - the between-uploads community posts
