Update to YouTube Agent

{
  "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\".",
  "included_files": [
    {
      "relative_path": "chapters.py",
      "size_in_bytes": 3744
    }
  ],
  "name": "yt-chapters",
  "skill_md_contents": "---\nname: yt-chapters\ndescription: >-\n  Write YouTube chapters from a transcript, validated against YouTube's own\n  rules so they actually render. Use for \"add chapters\", \"timestamps\",\n  \"break this video into sections\".\n---\n\n# yt-chapters\n\nUse scripts relative to this skill directory, not the user’s working directory. If local execution or inputs are unavailable, explain the limitation and provide a clearly labeled manual alternative; do not claim a tool ran. Scores and thresholds are heuristics, not guarantees or causal proof. Use only accessible or user-provided data; never invent analytics.\n\n```bash\npython3 chapters.py transcript.srt --target 8\n```\n\n## The rules, which are not optional\n\nA chapter list that breaks any of these silently does not become chapters at all - the block just\nsits in the description doing nothing:\n\n- The first entry must be **00:00**.\n- There must be **at least three**.\n- Each must be **at least 10 seconds** long.\n\nThe tool checks all three and tells you when a list is invalid rather than letting you paste it.\n\n## Retitle every line\n\n`chapters.py` finds the BOUNDARIES well - it scores the pauses you actually took by how much the\nvocabulary shifts across them. The titles it emits are the topic words, and they are a draft. A\nchapter called \"Thumbnails Titles Packaging\" is a placeholder. Rewrite each one as the promise of\nthat section, in the user's voice, three to five words.\n\nChapters are also a retention diagnostic: if a section cannot be named in five words, it is two\nsections or it is filler.\n\n## The gate\n\nNothing here publishes. This skill writes and you publish. Every output ends in a block the user\ncopies, and the last line of every run is the question: **ship it, or change it?**\n"
}