yt-package
Skill1 starsChanged 37 days agoMITView on GitHub
Write and lint the title and thumbnail for a YouTube video as one pairing, checking truncation, duplication and vagueness before publish. Use for "title ideas", "what should I call this", "thumbnail text", "my CTR is bad", packaging, or any request to rename or repackage an existing video.
7 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- utillayer/youtube-agent-skilltheir own version, first seen Nov 8, 2026
- uplika/uplika-pluginedited, first seen Oct 25, 2026
- Rohit-Kumar-AI/youtube-creator-agenttheir own version, first seen Oct 20, 2026
- swayamdhawan/youtube-agentedited, first seen Oct 15, 2026
- nessalazne/youtube-agent-skilledited, first seen Sep 23, 2026
- Jakeschincariol/youtube-agent-skilledited, first seen Sep 16, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- Jakeschincariol/youtube-agent-skill★ 4753% same
- nessalazne/youtube-agent-skill★ 547% same
- uplika/uplika-plugin★ 316% same
- swayamdhawan/youtube-agent★ 053% same
Wrote their own version · 3
- utillayer/youtube-agent-skill★ 10same name
- Rohit-Kumar-AI/youtube-creator-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 repository25 other files it gives its agents.
- openai/AGENTS.mdAGENTS.md
- llms.txtllms.txt
- yt-analyticsSkill
- yt-auditSkill
- yt-briefSkill
- yt-chaptersSkill
- yt-collabSkill
- yt-commentSkill
- yt-editSkill
- yt-endscreenSkill
- yt-funnelSkill
- yt-ideaSkill
- yt-planSkill
- yt-repurposeSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-seriesSkill
- yt-shortsSkill
- ytSkill
- yt-sponsorSkill
- yt-thumbnailSkill
- yt-trendSkill
- yt-viralSkill
- yt-voiceSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
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
- Distinctive: line 12
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
- Very specific: line 25
Use the creator's supplied voice profile or context, then a local ~/.claude/youtube/voice.md if available, following the operating guide.
- Distinctive: line 28
Never invent a number, a result or a source.
- Distinctive: line 36
Aim for 0–3 thumbnail words: Treat this as a readability heuristic, not a platform rule.
- Distinctive: line 38
Two all-caps words is the ceiling: before a title reads as spam.
“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
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
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 "$YT_SKILL_DIR/title.py" --title "..." --thumb "AI RAN IT"
python3 "$YT_SKILL_DIR/title.py" titles.txt # one per line, rankedBefore you write
- Use the creator's supplied voice profile or context, then a local
~/.claude/youtube/voice.mdif available, following the operating guide. If absent, draft in a clear voice using the stated audience and format; do not make voice-profile setup a prerequisite. - 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 and 40 characters are the helper's conservative truncation checks, not fixed YouTube limits. Display varies by surface and device; keep the subject early and preview when possible.
- The thumbnail must not repeat the title. Different words, same promise.
- Aim for 0–3 thumbnail words. Treat this as a readability heuristic, not a platform rule.
- 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.
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.