jakeschincariol/youtube-agent-skill

yt-audit

Audit a YouTube channel end to end - packaging, consistency, the first fifteen seconds, and what to fix first.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jakeschincariol/youtube-agent-skill --skill yt-audit

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

yt-audit

An audit that lists twenty problems is a way of avoiding the one that matters. This ends in ONE fix.

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.

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

What to look at, in this order

  1. The last ten titles, as a set. Read them as a list, the way the channel page shows them. Do

they promise different things? Run them through ../yt-package/title.py. A channel where every title is the same shape has a format problem, not a title problem.

  1. The thumbnails, at feed size. Shrink them. What survives? If three of them are unreadable at

that size, that is the fix and nothing else matters yet.

  1. The first fifteen seconds of the three most recent. Transcribe them and score with

../yt-script/hookscore.py. This is where most channels lose.

  1. Upload rhythm. Not frequency - CONSISTENCY. Six videos in one week and then nothing for a

month is worse than one a fortnight forever.

  1. The retention shape, if they can export it. /yt-retention.

What to hand back

  • The single biggest fix, named, with what to do this week.
  • Three things that are already working, so they do not break them. Be specific; "your energy is

good" is not an observation.

  • What NOT to do yet, and why.

Never open an audit with praise you do not mean, and never end one with a list of twenty things.

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?

同じリポジトリから

関連する Skills

すべての Skills