youtube-content-calendar
Skill1 starsChanged 47 days agoMITView on GitHub
Plan 1–4 weeks of YouTube videos and Shorts from the user's goals and content pillars, or by repurposing a blog post, video or transcript, draft the title and description for each slot, and schedule them with the PostOnce YouTube MCP once the videos exist. Use when the user asks for a YouTube content calendar, a YouTube upload schedule, YouTube video ideas, or to plan or repurpose content for YouTube.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 24
Use the user's own best times if they know them.
- Very specific: line 41
When a video file is ready (one file, up to 768 MB.
- Very specific: line 42
Call get_post to confirm each one is scheduled, and report the list back.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YouTube content calendar
Plan a realistic run of uploads, draft each one, and schedule them through PostOnce as the videos get made. Every YouTube post needs a video, so the calendar has two stages: plan and draft now, schedule when each file exists.
Before planning
Get or infer: the channel's goal (search traffic, subscribers, leads, sales), the audience, 2–4 content pillars, how many long videos and Shorts they can actually produce per week, the timezone, and what's already made. If they give a source (blog URL, long video, transcript, notes), plan from it first. Never invent results, guests or events.
Building the plan
- Cadence they can keep beats an ambitious one. One long video a week plus a few Shorts is a strong plan for most solo creators.
- Long videos: one searchable topic each. Write the keyword first, then the angle.
- Shorts: cut from the week's long video where possible (self-contained moments), plus a few standalone ideas. Vertical, up to 3 minutes.
- Rotate pillars so no week is all one topic.
- Repurposing: one long video can feed several Shorts, and each Short can go to TikTok, Instagram Reels and Facebook in the same
create_post. - Use the user's own best times if they know them; otherwise pick consistent days and times and say it's a starting point.
Each slot
| Field | Content |
| Date and time | With timezone |
| Format | Long video or Short |
| Pillar and keyword | One each |
| Title | Under 60 characters (youtube-title-generator rules) |
| Description | First two lines with the keyword, links, 3–5 hashtags (youtube-description-generator rules) |
| Privacy | public unless the user says unlisted or private |
| Production note | Script, thumbnail idea, and what footage it needs |
Scheduling through PostOnce
- On approval, save slots without a finished video as drafts with
create_draft(the title on the first line, then the description), so nothing is lost. - When a video file is ready (one file, up to 768 MB; MP4, MOV or WebM through
create_upload_url), upload it and callcreate_postwithpublish_atfor that slot, the video inmedia, andplatform_optionstitle,description,privacyand, if relevant,categoryIdandai_generated. - Call
get_postto confirm each one is scheduled, and report the list back.
PostOnce uploads the video at the scheduled time; it doesn't use YouTube's own scheduled-publish setting. Scheduled posts can be changed with update_post or cancelled with cancel_post before they run. Custom thumbnails are uploaded in YouTube Studio after the video is live.
Output
Return the calendar as a table (one row per slot), then the full title and description for each slot. Ask for approval, then confirm the channel and timezone before creating drafts or scheduled posts with the postonce skill.
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.

