youtube-script-generator
Skill1 starsChanged 47 days agoMITView on GitHub
Write long-form YouTube video scripts with a hook for the first 30 seconds, retention beats, pattern interrupts, a payoff and a call to action, plus the title and description to publish it with the PostOnce YouTube MCP. Use when the user asks for a YouTube script, a script generator, a video outline, or to turn an article, notes or idea into a YouTube video script.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Write one script for one long-form video (roughly 5–20 minutes).
- Distinctive: line 33
Write for the ear: short sentences, contractions, one idea per sentence.
≈ “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.
Files
YouTube script generator
Write one script for one long-form video (roughly 5–20 minutes). For vertical videos up to 3 minutes, use the youtube-shorts-script skill instead.
Before writing
Get or infer: the topic and the one promise the video makes, the viewer (beginner or experienced), target length, the presenter's voice (read a past script or transcript if offered), what's on screen (talking head, screen recording, B-roll), and the action the viewer should take at the end. If the user gives a source (article, notes, transcript), keep its facts and cut the rest. Never invent data, quotes, case studies or personal stories.
Structure
| Section | Job | Length |
| Hook | Deliver on the title and thumbnail in the first line. Show the result, the stakes or the problem. | 0:00–0:30 |
| Setup | Why this matters to the viewer and what they'll have by the end. No channel intro, no "before we start, subscribe". | 30–60 seconds |
| Body | 3–7 beats in a clear order (steps, mistakes, levels). Each beat: point, proof or example, what to do. | Most of the video |
| Payoff | The result, summarized in one or two lines. | Short |
| CTA | One ask tied to the video: a related video, a free resource or a subscribe with a reason. | 1–2 sentences |
Keeping people watching
- Open loops: tease a later beat early ("the third setting is the one most people miss") and pay it off.
- Re-hook between beats with a one-line transition that says what's next and why it matters.
- Pattern interrupts every 30–60 seconds: a cut to screen, a B-roll note, an on-screen text callout, a quick example. Mark them in the script.
- Show, don't narrate: when something is on screen, the script should say less.
- Write for the ear: short sentences, contractions, one idea per sentence. Read it aloud.
Anti-patterns
Long intros, "Hey guys, welcome back", asking for likes before delivering value, filler recaps, and ending with "that's it for today" and no next step.
Output
Return:
- The script with section headings, spoken lines, and
[ON SCREEN: …]/[B-ROLL: …]notes, plus a rough runtime. - Three title options (use
youtube-title-generatorrules) and a thumbnail idea that pairs with the best one. - Offer a description with chapters from the final timestamps (
youtube-description-generator).
Once the video is recorded and exported (one file, up to 768 MB), offer to upload and publish or schedule it with the postonce skill, setting platform_options.title, description and privacy. Confirm the channel, privacy and time before calling create_post.
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.