agentleFS
aya-talebaya-taleb/multimedia-skills/skills/youtube-plan/SKILL.md

youtube-plan

Skill1 starsChanged 22 days agoMITView on GitHub

Build a YouTube plan a busy founder can actually keep: works out a pace from the hours they really have, then lays out the next 4 to 8 weeks of videos with working titles, the viewer question each answers, the format, the Shorts to cut from each, and how each video leads back to the business. No promised views. Use it for "plan my YouTube channel", "what videos should I make", "YouTube content calendar", "how often should I post on YouTube", "video ideas for my business", "I want to start a YouTube channel for my startup", or after youtube-audit when the plan needs to change.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use weeks (week 1, week 3), not calendar dates, unless the user gave a start date.

    line 59
  2. Distinctive:

    If you must ask questions first, still write a draft plan file with your assumptions marked, so the user has something to react to.

    line 62
  3. Distinctive:

    After 4 weeks, look at: which videos got the most views per impression and the longest watch, which questions came up in comments, and …

    line 77
  4. Very specific:

    Write media/youtube/plan-<yyyy-mm>.md: the pace math, the calendar table, the 4-week check, and a one-line "if you only do one thing" for …

    line 84
  5. Distinctive:

    Start from real hours. Show the math.

    line 91
  6. Distinctive:

    No promised views, subscribers or revenue.

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

youtube-plan

Most founder channels stop in week three because the plan assumed time nobody had. This skill starts from the hours, then fills the calendar with videos the founder's buyers are already asking about.

What this skill reads and writes

  • Reads: the founder-context business file (who they serve, goals, topics, proof, tone, off-limits). The latest media/youtube/audit-*.md if youtube-audit ran. Any idea list the user has.
  • Writes: media/youtube/plan-<yyyy-mm>.md.
  • Next: the linked yt-script skill to script the first video, youtube-seo before each upload, youtube-shorts after each long video.

1. Ask what is real (one batch of questions)

Skip anything the business file or the user already said:

  • Hours per week for YouTube, all in (planning, filming, editing, uploading).
  • Format they can make: talking head, screen recording, podcast or interview, a mix.
  • Who does the editing: them, a tool, an editor.
  • What the channel is for: leads, trust before a sales call, hiring, a launch.
  • Videos already made, and any ideas they want in.

2. Work out the pace, and show the math

Rough hours per finished long video, as a starting point to adjust with the founder:

formatfirst videosonce practiced
screen recording tutorial4 to 6 h2 to 3 h
talking head, light edit5 to 8 h3 to 4 h
interview or podcast6 to 10 h (with guest prep)4 to 6 h

These are planning guesses, not measured facts. Say so, and ask how long their last video took if they made one. Cutting 2 to 3 Shorts from a finished long video adds about an hour.

Pace = hours per week / hours per video. Round down. One good video every two weeks that keeps going beats a weekly plan that stops. Show the sum.

3. Fill the calendar

Draw ideas from the business file's topics and the buyer's real questions (from sales calls, comments, support, the audit's stand-outs). Ask for those questions if you have none. If you draft questions yourself, label them "likely question, check with buyers", never as quotes. Use weeks (week 1, week 3), not calendar dates, unless the user gave a start date. Do not name product features or past events the business file does not mention.

If you must ask questions first, still write a draft plan file with your assumptions marked, so the user has something to react to. For a founder channel, a good mix over a month is:

  • Mostly "how to" or "how I" videos that answer a question the buyer would search.
  • One video with the founder's point of view or a story from building the business.
  • Shorts cut from each long video.

For each video: week, working title (plain and specific), the viewer question it answers, format, rough length, the Shorts it can yield, and the next step it points to (a product page, email list, booking a call). Keep titles honest. Ideas that need proof the founder lacks (a case study with numbers) go in as "needs: {{the real number}}" or wait until they have it.

4. Decide what to check

After 4 weeks, look at: which videos got the most views per impression and the longest watch, which questions came up in comments, and whether any viewers took the next step. Name these in the plan, with "run youtube-audit" as the check. Do not set view or subscriber targets you cannot ground in their own past numbers.

5. Write and hand back

Write media/youtube/plan-<yyyy-mm>.md: the pace math, the calendar table, the 4-week check, and a one-line "if you only do one thing" for weeks when time runs out. Show the calendar and end with one line naming the next step, usually scripting video 1 with the linked yt-script skill. Nothing gets scheduled or uploaded by this skill.

Rules

  • Start from real hours. Show the math.
  • Ideas come from the founder's topics and buyers, not generic trends.
  • No promised views, subscribers or revenue.
  • Off-limits topics stay off the calendar.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.