yt-plan
Skill5 starsChanged 52 days agoMITView on GitHub
Plan a week or a month of YouTube uploads - what to post, when, and in what order, sized to the creator's actual capacity. Use for "plan my week", "content calendar", "what should I post", "I have no idea what to make next".
5 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- utillayer/youtube-agent-skilledited, first seen Nov 8, 2026
- uplika/uplika-pluginedited, first seen Oct 25, 2026
- swayamdhawan/youtube-agentedited, first seen Oct 15, 2026
- ahmedsakri/youtube-agent-proedited, first seen Oct 15, 2026
- Jakeschincariol/youtube-agent-skilledited, first seen Sep 16, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- Jakeschincariol/youtube-agent-skill★ 4797% same
- utillayer/youtube-agent-skill★ 1025% same
- uplika/uplika-plugin★ 335% same
- ahmedsakri/youtube-agent-pro★ 132% same
- swayamdhawan/youtube-agent★ 097% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- yt-auditSkill
- yt-chaptersSkill
- yt-commentSkill
- yt-editSkill
- yt-packageSkill
- yt-publishSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-shortsSkill
- yt-viralSkill
The file
We split this skill into the rules it gives an agent
3 rules. 1 is common, 0 are distinctive, and 2 are very specific to this project.
1
Common
Most of the 5 edited versions we read keep these.
0
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
- Very specific: line 17
Read ~/.claude/youtube/voice.md if it exists.
- Common: line 22
Never invent a number, a result or a source.
- Very specific: line 48
If they want it on the channel, /yt-publish is the only skill in this pack that touches YouTube, it uploads private unless they say …
“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.
Files
yt-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
This skill never publishes. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?
If they want it on the channel, /yt-publish is the only skill in this pack that touches YouTube,
it uploads private unless they say otherwise, and it asks again before it does anything.
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
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.