agentleFS
Sign inStart free
utillayerutillayer/youtube-agent-skill/skills/yt-audit/SKILL.md

yt-audit

Skill10 starsChanged 29 days agoMITView on GitHub

Review a whole YouTube channel - packaging, consistency, openings, rhythm - and end with the single fix that matters most. Use for "audit my channel", "why isn't my channel growing", "review my videos", or a pasted channel link.

5 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    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
  1. Very specific:

    Read ~/.claude/youtube/voice.md if it exists.

    line 16
  2. Distinctive:

    Never make up a number. Use the channel's figures or none.

    line 18
  3. Distinctive:

    No praise you do not mean at the start, no twenty-item list at the end.

    line 40

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

yt-audit

A list of twenty problems is a way to avoid the one that matters. This review ends with one fix.

Before you start

  1. Read ~/.claude/youtube/voice.md if it exists. If not, ask for three of the creator's videos and write it.
  2. Never make up a number. Use the channel's figures or none.

What to look at, in order

  1. The last ten titles, as a list - the way the channel page shows them. Do they promise different things? Lint them with ${CLAUDE_SKILL_DIR}/../yt-package/title.py. When every title has the same shape, the problem is the format, not the titles.
  2. The thumbnails, at feed size. Shrink them. What still reads? If three are unreadable small, that is the fix and nothing else matters yet.
  3. The first fifteen seconds of the last three videos. Transcribe them and score them with ${CLAUDE_SKILL_DIR}/../yt-script/hookscore.py. This is where most channels lose people.
  4. Upload rhythm. Consistency, not frequency. Six videos in a week and then a silent month does more harm than one every fortnight forever.
  5. Retention, if they can export it: /yt-retention.

What to hand back

  • The single biggest fix, named, with what to do about it this week.
  • Three things that already work, so they are not broken by accident. Specific: "your energy is good" is not an observation.
  • What not to do yet, and why.

No praise you do not mean at the start, no twenty-item list at the end.

Before you hand it over

This skill drafts; you publish. End with the copy-ready block and one question: post it as is, or another pass?

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free