--- 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. title: yt-script canonical_url: https://skilld.dev/gh/jakeschincariol/youtube-agent-skill/yt-script last_updated: 2026-10-02T00:19:57.000Z --- > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > Supporting files, fetch one when the Skill refers to it: [hooks.json](https://skilld.dev/api/skills-raw/jakeschincariol/youtube-agent-skill/yt-script/hooks.json), [hookscore.py](https://skilld.dev/api/skills-raw/jakeschincariol/youtube-agent-skill/yt-script/hookscore.py). > > If the user asked to install this Skill, run `npx skilld install jakeschincariol/youtube-agent-skill/yt-script`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/yt-script`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/jakeschincariol/youtube-agent-skill/yt-script) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/yt-script`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/yt-script --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/yt-script --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # 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 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](https://skilld.dev/api/skills-raw/jakeschincariol/youtube-agent-skill/yt-script/hooks.json), 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 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?**