yt-chapters
Write YouTube chapters from a transcript, validated against YouTube's own rules so they actually render.
- Kind
- Skill
- Works with
- Claude Code
- Source
- YouTube agent skill (Jake Schincariol) @ a2feb2104981
- Path
- skills/yt-chapters/SKILL.md
- Jobs
- Implementation
- Topics
- YouTube
Credit
- Made by
- Jakeschincariol
- Original
- github.com/Jakeschincariol/youtube-agent-skill/blob/a2feb2104…
- License
- MIT
Listed by Skill Manifest; not made by us.
InstallInstall it from a plugin marketplace.
/plugin marketplace add Jakeschincariol/youtube-agent-skill
Install factsScanned 2 Nov 2026
- Adds
- .claude/skills/yt-chapters/ (the skill folder)
- Runs scripts
- Yes
- chapters.py
- shell block in the text
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- a2feb2104981
- Licence
- MIT
- Last activity
- 16 Sep 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- Only the main file is read; other files in the folder are not scanned
# yt-chapters ```bash 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?**