agentleFS
postoncehqpostoncehq/youtube-mcp/skills/youtube-shorts-script/SKILL.md

youtube-shorts-script

Skill1 starsChanged 47 days agoMITView on GitHub

Write YouTube Shorts scripts for vertical videos up to 3 minutes, with a hook in the first second, a loopable ending, and the Short's title and description, ready to publish with the PostOnce YouTube MCP. Use when the user asks for a Shorts script, YouTube Shorts ideas, a script for a vertical video, or to cut a long video or article into Shorts.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write one script per Short.

    line 11
  2. Distinctive:

    Start mid-action. No intro, no "in this video".

    line 32
  3. Distinctive:

    No CTA that pauses the video.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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

YouTube Shorts script

Write one script per Short. If the user wants several (for example from one long video), write each as its own Short with its own hook.

Before writing

Get or infer: the one idea, who it's for, the format (talking head, screen recording, voiceover on B-roll, text on screen), target length, and any source to cut from. From a long video or transcript, pick self-contained moments that make sense with no context. Never invent facts, results or stories.

Format facts

  • Shorts are vertical (9:16, 1080×1920 works) and up to 3 minutes. Most land best well under a minute; only go longer when the content earns it.
  • PostOnce treats portrait videos as Shorts; YouTube classifies the final format from the video itself. #shorts is optional.
  • One video per post, up to 768 MB, MP4, MOV or WebM.

Structure

BeatJobTime
HookSay or show the payoff, the problem or a surprising line in the first second. The first frame must work with the sound off.0–2 s
BodyOne idea delivered fast: steps, a before/after, one example. Cut every word that doesn't move it forward.Most of it
EndLand the point, then end on a line or image that flows back into the start so it loops.Last 1–3 s

Rules:

  • Start mid-action. No intro, no "in this video".
  • On-screen text for the key line of every beat, inside the middle of the frame: the top and bottom are covered by the Shorts UI.
  • A visual change every few seconds: cut, zoom, new text, new angle.
  • No CTA that pauses the video. If there's an ask, make it one short line at the end, or point to the related long video.

Title and description

  • Title: short and plain, 3–6 words naming the moment or result, under 60 characters. Pass it as platform_options.title; otherwise the first line of the content is used.
  • Description: one or two lines on what it's about, then 2–3 single-word hashtags. PostOnce sends up to 8 description hashtags as tags.

Output

Return, per Short: the hook line, the script with [ON SCREEN: …] and [SHOT: …] notes, the estimated length, the title and the description.

Once the vertical video is exported, offer to upload and publish or schedule it with the postonce skill. The same file can go to TikTok, Instagram Reels and Facebook as extra targets in one create_post, with a content_override per platform. Confirm the channel, privacy and time before calling create_post.

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.