yt-audit
Skill5 starsChanged 52 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
- ahmedsakri/youtube-agent-proedited, first seen Oct 15, 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★ 4793% same
- utillayer/youtube-agent-skill★ 1026% same
- uplika/uplika-plugin★ 334% same
- ahmedsakri/youtube-agent-pro★ 165% same
- swayamdhawan/youtube-agent★ 093% 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 repository11 other files it gives its agents.
- yt-chaptersSkill
- yt-commentSkill
- yt-editSkill
- yt-packageSkill
- yt-planSkill
- yt-publishSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-shortsSkill
- yt-viralSkill
The file
We split this skill into the rules it gives an agent
6 rules. 2 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read ~/.claude/youtube/voice.md if it exists.
- Common: line 20
Never invent a number, a result or a source.
- Very specific: line 31
Read them as a list, the way the channel page shows them.
- Distinctive: line 45
Upload rhythm: Not frequency - CONSISTENCY.
- Common: line 56
Never open an audit with praise you do not mean, and never end one with a list of twenty things.
- Very specific: line 63
If they want it on the channel, /yt-publish is the only skill in this pack that touches YouTube, it uploads private unless they say …
“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
An audit that lists twenty problems is a way of avoiding the one that matters. This ends in ONE fix.
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.
What to look at, in this order
The last ten titles, as a set. Pull them rather than asking the user to paste them:
python3 ../../tools/channel.py @handle --max 10Read 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. Pull each transcript, take the opening, and score it:
python3 ../../tools/transcript.py "$URL" | head -c 400 > hook.txt python3 ../yt-script/hookscore.py hook.txtThis is where most channels lose.
- Upload rhythm. Not frequency - CONSISTENCY. Six videos in one week and then nothing for a month is worse than one a fortnight forever.
- The retention shape, if they can export it.
/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.
The gate
This skill never publishes. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?
If they want it on the channel, /yt-publish is the only skill in this pack that touches YouTube,
it uploads private unless they say otherwise, and it asks again before it does anything.
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.