yt-plan — Claude Code skill: planning and setup
yt-plan — a skill for Claude Code plans a week or month of YouTube uploads around available hours and work already in progress. It assigns formats and publishing days.
MIT 1,300 installs ★ 6,796 updated 2026-09-16
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-plan -a claude-codeWhat yt-plan does
yt-plan lays out a publishing calendar with one main video, a low-effort post drawn from existing material, and Shorts cut from the main video. Its table lists the day, format, working title, a one-sentence promise, and what is already prepared. It also estimates the hours required and names the first item to drop if the week falls apart.
The skill reads ~/.claude/youtube/voice.md when that file exists. Otherwise, it asks for three of the creator’s videos, infers a voice profile, and saves it there. Channel analytics determine the best day for the main upload; the skill does not publish anything. It does not make up figures, results, or sources.
What it helps with
- plan a week of YouTube uploads
- fit video work around available hours
- turn existing footage into short-form posts
- decide what to drop when a schedule slips
Example prompts for the agent
- Plan next week’s YouTube posts: I have five hours, and my camera setup video is half-finished.
- Build a monthly upload calendar and choose the main video’s day from my channel analytics.
- Split the main video into Shorts and tell me what to cut first if the schedule slips.
How to install yt-plan
1Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-plan -a claude-code2Manually: put the files in place
~/.claude/skills/yt-plan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/yt-plan/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-plan -a codex2Manually: put the files in place
.agents/skills/yt-plan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-plan -a cursor2Manually: put the files in place
.cursor/skills/yt-plan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/youtube-agent-skill skills/yt-plan2Manually: put the files in place
.github/skills/yt-plan/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-plan -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/youtube-agent-skill --path skills/yt-planManually: put the files in place
.devin/skills/yt-plan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-plan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about yt-plan
How do I install yt-plan in Claude Code?
Run npx skills add Jakeschincariol/youtube-agent-skill --skill yt-plan -a claude-code. The skill file is installed at ~/.claude/skills/yt-plan/SKILL.md.
What does yt-plan do?
It plans YouTube uploads for a week or month, factoring in available hours and existing work. The result is a table of formats, working titles, and estimated time; publishing remains manual.
Does yt-plan publish videos?
No. It prepares the schedule and gives the creator a block to copy; the creator publishes the videos.
Source text
SKILL.md · MIT
--- name: yt-plan description: >- 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". --- # 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 1. Read `~/.claude/youtube/voice.md` if 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. 2. 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-shorts` finds 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?**
© Jakeschincariol · MIT · Jakeschincariol/youtube-agent-skill