Video Content logo

Video Content

CommunityPopular
cbrock84
video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

Overview

Publishercbrock84
Repositoryheadcount
Skill namevideo-content
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 Video Content 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/video-content
  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/video-content .claude/skills/video-content
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Video Content 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 Video Content 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 Video Content 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.

Video content

This covers video as a format across platforms — short-form, long-form, and the packaging that decides whether either gets watched. youtube-producer covers one platform in depth: channel strategy, idea selection against a channel's history, and retention teardowns against YouTube's own curves. When the question is about a channel rather than a video, it belongs there.

Packaging is most of the outcome

A video nobody clicks has no retention curve. Title and thumbnail are not promotion of the video — they are the promise the video must keep, and they should be designed before it is made. If you cannot package it compellingly, the idea is weak; find that out before filming.

Titles — specific over clever. Curiosity that a real answer resolves, not a withheld one. Front-load the distinguishing word, since titles truncate.

Thumbnails — one subject, readable at thumbnail size on a phone. High contrast. Text under about four words, or none. Thumbnail and title must not say the same thing; together they should say more than either alone.

Openings

The first fifteen seconds decide the rest. Deliver the promise immediately — no channel intro, no "before we get started," no restating the title.

Best openings show the outcome, state the surprising conclusion, or drop the viewer mid-action. Then say what the video will cover, briefly, so they know the shape of the commitment.

Structure by length

Short-form — one idea, opening frame that reads as motion, and a payoff before attention decays. No setup. The loop matters: end where the beginning makes sense again.

Long-form — chapters that each work standalone, with an explicit reason to continue at every seam. Retention is lost at transitions, not in the middle of sections. Vary pace deliberately; a uniformly intense video is as tiring as a flat one.

Diagnosing underperformance

  • Low click-through — packaging problem. Title and thumbnail, not content.
  • High click-through, early drop — the opening did not pay the promise. Or the promise was unpayable.
  • Steady mid-video decline — normal. Look at the slope against your own baseline, not absolutes.
  • Sharp mid-video cliff — find the timestamp and watch it. It is almost always a transition, a tangent, or a sponsor read placed badly.

Repurposing

Plan derivatives before filming, not after. Segments intended to stand alone get shot to stand alone. Extracting short-form from a video not built for it produces clips that need context they do not have.

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.

Tooling

Editing: DaVinci Resolve, Adobe Premiere Pro, Final Cut Pro, CapCut, and similar; Descript for transcript-driven editing, which is faster for talking-head and interview formats than a timeline.

Recording remote: Riverside, Zoom, StreamYard, and similar — record local tracks per participant where the tool supports it, because the connection quality on the day decides the ceiling otherwise.

Repurposing and captions: Opus Clip, Submagic, and similar. Burned-in captions are not optional; most viewing is silent, and the caption is the packaging on every platform that autoplays.

Never

  • Produce before the title and thumbnail exist. Packaging decides whether anything you shot gets seen.
  • Open with a preamble. The first seconds are where an audience is lost, not where it is warmed up.
  • Diagnose a video on view count alone. Impressions, click-through, and retention fail differently and need different fixes.

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 Video Content AI skill do?

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

Why use Video Content on TypingMind?

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

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

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 Video Content?

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

Is the Video Content 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 👇