executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
yt-retentionRead 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".
Independent GitHub snapshot · Automated classification · Original documentation governs
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".
--transcript the tool prints what was being said there, which
is what makes the report actionable instead of interesting.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.
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?