mcpField
Y
yt-chapters

yt-chapters

github.com/jakeschincariolCreative & media3.5k481 installsUpdated 6w ago
Repository

About yt-chapters

yt-chapters analyzes an SRT transcript to identify chapter boundaries and draft topic-based titles. It also validates YouTube chapter requirements before the list is copied into a description.

Key features

  1. 01Scores pauses as boundaries
  2. 02Drafts topic-based titles
  3. 03Requires a 00:00 first entry
  4. 04Checks chapter count and duration
  5. 05Reports invalid lists

Use cases

  1. 01Drafting chapters from an SRT transcript
  2. 02Checking chapter formatting before pasting
  3. 03Reviewing whether a section needs dividing

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jakeschincariol/youtube-agent-skill --skill yt-chapters

After installing, type/yt-chaptersin Claude Code to confirm it loaded.

Bundled fileschapters.py

Details

From the project README

yt-chapters

python3 chapters.py transcript.srt --target 8

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

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?

Comments

Markdown supported