Upload Schedule Planner

Yt plan

by Jakeschincariol · MIT license · ★ 1,136 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".

---
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

Overview

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.

Manual install (npx, ZIP)

Claude Codenpx skills add Jakeschincariol/youtube-agent-skill --skill yt-plan -g -a claude-code

Claude Code (degit)npx degit Jakeschincariol/youtube-agent-skill/skills/yt-plan#main ~/.claude/skills/yt-plan

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.0 KB

Read SKILL.md here

Jakeschincariol/main1 file shown

SKILL.md2.0 KB

Browse every file on GitHub↗

SKILL.md

Show the full text47 lines

yt-plan/SKILL.md47 lines · 2.0 KB

PreviewCode

Outline

RawView on GitHub

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.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.
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?

1	---
2	name: yt-plan
3	description: >-
4	Plan a week or a month of YouTube uploads - what to post, when, and in
5	what order, sized to the creator's actual capacity. Use for "plan my
6	week", "content calendar", "what should I post", "I have no idea what to
7	make next".
8	---
9
10	# yt-plan
11
12	A plan that does not fit the week is a list of regrets. Ask two questions before writing anything:
13	how many hours do you actually have, and what is already half-made.
14
15	## Before you write
16
17	1. Read `~/.claude/youtube/voice.md` if it exists. That is the user's voice profile: how they talk
18	on camera, the words they never use, who they are talking to, what they will not claim. If it
19	does not exist, ask for three of their own videos, read or transcribe them, infer the voice,
20	and write the file. A script in the wrong voice is worse than no script, because they have to
21	read it out loud.
22	2. Never invent a number, a result or a source. If a figure would strengthen it and you do not have
23	one, ask for it or write the line without it.
24
25	## The shape of a week
26
27	- One anchor. The video the week is for. It gets the most time and it goes out on the day the
28	channel's own analytics say is best - ask for that, do not assume Tuesday.
29	- One cheap one. Built from something that exists: a clip, a reaction, a follow-up to the
30	comment that got the most replies last week.
31	- Shorts from the anchor. Three, cut from the long video, not written separately. `/yt-shorts`
32	finds them.
33
34	Three uploads on a seven-day week, not seven. A plan that posts daily is not a plan anyone
35	recognises, and the empty days are what make the filled ones survive a bad week.
36
37	## What to hand back
38
39	A table: day, format, working title, the one sentence it promises, and what already exists for it.
40	Then the honest line at the bottom - how many hours this costs, and what to drop first if the week
41	goes wrong.
42
43	## The gate
44
45	Nothing here publishes. This skill writes and you publish. Every output ends in a block the user
46	copies, and the last line of every run is the question: ship it, or change it?
47