agentleFS
Sign inStart free
utillayerutillayer/youtube-agent-skill/skills/yt-plan/SKILL.md

yt-plan

Skill10 starsChanged 29 days agoMITView on GitHub

Plan the coming week or month of uploads - what, when and in what order - sized to the time the creator really has. Use for "plan my week", "content calendar", "what should I post", "I don't know what to make next".

5 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ~/.claude/youtube/voice.md if it exists.

    line 16
  2. Distinctive:

    Never make up a number. Ask for the channel's best upload day.

    line 18
  3. Very specific:

    If a video retells a source, the plan includes the research day: /yt-research before /yt-script.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

yt-plan

A plan that does not fit the week becomes a list of guilt. Before writing anything, ask two questions: how many hours do you actually have, and what is already half-done.

Before you start

  1. Read ~/.claude/youtube/voice.md if it exists. If not, ask for three of the creator's videos and write it.
  2. Never make up a number. Ask for the channel's best upload day; do not assume one.

The shape of a week

  • One main video. The one the week is for. It gets most of the time and goes out on the day the channel's own analytics say is best.
  • One quick one, built from something that exists: a clip, a reply to the most-discussed comment, a follow-up.
  • Shorts cut from the main video, not written separately. /yt-shorts finds them.

Two or three uploads a week, not seven. The quiet days are what let the busy ones survive a bad week. For a story or history channel, a standalone video a week often beats a numbered series: each one can be anyone's first, and numbered parts tend to lose viewers part by part.

If a video retells a source, the plan includes the research day: /yt-research before /yt-script.

What to hand back

A table: day, format, working title, the one-sentence promise, and what already exists for it. Then the honest line underneath: how many hours it costs, and what to drop first if the week goes wrong.

Before you hand it over

This skill drafts; you publish. End with the copy-ready block and one question: post it as is, or another pass?

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.

Check your setup, free