yt-seo
Skill47 starsChanged 59 days agoMITView on GitHub
Write the description, tags and search-facing text for a YouTube video, aimed at the query a real person types. Use for "write my description", "tags", "SEO", "help this video get found", "nobody is finding this".
6 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- utillayer/youtube-agent-skilledited, first seen Nov 8, 2026
- uplika/uplika-pluginedited, first seen Oct 25, 2026
- swayamdhawan/youtube-agentword for word, first seen Oct 15, 2026
- ahmedsakri/youtube-agent-protheir own version, first seen Oct 15, 2026
- nessalazne/youtube-agent-skilledited, first seen Sep 23, 2026
- tylerprogramming/claude-skillstheir own version, first seen Aug 9, 2026
Other versions6 projects use a version of this.
Word for word · 1
- swayamdhawan/youtube-agent★ 0100% same
Edited · 3
- utillayer/youtube-agent-skill★ 1012% same
- nessalazne/youtube-agent-skill★ 584% same
- uplika/uplika-plugin★ 328% same
Wrote their own version · 2
- ahmedsakri/youtube-agent-pro★ 1same 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 repository10 other files it gives its agents.
- yt-auditSkill
- yt-chaptersSkill
- yt-commentSkill
- yt-editSkill
- yt-packageSkill
- yt-planSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-shortsSkill
- yt-viralSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Search is a smaller lever than packaging and a bigger one than people think for evergreen videos.
- Very specific: line 16
Read ~/.claude/youtube/voice.md if it exists.
- Distinctive: line 21
Never invent a number, a result or a source.
- Distinctive: line 40
Before handing anything over, write the three search queries this video should win, and check the title and first two description lines …
“Common” is measured: kept by at least 6 in 10 of the 5 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-seo
Search is a smaller lever than packaging and a bigger one than people think for evergreen videos.
For a video aimed at the subscriber feed, say so and spend the effort on /yt-package instead.
Before you write
- Read
~/.claude/youtube/voice.mdif 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.
The description
- The first two lines are the only ones anyone reads. They show above "...more" and they are the search snippet. Say what the video gives them, in the words they would have typed.
- Then the link or the resource, if there is one, so it is above the fold.
- Then chapters (
/yt-chapterswrites them). - Then the long version: what is covered, who it is for, what it assumes.
Tags, honestly
Tags are a weak signal and YouTube has said so. Use them for disambiguation - spellings, the tool names, the abbreviations people actually type - and stop. Fifteen is plenty. A wall of tags is not a strategy and stuffing unrelated ones is against the terms.
The query test
Before handing anything over, write the three search queries this video should win, and check the title and first two description lines contain the words in those queries. If they do not, the problem is the title, not the description.
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?
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.