agentleFS
nessalaznenessalazne/youtube-agent-skill/skills/yt-viral/SKILL.md

yt-viral

Skill5 starsChanged 54 days agoMITView on GitHub

Find what is actually working in the user's niche on YouTube and rank it by how far each video beat its own channel, then name the formula. Use for "what's working right now", "find viral videos in my niche", "why did this blow up", competitor research, or a swipe file.

  • Reads credentials

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

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    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:

    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 …

    line 57

“Common” is measured: kept by at least 6 in 10 of the 3 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-viral

Raw view counts rank channel size, not ideas. This ranks by multiple over each channel's own median, which is the only version of the question that is about the video.

python3 swipe.py collected.json --min 2.0

Collecting the input

You need at least four videos per channel or a median means nothing, and the tool will skip the channel and tell you it did.

channel.py collects them for you, and writes the exact shape swipe.py reads:

python3 ../../tools/channel.py @rival1 @rival2 @rival3 --max 15 --json > collected.json
python3 swipe.py collected.json --min 2.0

That needs a free YouTube API key in ~/.claude/youtube/.env. Without one, collect the list however the user prefers - yt-dlp --flat-playlist -J against a channel URL works, the public page works, a manual list works - and hand swipe.py the same shape:

[{"channel":"...","title":"...","views":412000,"url":"...","duration":613}]

Read, do not scrape. channel.py is the official Data API with the user's own key: public listings only, never a logged-in session, never the user's own account credentials.

Reading the output

The multiple is the signal. The formula line is a judgement about the TITLE, matched against the 21 formulas - it is not a claim about why the video worked, and you should say so when you present it.

What to hand back: the top five with their multiples, the formula each used, and the ONE structural thing they share. Then the harder line - which of those the user could actually make this week, in their voice, with what they have.

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.

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.