youtube-metadata
Skill4 starsChanged 33 days agoMITView on GitHub
Write the YouTube title options, description with chapters, tags and pinned comment for a finished video, using only claims the video actually makes. Use after a long form or short is edited.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- rocosen/flashdata-mcptheir own version, first seen Oct 17, 2026
- shipshitshow/skillstheir own version, first seen Oct 2, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- rocosen/flashdata-mcp★ 0same name
- shipshitshow/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 repository4 other files it gives its agents.
- interview-shot-sheetSkill
- long-form-editorSkill
- shorts-cutterSkill
- video-quality-checkSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 14
No claim the video doesn't back up.
- Distinctive: line 30
Every number matches the video.
- Very specific: line 31
Every link promised in the video is filled in.
≈ “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 metadata
Work from the final cut, not the plan: read the transcript and the cut list so every claim matches what's actually said.
Title
- One main title plus 2 backups for A/B testing.
- Under ~60 characters, with the strongest word early.
- The title and thumbnail should add to each other, not repeat. If the thumbnail says "10 HRS → 1 HR", the title shouldn't.
- No claim the video doesn't back up.
Description
- First two lines (shown above "more"): what the video is plus the payoff. Put links people were promised in the video here.
- What's inside / resources.
- Chapters, computed from the real edit timeline (
0:00first, at least 3, each ≥ 10 s). Name them like a viewer would search. - Gear or tools mentioned, with the real prices said in the video.
- A short sign-off or CTA in the creator's own voice.
Tags
10–20, most specific first: the topic, the tools named, "how to" phrasings, the channel name.
Pinned comment
The promised link plus one question that invites replies.
Checks before posting
- Every number matches the video.
- Every link promised in the video is filled in. Never ship a
[placeholder]. - Flag anything that could read as contradictory (e.g. two different time claims) and suggest how to answer 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.