Yt retention skill
Read a YouTube Studio audience-retention export and find where viewers actually leave, then say what to change.
by Jakeschincariol·MIT license·★ 1,136 Stars on the repo·GitHub ↗
Use now
npx degit Jakeschincariol/youtube-agent-skill/skills/yt-retention#main ~/.claude/skills/yt-retentionChecked ·commit main
Inside this skill
SKILL.md · the author's own words# 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.
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Yt retention
SKILL.md
Show the full text42 lines
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?
| 1 | |
| 2 | name yt-retention |
| 3 | description >- |
| 4 | Read a YouTube Studio audience-retention export and find where viewers |
| 5 | actually leave, then say what to change. Use for "why do people stop |
| 6 | watching", "my retention is bad", a pasted retention chart or CSV, or "fix |
| 7 | my pacing". |
| 8 | |
| 9 | |
| 10 | # yt-retention |
| 11 | |
| 12 | The retention graph is the only honest feedback YouTube gives you. Almost nobody exports it. |
| 13 | |
| 14 | |
| 15 | python3 retention.py retention.csv --duration 600 |
| 16 | python3 retention.py retention.csv --transcript transcript.srt |
| 17 | |
| 18 | |
| 19 | Getting the file: Studio -> a video -> Analytics -> Engagement -> the audience-retention chart -> |
| 20 | the download icon -> "Audience retention". |
| 21 | |
| 22 | ## Three different problems |
| 23 | |
| 24 | **HOOK LEAK** - what is lost in the first 30 seconds. Under 25% is healthy. This is always the |
| 25 | first thing to fix and it is always the first fifteen seconds of script, never the edit. |
| 26 | **CLIFFS** - single steep drops. A cliff is a moment: a topic change with no signposting, a |
| 27 | sponsor read, a long setup. With `--transcript` the tool prints what was being said there, which |
| 28 | is what makes the report actionable instead of interesting. |
| 29 | **SLIDE** - the steady bleed across the middle. A flat slide is pacing. The fix is cutting, not |
| 30 | rewriting. |
| 31 | |
| 32 | ## What to hand back |
| 33 | |
| 34 | Name the single biggest leak and one change for it. Not a list of five. Then, only if asked, the |
| 35 | rest. And if the hook leak is healthy and the slide is flat, say the video is fine and the problem |
| 36 | is packaging - send them to `/yt-package`. |
| 37 | |
| 38 | ## The gate |
| 39 | |
| 40 | Nothing here publishes. This skill writes and you publish. Every output ends in a block the user |
| 41 | copies, and the last line of every run is the question: **ship it, or change it?** |
| 42 |
Discussion
Alternatives
Subscription Lifecycle: Trial, Churn, Win-backWhen the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.Win back customers before they cancelTell us about your subscription business and why people quit. Get back a ready-to-use plan to keep more customers and recover failed payments.Customer success managerUse this agent when you need to assess customer health, develop retention strategies, identify upsell opportunities, or maximize customer lifetime value. Invoke this agent for account health analysis, churn prevention, product adoption optimization, and customer success planning. Specifically:\\n\\n<example>\\nContext: Customer success team notices a large enterprise customer has reduced usage frequency by 40% over the past month and hasn't engaged in quarterly business reviews.\\nuser: "We're concerned about TechCorp's engagement. Usage is down significantly. Can you assess what's happening and help us develop a retention strategy?"\\nassistant: "I'll analyze TechCorp's health metrics including usage patterns, feature adoption, support interactions, and engagement history. I'll identify specific churn risks, assess whether there are product fit issues or implementation gaps, and develop a targeted intervention plan with clear milestones and success metrics."\\n<commentary>\\nUse customer-success-manager when you need to evaluate at-risk accounts and create proactive retention strategies. This agent analyzes health signals holistically and prescribes specific interventions.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Product team is rolling out new features and customer success team wants to maximize adoption across the customer base while identifying expansion revenue opportunities.\\nuser: "We're launching three new features next month. How do we ensure our customers actually adopt them? And which customers might be willing to upgrade to higher tiers?"\\nassistant: "I'll segment your customer base by maturity level and current product usage patterns. I'll develop feature-specific adoption strategies for each segment, identify high-value customers ready for expansion conversations, and create a phased rollout plan with success metrics and training resources."\\n<commentary>\\nInvoke this agent when you need to drive adoption of new features or identify expansion opportunities. The agent analyzes customer readiness and creates tailored engagement strategies for different segments.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Quarterly renewal period is approaching and customer success team wants to prepare for renewal conversations with key accounts and identify which customers are at risk of non-renewal.\\nuser: "We have 40 accounts up for renewal in the next 90 days. Can you help us prepare renewal strategies and flag which ones might be at risk?"\\nassistant: "I'll assess each account's health indicators including NPS, usage trends, executive engagement, feature adoption, and any unresolved issues. I'll prioritize high-risk accounts for intervention, develop renewal talking points based on demonstrated value, and create a pre-renewal engagement plan for each tier of customer."\\n<commentary>\\nUse this agent when renewal periods are approaching or you need to forecast renewal risk. The agent quantifies customer health and develops specific pre-renewal strategies to maximize renewal rates.\\n</commentary>\\n</example>\\n\\nDoes not handle individual support tickets or FAQ/help-center content — hand those to customer-support. Does not own pre-sale technical POC/RFP work — hand that to sales-engineer. Does not finalize pricing or discount decisions — route to the account/deal team. Does not review or negotiate contract/legal terms — route to legal-advisor./cs:cco-review — CCO Forcing Questions/cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire.
Browse more free Claude skills or everything in Customer support.