agentleFS
Sign inStart free
nessalaznenessalazne/youtube-agent-skill/skills/yt-chapters/SKILL.md

yt-chapters

Skill5 starsChanged 52 days agoMITView on GitHub

Write YouTube chapters from a transcript, validated against YouTube's own rules so they actually render. Use for "add chapters", "timestamps", "break this video into sections".

6 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No transcript to hand? If the video is on YouTube already:

    line 15
  2. Very specific:

    If they want it on the channel, /yt-publish is the only skill in this pack that touches YouTube, it uploads private unless they say …

    line 47

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

yt-chapters

python3 chapters.py transcript.srt --target 8

No transcript to hand? If the video is on YouTube already:

python3 ../../tools/transcript.py "$URL" --srt -o transcript.srt

The rules, which are not optional

A chapter list that breaks any of these silently does not become chapters at all - the block just sits in the description doing nothing:

  • The first entry must be 00:00.
  • There must be at least three.
  • Each must be at least 10 seconds long.

The tool checks all three and tells you when a list is invalid rather than letting you paste it.

Retitle every line

chapters.py finds the BOUNDARIES well - it scores the pauses you actually took by how much the vocabulary shifts across them. The titles it emits are the topic words, and they are a draft. A chapter called "Thumbnails Titles Packaging" is a placeholder. Rewrite each one as the promise of that section, in the user's voice, three to five words.

Chapters are also a retention diagnostic: if a section cannot be named in five words, it is two sections or it is filler.

The gate

This skill never publishes. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?

If they want it on the channel, /yt-publish is the only skill in this pack that touches YouTube, it uploads private unless they say otherwise, and it asks again before it does anything.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free