All skills
jakeschincariol avatar

/yt-retention

@a2feb21
by Jake Schincarioljakeschincariol/youtube-agent-skill707 stars
179

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".

Requires /yt-package
Use this Skill: https://skilld.dev/gh/jakeschincariol/youtube-agent-skill/yt-retention

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈60 tokens for metadata: the name and description. ≈354 when used: this file.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈241 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 --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?

Source: SKILL.md on GitHub

Skill behaviors

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

Third-party checks

No alerts19d3 checks · Risk SAFE
  • Gen Agent Trust Hub19d

    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.

  • Socket19d

    No alerts

  • Snyk19d

    Risk: LOW · No issues

Provenance

Signed by skilld at a2feb21. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 1 hour ago.

Activeupdated 3 weeks ago

README badge

README badge for jakeschincariol/youtube-agent-skill/yt-retention