viral-scout
Skill23 starsChanged 18 days agoMITView on GitHub
Finds the pattern behind hooks that worked in a niche, never the wording. Works honestly without web access by asking the user to paste examples. Use when someone asks what's trending, what's going viral, or wants to learn from other creators' hooks.
In this repository8 other files it gives its agents.
- four-failures-checkSkill
- hook-formatsSkill
- hook-masterSkill
- lock-inSkill
- niche-tunerSkill
- the-councilSkill
- viewer-panelSkill
- visual-matchSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Distinctive: line 17
Ask for 3 to 5 examples, pasted or linked:
- Distinctive: line 40
Only borrow a pattern the user's own footage and proof can support.
- Distinctive: line 45
Don't leave them with nothing.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Viral Scout
People ask "what's going viral this week?" The honest answer depends on what you can actually see.
First, say what you can see
- No web or platform access (the usual case): say so in one plain line. "I can't see this week's feeds, so I won't guess what's trending." Then offer the useful route below. Never list "trending hooks" from memory as if they were current.
- Web access: you can search, but view counts on a page are a snapshot and creators' own numbers are self-reported. Say where each example came from and when.
The honest route
Ask for 3 to 5 examples, pasted or linked:
- The first line spoken, the on-screen text, what's in the first shot.
- Rough views, and that creator's usual views if they know them. A video that beats its own creator's normal is more useful than a big account's ordinary post.
- One or two that flopped in the same niche, if they have them. Comparing a hit with its weaker neighbours shows what made the difference.
Break down the pattern, not the words
For each example:
| Part | Note |
| Format | Fortune Teller, Experimenter, Teacher, Investigator, Contrarian, Magician layer |
| Contrast | What the viewer believed versus what the video showed |
| First shot | What was on screen at second zero |
| Text | What the on-screen text added |
| Payoff speed | How fast the next lines confirmed the hook |
| Proof | What made it believable |
Then write the pattern in one line: "The hits open on [shot], use [format], and prove it within [time]."
Use it without copying
- Borrow the pattern, never the sentence. Their exact line belongs to them.
- Only borrow a pattern the user's own footage and proof can support.
- One example is an anecdote. Three that share a pattern are a lead, not a law.
While you wait for examples
Don't leave them with nothing. Fix their hook now using durable patterns (a clear subject, a true contrast, the payoff frame at second zero, proof straight after). Say these are durable principles, not this week's trend.
Never
- Invent a trending sound, format, or "hook everyone's using right now".
- Quote view counts you didn't see.
- Promise a pattern will make their video go viral.
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.

