yt-audit
Skill1 starsChanged 37 days agoMITView on GitHub
Audit a YouTube channel end to end - packaging, consistency, the first fifteen seconds, and what to fix first. Use for "audit my channel", "why isn't my channel growing", "review my videos", or a pasted channel URL.
5 other projects use a version of this, 5 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-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 versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- Jakeschincariol/youtube-agent-skill★ 4764% same
- utillayer/youtube-agent-skill★ 1025% same
- nessalazne/youtube-agent-skill★ 552% same
- uplika/uplika-plugin★ 327% same
- swayamdhawan/youtube-agent★ 064% same
Wrote their own version · 0
None found.
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-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
- 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. 2 are common, 1 is distinctive, and 2 are very specific to this project.
2
Common
Most of the 5 edited versions we read keep these.
1
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
- Distinctive: line 11
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
- Very specific: line 18
Use the creator's supplied voice profile or context, then a local ~/.claude/youtube/voice.md if available, following the operating guide.
- Common: line 21
Never invent a number, a result or a source.
- Very specific: line 26
The last ten titles, as a set: Read them as a list, the way the channel page shows them.
- Common: line 45
Never open an audit with praise you do not mean, and never end one with a list of twenty things.
“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-audit
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
An audit that lists twenty problems is a way of avoiding the one that matters. This ends in ONE fix.
Before 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.
What to look at, in this order
- The last ten titles, as a set. Read them as a list, the way the channel page shows them. Do
they promise different things? Run them through
../yt-package/title.py. A channel where every title is the same shape has a format problem, not a title problem. - The thumbnails, at feed size. Shrink them. What survives? If three of them are unreadable at that size, that is the fix and nothing else matters yet.
- The first fifteen seconds of the three most recent. Transcribe them and score with
../yt-script/hookscore.py. This is where most channels lose. - Upload rhythm and capacity. Compare formats, publication age, and performance before attributing a result to frequency. A sustainable cadence helps planning, but consistency alone does not establish how YouTube will distribute a video.
- The retention shape, if they can export it.
/youtube-agent-pro:yt-retention.
What to hand back
- The single biggest fix, named, with what to do this week.
- Three things that are already working, so they do not break them. Be specific; "your energy is good" is not an observation.
- What NOT to do yet, and why.
Never open an audit with praise you do not mean, and never end one with a list of twenty things.
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.