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 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

모든 Skills