YouTube Video Scriptwriter

Yt script

by Jakeschincariol · MIT license · ★ 1,136 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",…

---
name: yt-script
description: >-
  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.
---

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

```bash
python3 hookscore.py hooks.txt              # rank your hook options

Overview

Two tools live in this folder and both actually run. Use them. Do not eyeball the hook.

Manual install (npx, ZIP)

Claude Codenpx skills add Jakeschincariol/youtube-agent-skill --skill yt-script -g -a claude-code

Claude Code (degit)npx degit Jakeschincariol/youtube-agent-skill/skills/yt-script#main ~/.claude/skills/yt-script

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.6 KB

Read SKILL.md here

Jakeschincariol/main1 file shown

SKILL.md2.6 KB

Browse every file on GitHub↗

SKILL.md

Show the full text59 lines

yt-script/SKILL.md59 lines · 2.6 KB

PreviewCode

Outline

RawView on GitHub

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

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

1	---
2	name: yt-script
3	description: >-
4	Write a YouTube video script from a raw idea - hook options off 21
5	formulas, scored, then the full spoken script with the retention beats
6	marked. Use whenever the user wants a video script, a hook, an opening
7	line, "what should I say", "write my next video", or is about to record
8	and does not have the first fifteen seconds yet.
9	---
10
11	# yt-script
12
13	One idea into a script somebody finishes.
14
15	Two tools live in this folder and both actually run. Use them. Do not eyeball the hook.
16
17	```bash
18	python3 hookscore.py hooks.txt # rank your hook options
19	python3 hookscore.py --hook "one line" # score a single one
20	```
21
22	## Before you write
23
24	1. Read `~/.claude/youtube/voice.md` if it exists. That is the user's voice profile: how they talk
25	on camera, the words they never use, who they are talking to, what they will not claim. If it
26	does not exist, ask for three of their own videos, read or transcribe them, infer the voice,
27	and write the file. A script in the wrong voice is worse than no script, because they have to
28	read it out loud.
29	2. Never invent a number, a result or a source. If a figure would strengthen it and you do not have
30	one, ask for it or write the line without it.
31
32	## The shape
33
34	The first 15 seconds is the whole job. It does three things or the video leaks: confirm the
35	click the title promised, open a question the viewer cannot close, and prove the payoff exists.
36
37	1. Hook. Write FIVE against [the 21 formulas](hooks.json), run them through `hookscore.py`,
38	keep the top two, and show the user both with their scores. Never hand over one hook.
39	2. The turn (0:15-0:45). Say what the video is going to do, in one sentence, and start doing it.
40	No channel intro, no "before we get started", no subscribe pitch. Those are the single most
41	common cause of the 0:30 cliff.
42	3. The body. One idea per beat. Mark each beat with what is ON SCREEN, not just what is said -
43	a talking head with nothing to look at is a podcast.
44	4. The payoff. Deliver the thing the hook promised, explicitly, and say that you are delivering
45	it: "that is the prompt, it is in the description".
46	5. The close. One ask. Not three.
47
48	## What to hand back
49
50	- the two best hooks with their scored panels
51	- the script, beat by beat, with `[ON SCREEN: ...]` on every beat
52	- the runtime estimate at 150 words per minute
53	- one line naming which formula the winning hook used and why it fits this idea
54
55	## The gate
56
57	Nothing here publishes. This skill writes and you publish. Every output ends in a block the user
58	copies, and the last line of every run is the question: ship it, or change it?
59