yt-retention
Read a YouTube Studio audience-retention export and find where viewers actually leave, then say what to change. Use for "why do people stop watching", "my retention is bad", a pasted retention chart or CSV, or "fix my pacing".
How do I install this agent skill?
npx skills add https://github.com/jakeschincariol/youtube-agent-skill --skill yt-retentionIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The yt-retention skill is designed to analyze YouTube audience retention data from CSV and transcript files. The skill is generally safe but carries minor risks associated with the dynamic loading of local modules and the ingestion of untrusted transcript data which provides a potential surface for indirect prompt injection.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
yt-retention
The retention graph is the only honest feedback YouTube gives you. Almost nobody exports it.
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
--transcriptthe 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?
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/jakeschincariol/youtube-agent-skill/yt-retention">View yt-retention on skillZs</a>