jakeschincariol/youtube-agent-skill

yt-retention

Read a YouTube Studio audience-retention export and find where viewers actually leave, then say what to change.

ソースを見る

使い方

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

開始前の確認

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

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

yt-retention

The retention graph is the only honest feedback YouTube gives you. Almost nobody exports it.

bash
python3 retention.py retention.csv --duration 600
python3 retention.py retention.csv --transcript transcript.srt

Getting the file: Studio -> a video -> Analytics -> Engagement -> the audience-retention chart -> the download icon -> "Audience retention".

Three different problems

  • HOOK LEAK - what is lost in the first 30 seconds. Under 25% is healthy. This is always the

first thing to fix and it is always the first fifteen seconds of script, never the edit.

  • CLIFFS - single steep drops. A cliff is a moment: a topic change with no signposting, a

sponsor read, a long setup. With --transcript the tool prints what was being said there, which is what makes the report actionable instead of interesting.

  • SLIDE - the steady bleed across the middle. A flat slide is pacing. The fix is cutting, not

rewriting.

What to hand back

Name the single biggest leak and one change for it. Not a list of five. Then, only if asked, the rest. And if the hook leak is healthy and the slide is flat, say the video is fine and the problem is packaging - send them to /yt-package.

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