yt-plan
Skill1 starsChanged 37 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
- nessalazne/youtube-agent-skilledited, first seen Sep 23, 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★ 4729% same
- utillayer/youtube-agent-skill★ 1012% same
- nessalazne/youtube-agent-skill★ 527% same
- uplika/uplika-plugin★ 311% same
- swayamdhawan/youtube-agent★ 029% 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 repository25 other files it gives its agents.
- openai/AGENTS.mdAGENTS.md
- llms.txtllms.txt
- yt-analyticsSkill
- yt-auditSkill
- yt-briefSkill
- yt-chaptersSkill
- yt-collabSkill
- yt-commentSkill
- yt-editSkill
- yt-endscreenSkill
- yt-funnelSkill
- yt-ideaSkill
- yt-packageSkill
- yt-repurposeSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-seriesSkill
- yt-shortsSkill
- ytSkill
- yt-sponsorSkill
- yt-thumbnailSkill
- yt-trendSkill
- yt-viralSkill
- yt-voiceSkill
The file
We split this skill into the rules it gives an agent
4 rules. 1 is common, 2 are distinctive, and 1 is very specific to this project.
1
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
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
- Distinctive: line 12
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
- Very specific: line 20
Use the creator's supplied voice profile or context, then a local ~/.claude/youtube/voice.md if available, following the operating guide.
- Common: line 23
Never invent a number, a result or a source.
- Distinctive: line 34
Use the channel's own audience and performance evidence for timing.
“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
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
Build around the user's requested cadence, format, timezone, available hours, and material already made. Use known context; ask only for missing constraints that change the plan.
Before you write
- Use the creator's supplied voice profile or context, then a local
~/.claude/youtube/voice.mdif available, following the operating guide. If absent, draft in a clear voice using the stated audience and format; do not make voice-profile setup a prerequisite. - 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.
Size the plan to the creator
For a mixed-format channel, an anchor video, a lower-effort follow-up, and selected Shorts from existing footage can be a useful starting mix. Use /youtube-agent-pro:yt-shorts for clip plans. For a Shorts-only channel, plan standalone Shorts without requiring a long-form anchor. Honor a requested daily or other cadence when capacity supports it; if it does not, name the tradeoff instead of silently changing the user's schedule.
Use the channel's own audience and performance evidence for timing. If none is available, label a proposed time as a test, not a universal best time. Keep dates and timezones explicit. This is a calendar draft unless the user separately requests scheduling through an available account tool.
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.
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.