youtube-title-generator
Skill1 starsChanged 47 days agoMITView on GitHub
Write YouTube video titles that rank for the search keyword and earn the click, then set the chosen one when publishing with the PostOnce YouTube MCP. Use when the user asks for a YouTube title generator, title ideas, a better title for a video, or to title a video from a script, transcript or topic.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vincentchan/AI-Content-Enginetheir own version, first seen Jan 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vincentchan/AI-Content-Engine★ 66same 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 repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
Write 10 title options for one video, recommend one, and hand it to the postonce skill as platform_options.title if the user wants to …
- Distinctive: line 19
Put the keyword near the front, in the words people search, not your internal name for it.
- Distinctive: line 23
Use numbers only when they're true and specific ("7 settings", "in 10 minutes").
- Very specific: line 24
Avoid &, < and >. PostOnce replaces & with "and" and angle brackets with look-alike characters because YouTube rejects them in titles.
- Distinctive: line 25
No ALL CAPS titles, no clickbait the video doesn't pay off, no stacked emojis, no hashtags in the title.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YouTube title generator
Write 10 title options for one video, recommend one, and hand it to the postonce skill as platform_options.title if the user wants to publish or schedule.
Before writing
Get or infer: what the video actually delivers (read the script, transcript or outline if there is one), who it's for, the search keyword people would type to find it, and whether it's long-form or a Short. Never promise something the video doesn't deliver, and never invent numbers or results for the title.
Rules
- Put the keyword near the front, in the words people search, not your internal name for it.
- Aim for under 60 characters so the title isn't cut off in search and suggested videos. YouTube's hard limit is 100.
- Make one clear promise: the result, the method or the mistake. One title, one idea.
- Titles and thumbnails work as a pair. The title should add to the thumbnail text, not repeat it.
- Use numbers only when they're true and specific ("7 settings", "in 10 minutes").
- Avoid
&,<and>. PostOnce replaces&with "and" and angle brackets with look-alike characters because YouTube rejects them in titles. - No ALL CAPS titles, no clickbait the video doesn't pay off, no stacked emojis, no hashtags in the title.
Patterns
| Pattern | Template |
| How-to | "How to [result] ([qualifier])" · "How to [result] Without [pain]" |
| Keyword + promise | "[Keyword]: [specific outcome] in [time]" |
| List | "[N] [Keyword] [Mistakes / Tips / Tools] for [audience]" |
| Mistake | "Stop [common action] (Do This Instead)" |
| Comparison | "[A] vs [B]: Which [Keyword] Is Better for [use]?" |
| Proof | "I [did the thing] for [time]. Here's What Happened" (only if they did) |
| Shorts | Short and plain; name the moment or result in 3–6 words. |
Output
Return a numbered list of 10 titles with the character count for each, grouped by pattern. Mark your pick and say why in one line (keyword position, promise, length).
When the user picks one, offer to publish or schedule with the postonce skill: pass it as platform_options.title on the YouTube target. If no title is set, YouTube gets the first line of the post content, so set it explicitly. Confirm the channel, privacy and time before calling create_post.
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.