agentleFS
Sign inStart free
nessalaznenessalazne/youtube-agent-skill/skills/yt-script/SKILL.md

yt-script

Skill5 starsChanged 51 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, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 1 is common, 1 is distinctive, and 3 are very specific to this project.

  • 1

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ~/.claude/youtube/voice.md if it exists.

    line 24
  2. Common:

    Never invent a number, a result or a source.

    line 29
  3. Very specific:

    Hook: Write FIVE against the 21 formulas, run them through hookscore.py, keep the top two, and show the user both with their scores.

    line 37
  4. Distinctive:

    No channel intro, no "before we get started", no subscribe pitch.

    line 40
  5. Very specific:

    If they want it on the channel, /yt-publish is the only skill in this pack that touches YouTube, it uploads private unless they say …

    line 60

“Common” is measured: kept by at least 6 in 10 of the 6 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

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 one

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

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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".
  5. 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

This skill never publishes. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?

If they want it on the channel, /yt-publish is the only skill in this pack that touches YouTube, it uploads private unless they say otherwise, and it asks again before it does anything.

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