yt-script
Skill47 starsChanged 57 days agoMITView on GitHub
Write a YouTube video script from a raw idea - hook options off 21 formulas, scored, then the full spoken script with the retention beats marked. Use whenever the user wants a video script, a hook, an opening line, "what should I say", "write my next video", or is about to record and does not have the first fifteen seconds yet.
6 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- utillayer/youtube-agent-skilltheir own version, first seen Nov 8, 2026
- uplika/uplika-pluginedited, first seen Oct 25, 2026
- Rohit-Kumar-AI/youtube-creator-agenttheir own version, first seen Oct 20, 2026
- swayamdhawan/youtube-agentword for word, first seen Oct 15, 2026
- ahmedsakri/youtube-agent-proedited, first seen Oct 15, 2026
- nessalazne/youtube-agent-skilledited, first seen Sep 23, 2026
Other versions6 projects use a version of this.
Word for word · 1
- swayamdhawan/youtube-agent★ 0100% same
Edited · 3
- nessalazne/youtube-agent-skill★ 592% same
- uplika/uplika-plugin★ 337% same
- ahmedsakri/youtube-agent-pro★ 149% same
Wrote their own version · 2
- utillayer/youtube-agent-skill★ 10same name
- Rohit-Kumar-AI/youtube-creator-agent★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- yt-auditSkill
- yt-chaptersSkill
- yt-commentSkill
- yt-editSkill
- yt-packageSkill
- yt-planSkill
- yt-retentionSkill
- yt-seoSkill
- yt-shortsSkill
- yt-viralSkill
The file
We split this skill into the rules it gives an agent
4 rules. 1 is common, 1 is distinctive, and 2 are very specific to this project.
1
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read ~/.claude/youtube/voice.md if it exists.
- Common: line 29
Never invent a number, a result or a source.
- Very specific: line 37
Hook: Write FIVE against the 21 formulas, run them through hookscore.py, keep the top two, and show the user both with their scores.
- Distinctive: line 40
No channel intro, no "before we get started", no subscribe pitch.
“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.
Files
yt-script
One idea into a script somebody finishes.
Two tools live in this folder and both actually run. Use them. Do not eyeball the hook.
python3 hookscore.py hooks.txt # rank your hook options
python3 hookscore.py --hook "one line" # score a single oneBefore you write
- Read
~/.claude/youtube/voice.mdif 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
The first 15 seconds is the whole job. It does three things or the video leaks: confirm the click the title promised, open a question the viewer cannot close, and prove the payoff exists.
- Hook. Write FIVE against the 21 formulas, run them through
hookscore.py, keep the top two, and show the user both with their scores. Never hand over one hook. - The turn (0:15-0:45). Say what the video is going to do, in one sentence, and start doing it. No channel intro, no "before we get started", no subscribe pitch. Those are the single most common cause of the 0:30 cliff.
- The body. One idea per beat. Mark each beat with what is ON SCREEN, not just what is said - a talking head with nothing to look at is a podcast.
- The payoff. Deliver the thing the hook promised, explicitly, and say that you are delivering it: "that is the prompt, it is in the description".
- The close. One ask. Not three.
What to hand back
- the two best hooks with their scored panels
- the script, beat by beat, with
[ON SCREEN: ...]on every beat - the runtime estimate at 150 words per minute
- one line naming which formula the winning hook used and why it fits this idea
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?
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.