yt
Skill1 starsChanged 37 days agoMITView on GitHub
The hub for the YouTube agent. Routes a vague request to the right skill and develops a video production package - idea, script, package, thumbnail, SEO, chapters, then the after-publish loop. Use for "help me with my channel", "make my next video", "where do I start", or any YouTube request where the specific skill is not obvious yet.
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-packageSkill
- yt-planSkill
- yt-repurposeSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-seriesSkill
- yt-shortsSkill
- yt-sponsorSkill
- yt-thumbnailSkill
- yt-trendSkill
- yt-viralSkill
- yt-voiceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
- Very specific: line 21
Use the available channel, voice, audience, and format context.
- Distinctive: line 57
When the user wants a whole production package, use this order and continue through the authorized stages.
- Very specific: line 65
After it is up: /youtube-agent-pro:yt-retention and /youtube-agent-pro:yt-analytics to find the one fix for next time.
≈ “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
yt
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
The front door. Use this when the user does not know which skill they need, or wants the whole thing done in order rather than one piece.
Start from the request
Use the available channel, voice, audience, and format context. A profile is optional; read the operating guide for lookup order. If the user wants profile setup, use /youtube-agent-pro:yt-voice. Otherwise continue with the task rather than requiring setup first.
Route the request
Match the ask to the skill below, read its linked instructions, and perform that workflow. These are local skill files, not tools or executable slash-commands.
| the user says | run |
| "what should I make", "I have no idea" | /youtube-agent-pro:yt-idea |
| "write the script", "what do I say" | /youtube-agent-pro:yt-script |
| "title", "what do I call it", "my CTR is bad" | /youtube-agent-pro:yt-package |
| "thumbnail", "design the thumbnail" | /youtube-agent-pro:yt-thumbnail |
| "description", "tags", "nobody finds it" | /youtube-agent-pro:yt-seo |
| "chapters", "timestamps" | /youtube-agent-pro:yt-chapters |
| "why do people stop watching" | /youtube-agent-pro:yt-retention |
| "my numbers", "which video worked", a Studio export | /youtube-agent-pro:yt-analytics |
| "cut this into shorts", "clip this" | /youtube-agent-pro:yt-shorts |
| "turn this into a thread / newsletter / post" | /youtube-agent-pro:yt-repurpose |
| "edit this", "I rambled" | /youtube-agent-pro:yt-edit |
| "reply to comments" | /youtube-agent-pro:yt-comment |
| "plan my week / month" | /youtube-agent-pro:yt-plan |
| "a series", "a playlist" | /youtube-agent-pro:yt-series |
| "what's working in my niche" | /youtube-agent-pro:yt-viral |
| "sponsorship", "rate card", "a brand emailed me" | /youtube-agent-pro:yt-sponsor |
| "find a collab" | /youtube-agent-pro:yt-collab |
| "my channel page", "subscribers aren't converting" | /youtube-agent-pro:yt-funnel |
| "what to post this season", "trending" | /youtube-agent-pro:yt-trend |
| "shot list", "production brief", "how do I film this" | /youtube-agent-pro:yt-brief |
| "end screen", "cards", "what plays next" | /youtube-agent-pro:yt-endscreen |
| "review my whole channel" | /youtube-agent-pro:yt-audit |
The full run
When the user wants a whole production package, use this order and continue through the authorized stages. Respect any explicit review point; ask only when a missing choice prevents useful progress.
- /youtube-agent-pro:yt-idea - pick one, scored.
- /youtube-agent-pro:yt-script - hook options, then the spoken script.
- /youtube-agent-pro:yt-brief - translate the script into a shot list and production plan.
- /youtube-agent-pro:yt-package + /youtube-agent-pro:yt-thumbnail - the click surface, linted as one pairing.
- /youtube-agent-pro:yt-seo + /youtube-agent-pro:yt-chapters - the found-in-search surface.
- After it is up: /youtube-agent-pro:yt-retention and /youtube-agent-pro:yt-analytics to find the one fix for next time.
Deliver the requested drafts and files with any assumptions or unresolved inputs. Creating a finished video requires separate recording, generation, or editing tools; this pack does not render or upload it. For a Shorts-only channel, keep the workflow and analytics specific to Shorts.
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.