Yt Content Planner logo

Yt Content Planner

Community
sergebulaev
yt-content-planner

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).

Overview

Publishersergebulaev
Repositoryyoutube-skills
Skill nameyt-content-planner
Stars
85
Forks
21
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by sergebulaev on GitHub. Read the source before you install it.

Installation

Install the Yt Content Planner AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/sergebulaev/youtube-skills/tree/main/skills/yt-content-planner
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/sergebulaev/youtube-skills.git /tmp/youtube-skills
mkdir -p .claude/skills
cp -r /tmp/youtube-skills/skills/yt-content-planner .claude/skills/yt-content-planner
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Yt Content Planner in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Yt Content Planner on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Yt Content Planner is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Yt Content Planner AI skill do?

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).

Why use Yt Content Planner on TypingMind?

Because you install it once and use it with any model. Yt Content Planner is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Yt Content Planner in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/sergebulaev/youtube-skills/tree/main/skills/yt-content-planner. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Yt Content Planner?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Yt Content Planner?

As many as you like. As long as a model supports skills, you can use Yt Content Planner with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Yt Content Planner AI skill free?

Yes. It is published on GitHub by sergebulaev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇