yt-plan
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
SKILL.mdskills/yt-plan/SKILL.md
GitHubyt-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
- Read
~/.claude/youtube/voice.mdif it exists. If not, ask for three of the creator's videos and write it. - 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-shortsfinds 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?