agentleFS
Sign inStart free
uplikauplika/uplika-plugin/skills/yt-plan/SKILL.md

yt-plan

Skill3 starsChanged 34 days agoMITView on GitHub

Plan a week or month of YouTube uploads sized to the hours the creator has, then schedule them. For 'plan my week', content calendar, what to post.

5 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 1 is common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Never invent a number, a result or a source.

    line 15
  2. Very specific:

    If a call answers workspace_required, show the workspaces it lists, ask which one, and pass workspaceId on every call, publish included.

    line 23

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adapted from Jakeschincariol/youtube-agent-skill (MIT). Not affiliated with the original author.

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. Use it for "plan my week", "content calendar", "what should I post", "I have no idea what to make next".

Before you write

  1. Read ~/.uplika/<workspace-slug>/voice.md if it exists. That is the person'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, create it with the voice-profile skill; if they would rather not, ask its three questions (tone, ending style, words to avoid) and use the answers for this session.
  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.

With Uplika connected

  1. The rhythm so far. Find the YouTube account in list_accounts, then call list_channel_posts with its accountId: the timestamp of each video is the real upload rhythm, and get_insights on the recent ones shows which held views (null means not reported, not zero). The best day to post is in YouTube Studio's audience data, not in Uplika: ask the person for it rather than assume.
  2. Plan the week as below.
  3. Schedule, after the person approves the whole table. For each slot whose video file is ready, prepare it the way the yt-upload skill does (media id, options.youtube.title, privacy, the made-for-kids answer) and call publish with scheduledAt set to the slot's time with a time zone offset. Ask which time zone they mean; do not guess. Uplika keeps the video and uploads it at that time. Slots without a finished video stay in the plan and nothing is scheduled for them.
  4. Each publish answers with status scheduled and its time: show the person the list of what is booked.
  5. If a call answers workspace_required, show the workspaces it lists, ask which one, and pass workspaceId on every call, publish included. A channel that is not connected: https://uplika.com/dashboard/connections. Other errors: get_help with the code.
  6. youtube_quota_exhausted from list_channel_posts, or noteCode youtube_quota_exhausted from get_insights: Uplika's daily YouTube limit, which everyone on Uplika shares, ran out: stop and do not repeat the call, tell the person when it refills (resetsAt, or the time in the message), and do not ask them to reconnect, because it is not their account (faq:youtube-daily-limit). A booked upload that comes due on such a day ends with youtube_daily_cap and is not sent; it goes again only when someone sends it after that time.

Without Uplika

The person tells you their upload rhythm and their best day from YouTube Studio, and schedules the uploads in Studio themselves.

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 is scheduled until the person approves the table. Every output ends in a block they can copy, and the last line of every run is the question: ship it, or change it? With Uplika connected, "ship it" means you schedule the ready videos with publish.

Tools

  • list_accounts: the YouTube account id
  • list_channel_posts: upload dates of the recent videos, the real rhythm
  • get_insights: views and likes of recent videos
  • publish: schedule a ready video with scheduledAt, after approval
  • get_help: the answer for an error code

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free