About yt-plan
yt-plan is a YouTube publishing-week planning skill for creators. It accounts for available hours, existing work, channel voice, and analytics to produce a schedule with priorities and fallback cuts.
Key features
- 01Checks available work hours
- 02Accounts for existing drafts
- 03Uses a voice profile
- 04Plans an anchor and a smaller video
- 05Derives Shorts from the anchor
- 06Estimates effort and fallback cuts
Use cases
- 01Planning a realistic upload week
- 02Scheduling around partially made videos
- 03Adapting a plan to channel voice
- 04Deciding what to drop when time runs short
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/yt-planin Claude Code to confirm it loaded.
Details
From the project READMEyt-plan
A plan that does not fit the week is a list of regrets. Ask two questions before writing anything: how many hours do you actually have, and what is already half-made.
Before you write
- Read
~/.claude/youtube/voice.mdif it exists. That is the user's voice profile: how they talk on camera, the words they never use, who they are talking to, what they will not claim. If it does not exist, ask for three of their own videos, read or transcribe them, infer the voice, and write the file. A script in the wrong voice is worse than no script, because they have to read it out loud. - Never invent a number, a result or a source. If a figure would strengthen it and you do not have one, ask for it or write the line without it.
The shape of a week
- One anchor. The video the week is for. It gets the most time and it goes out on the day the channel's own analytics say is best - ask for that, do not assume Tuesday.
- One cheap one. Built from something that exists: a clip, a reaction, a follow-up to the comment that got the most replies last week.
- Shorts from the anchor. Three, cut from the long video, not written separately.
/yt-shortsfinds them.
Three uploads on a seven-day week, not seven. A plan that posts daily is not a plan anyone recognises, and the empty days are what make the filled ones survive a bad week.
What to hand back
A table: day, format, working title, the one sentence it promises, and what already exists for it. Then the honest line at the bottom - how many hours this costs, and what to drop first if the week goes wrong.
The gate
Nothing here publishes. This skill writes and you publish. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?