使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jakeschincariol/youtube-agent-skill --skill yt-script開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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?