yt-package
The title and the thumbnail are ONE unit. Writing them separately is why most packaging fails: the
thumbnail repeats the title, and half the click surface says the same thing twice.
python3 title.py --title "..." --thumb "AI RAN IT"
python3 title.py titles.txt # one per line, ranked
Before you write
- Read
~/.claude/youtube/voice.md if it exists. That is the user's voice profile: how they talk
on camera, the words they never use, who they are talking to, what they will not claim. If it
does not exist, ask for three of their own videos, read or transcribe them, infer the voice,
and write the file. A script in the wrong voice is worse than no script, because they have to
read it out loud.
- Never invent a number, a result or a source. If a figure would strengthen it and you do not have
one, ask for it or write the line without it.
Rules the tool enforces, and why
- 60 characters is where desktop search truncates, 40 is a mobile home feed. Both are
reported because they fail differently: a desktop cut loses the tail, a mobile cut can lose the
subject.
- The thumbnail must not repeat the title. Different words, same promise.
- Three words maximum on the thumbnail. At feed size a fourth word is a grey smear.
- A number, a name or a date beats every adjective available to you.
- Two all-caps words is the ceiling before a title reads as spam.
Write ten, keep two
Generate ten titles, run them all through title.py, show the user the top three with their scores
and the specific issue on each. For the winner, write the thumbnail brief: the expression, the
framing, the three words, and what the background has to do to hold contrast at feed size.
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?
1---2name: yt-package3description: >-4 Write and lint the title and thumbnail for a YouTube video as one pairing,5 checking truncation, duplication and vagueness before publish. Use for6 "title ideas", "what should I call this", "thumbnail text", "my CTR is7 bad", packaging, or any request to rename or repackage an existing video.8metadata:9 source: https://skillmd.com/skills/jakeschincariol/yt-package10---1112# yt-package1314The title and the thumbnail are ONE unit. Writing them separately is why most packaging fails: the15thumbnail repeats the title, and half the click surface says the same thing twice.1617```bash18python3 title.py --title "..." --thumb "AI RAN IT"19python3 title.py titles.txt # one per line, ranked20```2122## Before you write23241. Read `~/.claude/youtube/voice.md` if it exists. That is the user's voice profile: how they talk25 on camera, the words they never use, who they are talking to, what they will not claim. If it26 does not exist, ask for **three of their own videos**, read or transcribe them, infer the voice,27 and write the file. A script in the wrong voice is worse than no script, because they have to28 read it out loud.292. Never invent a number, a result or a source. If a figure would strengthen it and you do not have30 one, ask for it or write the line without it.3132## Rules the tool enforces, and why3334- **60 characters** is where desktop search truncates, **40** is a mobile home feed. Both are35 reported because they fail differently: a desktop cut loses the tail, a mobile cut can lose the36 subject.37- **The thumbnail must not repeat the title.** Different words, same promise.38- **Three words maximum on the thumbnail.** At feed size a fourth word is a grey smear.39- **A number, a name or a date** beats every adjective available to you.40- **Two all-caps words is the ceiling** before a title reads as spam.4142## Write ten, keep two4344Generate ten titles, run them all through `title.py`, show the user the top three with their scores45and the specific issue on each. For the winner, write the thumbnail brief: the expression, the46framing, the three words, and what the background has to do to hold contrast at feed size.4748## The gate4950Nothing here publishes. This skill writes and you publish. Every output ends in a block the user51copies, and the last line of every run is the question: **ship it, or change it?**