Back to Details

yt-retention

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

yt-retention

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".
观众留存图是 YouTube 唯一真正诚实的反馈来源。几乎没人会导出它。
bash
python3 retention.py retention.csv --duration 600
python3 retention.py retention.csv --transcript transcript.srt
获取文件：Studio -> 某个视频 -> 分析 -> 互动 -> 观众留存图 -> 下载图标 -> “观众留存率”。

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.
  • HOOK LEAK（开头流失）——前 30 秒流失了什么。流失率低于 25% 属于健康范围。这始终是首要修复项，而且应该从脚本的前十五秒着手解决，而不是只靠剪辑。
  • CLIFFS（断崖式下跌）——单次陡降。断崖通常发生在某个瞬间，例如没有过渡提示的主题切换、赞助商口播或冗长的铺垫。使用 
    --transcript
    时，工具会打印当时所说的内容，这正是报告能够用于实际决策，而不只是提供一些有趣信息的原因。
  • SLIDE（平缓下滑）——视频中段持续流失。平缓下滑是节奏问题。解决方法是删减，而不是重写。

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
.
指出最大的单一流失点，并针对它给出一个改动建议。不要列出一长串建议。只有在用户提出要求时，再给出其余建议。如果开头流失情况健康，而中段呈平缓下滑，就说明视频本身没有问题，问题出在包装——请让用户使用 
/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?
这里不会发布任何内容。这个 skill 负责输出内容，由用户负责发布。每份输出都以一个供用户复制的区块结束，而每次运行的最后一行都是这个问题：发布，还是修改？