Skip to main content

yt-chapters

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

Zur Installation springen

Quellinformationen

Repository
Jakeschincariol/youtube-agent-skill
Letzte Quellaktivität
16. September 2026 um 13:31
Erkannte Sprache von SKILL.md
Englisch
Sterne
95
Forks
16

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
2 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
yt-chapters
description
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".
# 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?**
Auf GitHub ansehen