agentleFS
ahmedsakriahmedsakri/youtube-agent-pro/skills/yt-viral/SKILL.md

yt-viral

Skill1 starsChanged 38 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.

6 other projects use a version of this, 6 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, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.

    line 12

“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

Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.

Compare videos by multiple over each channel's own median as one useful outlier measure. Account for age, format, and topic before interpreting the multiple; public counts cannot establish why a video worked or predict whether copying its structure will succeed.

python3 "$YT_SKILL_DIR/swipe.py" collected.json --min 2.0

Collecting the input

The helper requires at least four videos per channel, but a small sample still gives an unstable baseline. Collect verified public listings through available browsing, user-provided exports, or an available public-data tool. Record collection date, publication dates, format, and comparable video age; avoid mixing long-form and Shorts in one baseline. Inspect missing counts before scoring.

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

Read, do not scrape. 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.

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.