Youtube Producer logo

Youtube Producer

CommunityPopular
cbrock84
youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a topic and wants it turned into something publishable. For short-form and cross-platform video, use `video-content`.

Overview

Publishercbrock84
Repositoryheadcount
Skill nameyoutube-producer
Stars
2K
Forks
316
Bundled files
1
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.

  • 1 bundled files

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

  • Open source

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

Installation

Install the Youtube Producer 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/cbrock84/headcount/tree/main/plugins/marketing/skills/youtube-producer
  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/cbrock84/headcount.git /tmp/headcount
mkdir -p .claude/skills
cp -r /tmp/headcount/plugins/marketing/skills/youtube-producer .claude/skills/youtube-producer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Youtube Producer 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 Youtube Producer 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 Youtube Producer 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 producer

Package before you produce

Title and thumbnail decide whether a video is watched at all. Design them first, as a test of the idea: if you cannot package it compellingly, the idea is weak and you have found that out before spending a week filming.

Titles. Specific over clever. Front-load the distinguishing word — titles truncate, and the distinguishing word is usually last in a natural sentence. Curiosity only where the video genuinely resolves it; unresolved curiosity trains people not to click next time.

Thumbnails. One subject, readable at phone-thumbnail size. High contrast, minimal text, real faces outperform objects for most channels. Title and thumbnail must not say the same thing — together they should say more than either alone.

Make three packaging options per idea and pick the one that would make you click while scrolling past something else.

Idea selection

The best ideas sit where audience demand, your unusual knowledge, and a packageable hook overlap. Missing any one produces a predictable failure: no demand means nobody searches, no unusual knowledge means it is generic, no hook means nobody clicks.

Check what already exists on the topic. Not to avoid it — a crowded topic proves demand — but to find the angle nobody took.

The first thirty seconds

Deliver the promise immediately. No channel intro, no "before we get started," no restating the title. Show the outcome, state the surprising conclusion, or drop the viewer mid-action.

Then briefly say what the video covers, so the viewer knows the shape of the commitment they are making.

Retention structure

Retention is lost at seams, not in the middle of sections. Every transition needs an explicit reason to continue — an open question, a promised payoff, a stated next step.

  • Chapter it. Each section should work standalone and end pointing forward.
  • Vary pace deliberately. A uniformly intense video is as tiring as a flat one.
  • Front-load value. Withholding the good part until the end optimizes for a viewer who is no longer watching.
  • Place sponsor reads after the first payoff, never before it.

Visual direction and editing

Retention is as much editing as writing. The script sets what is said; the edit sets whether it is watched.

  • Cut on the beat of meaning, not on a timer. Rhythmic cutting for its own sake reads as noise.
  • Show, then say. Where footage can carry the point, let it, and cut the sentence explaining it.
  • B-roll earns its place by showing something the words cannot. Decorative b-roll is dead air with pictures.
  • Text on screen for anything numeric or named. Viewers do not retain spoken numbers.
  • Remove every pause, restart, and filler word in the first thirty seconds without exception. Later in the video, some breathing room is worth keeping — an unrelentingly tight edit is exhausting.
  • Change something visually at each chapter transition. Transitions are where viewers leave, and a visual change is a cheap reason to stay.

Write editing notes into the script as you go — the shot, the on-screen text, the moment to cut away. Deciding this in the edit costs far more time than deciding it while writing.

Diagnosing

  • Low click-through — packaging. Title and thumbnail, not content.
  • High click-through, immediate drop — the opening did not pay the promise, or the promise was unpayable.
  • Gradual decline — normal. Judge the slope against your own baseline, not against absolutes.
  • A sharp cliff mid-video — find the timestamp and watch it. Almost always a transition, a tangent, or a badly placed sponsor read.
  • Good retention, no growth — the videos work but the packaging is not earning impressions, or the topics have no audience beyond existing subscribers.

Channel level

Consistency of promise matters more than consistency of schedule. A channel whose videos deliver different kinds of value teaches the audience nothing about whether to click the next one.

Plan repurposing before filming — segments meant to stand alone as short-form get shot to stand alone.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Produce an idea whose title you cannot write. If the title is hard, the idea is not yet clear.
  • Judge a video on its first day. The signal that matters accrues over weeks.
  • Change what the channel is about because one video underperformed.
  • Fix retention by cutting faster when the problem is that the promise was wrong.

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 Youtube Producer AI skill do?

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a topic and wants it turned into something publishable. For short-form and cross-platform video, use `video-content`.

Why use Youtube Producer on TypingMind?

Because you install it once and use it with any model. Youtube Producer 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 Youtube Producer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/youtube-producer. 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 Youtube Producer?

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 Youtube Producer?

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

Is the Youtube Producer AI skill free?

Yes. It is published on GitHub by cbrock84 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 👇