yt-package
Skill10 starsChanged 29 days agoMITView on GitHub
Write and test a video's title and thumbnail together, linted for truncation, repetition and vague words before it goes live. Use for "title ideas", "what should I call this", "thumbnail text", "my click-through is low", packaging, or renaming a video that already exists.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- uplika/uplika-plugintheir own version, first seen Oct 25, 2026
- Rohit-Kumar-AI/youtube-creator-agenttheir own version, first seen Oct 20, 2026
- swayamdhawan/youtube-agenttheir own version, first seen Oct 15, 2026
- ahmedsakri/youtube-agent-protheir own version, first seen Oct 15, 2026
- nessalazne/youtube-agent-skilltheir own version, first seen Sep 23, 2026
- Jakeschincariol/youtube-agent-skilltheir own version, first seen Sep 16, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Jakeschincariol/youtube-agent-skill★ 47same name
- nessalazne/youtube-agent-skill★ 5same name
- uplika/uplika-plugin★ 3same name
- ahmedsakri/youtube-agent-pro★ 1same name
- Rohit-Kumar-AI/youtube-creator-agent★ 0same name
- swayamdhawan/youtube-agent★ 0same name
- tylerprogramming/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- yt-auditSkill
- yt-chaptersSkill
- yt-commentSkill
- yt-editSkill
- yt-planSkill
- yt-researchSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-shortsSkill
- yt-viralSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read ~/.claude/youtube/voice.md if it exists.
- Distinctive: line 28
Never make up a number. "Doubled" needs the before and after.
- Distinctive: line 43
Write ten titles. Lint them all.
- Distinctive: line 46
If the top two are close, say so and suggest Studio's A/B test (up to three titles or thumbnails, judged by watch time share.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
yt-package
A viewer sees the title and the thumbnail in the same glance, so write them as one thing. The commonest waste is a thumbnail that repeats the title: two surfaces, one message.
python3 ${CLAUDE_SKILL_DIR}/title.py --title "..." --thumb "THREE WORDS"
python3 ${CLAUDE_SKILL_DIR}/title.py titles.txt --thumb "THREE WORDS" # one per line, rankedThe tools live in this skill's folder. ${CLAUDE_SKILL_DIR} is that folder in Claude Code; anywhere
it does not expand (claude.ai, Codex), use the folder this SKILL.md was loaded from.
Before you start
- Read
~/.claude/youtube/voice.mdif it exists. If not, ask for three of the creator's videos and write it. The title should sound like the person in the video. - Never make up a number. "Doubled" needs the before and after.
What the linter checks, and why
- Length. About 60 characters survives desktop search and about 40 a phone feed. YouTube does
not publish either number - truncation is by pixel width - so treat them as the safe side, not a
law. A desktop cut loses the end; a phone cut can lose the subject. The hard limit is 100, and
<>are not allowed. - Repetition. The thumbnail says what the title does not.
- Thumbnail words. Three at most. A fourth turns to mush at feed size.
- Something concrete. A number, a name or a date beats any adjective.
- Capitals. Two all-caps words is the limit before it reads as shouting.
The method
- Write ten titles. Lint them all. Show the best three with their scores and the one issue each has.
- For the winner, write the thumbnail: the single image, the expression, at most three words, and how the background keeps contrast at feed size.
- If the top two are close, say so and suggest Studio's A/B test (up to three titles or thumbnails, judged by watch time share; desktop Studio only, not for Shorts) instead of pretending the linter can tell them apart. The score is a lint, not a forecast.
Before you hand it over
This skill drafts; you publish. End with the copy-ready block and one question: post it as is, or another pass?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.