agentleFS
Ootto-AIOotto-AI/claude-virality-skill/virality/SKILL.md

virality

Skill3 starsChanged 30 days agoMITView on GitHub

Plan, script and review short-form videos (Instagram Reels, TikTok, YouTube Shorts) so they actually get watched, with hooks that do something extraordinary in the first 3 seconds. Use when the user wants a reel idea, a hook, a script, a storyboard, or wants to know why a post flopped. Built from the real winners and losers of 262 posts and 3.5M views on @jayantcreates.ai.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. Ootto-AI/claude-content-skills★ 41762% same

    Wrote their own version · 1

    1. Jakeschincariol/master-skills★ 1same name

    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.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    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
  1. Distinctive:

    If nothing happens in those 3 seconds, nothing else you made matters.

    line 21
  2. Distinctive:

    Not a title card. Not a logo fading in.

    line 24
  3. Distinctive:

    Not a logo fading in. Not "Hi guys, today I want to talk about".

    line 25
  4. Distinctive:

    Every one of these crossed 100,000 views.

    line 31
  5. Distinctive:

    Every one of these stayed under 1,000 views.

    line 45
  6. Distinctive:

    Frame 0 is already moving: No fade-in, no black frame, no empty frame.

    line 83
  7. Distinctive:

    If a hook does not pass all eight, rewrite it before writing anything else.

    line 92
  8. Distinctive:

    Keep the reel short and put the depth in the caption.

    line 121
  9. Distinctive:

    When the user asks for a reel, a hook, or a script:

    line 136
  10. Distinctive:

    Ask who it is for and what they should get.

    line 138
  11. Distinctive:

    Write three hooks. For each, describe frame 0 and every half second up to 3 seconds, and check all eight points of the checklist.

    line 139
  12. Distinctive:

    Write the script line by line.

    line 141
  13. Distinctive:

    Write the comment keyword and the real thing the DM delivers.

    line 142
  14. Distinctive:

    Write the caption: problem, solution, the steps, then the keyword.

    line 143
  15. Distinctive:

    When the user asks why a post flopped:

    line 145
  16. Distinctive:

    Look at frame 0, 0.5s, 1s, 2s and 3s only.

    line 147

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

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

Virality

This skill ran the Instagram page @jayantcreates.ai: 262 posts, 3,503,488 views, 124,163 comments. It was not built from theory. It was built by putting our biggest winners and our worst flops side by side and studying the first 3 seconds of each, frame by frame.

  • June to August: 132 posts. Only 3 crossed 10,000 views.
  • September to October: 130 posts. 31 crossed 10,000 views. 9 crossed 100,000.

Same account, same topic, same tools. What changed is everything in this file.

Rule 1: The hook is the whole game

Most viewers decide in the first 3 seconds. If nothing happens in those 3 seconds, nothing else you made matters.

In the first 3 seconds, something extraordinary has to happen on screen. Not a title card. Not a logo fading in. Not "Hi guys, today I want to talk about". An event the eye cannot ignore.

What our winners did in the first 3 seconds

Every one of these crossed 100,000 views.

ViewsFrame 0 to 3s
346,327The Claude logo + the Instagram logo = a fire emoji, then a laptop slides up. Words land one at a time: "This honestly doesn't make sense".
306,575"How to edit video with Claude" with an edit timeline scrubbing under it, then a giant "7" slams in: "So easy. Only seven."
277,424The Instagram and Claude logos joined by a line, a counter that reads 0 and starts climbing: "Don't post anything else on Instagram until…"
225,342The Instagram logo and Claude connected by a glowing cable, words building: "Connect Claude to your Instagram".
132,604A skill file wired to Claude, the claim builds word by word: "This Claude skill makes unlimited reels", a hand reaches in.
132,399Claude and Instagram side by side with a LIVE badge, a news headline bar slides up underneath.
101,571The Claude character rains down out of the sky as voxels, lifts a lighter, and the headline burns away.

What our flops did in the first 3 seconds

Every one of these stayed under 1,000 views.

ViewsFrame 0 to 3s
279A pink sci-fi tunnel, then a static card: "2026: Claude writes code. 2028?" It never changes for 3 seconds.
306Same tunnel, static card: "$10 answer vs $10,000 answer. Same Claude." Nothing moves.
340Frame 0 is black. Then a dark grid: "This entire feed is 100% AI." It holds still.
383Frame 0 is almost empty dots. Green word chips: "YES, GENIUS, DO IT".
409Small red serif on a beige blur: "There are only 5 types of content".
519Small red serif: "Claude can plan 30 days of content". A counter is the only thing moving.
522"99% of Claude users don't know this" on a blank card, about a memory trick.

The same "99% of Claude users don't know this" hook flopped at 522 views and won at 35,834. The winner typed it live inside the real Claude app, then cut to the product doing it. The words were never the difference. What happened on screen was.

The patterns

Winners:

  1. The two logos the viewer knows, on frame 0. Five of our seven biggest reels opened on Claude and Instagram side by side, joined by a line, a plus sign or a cable. The viewer instantly knows what this is about, and that it is about their account.
  2. Something moves or happens on frame 0. A counter climbs, a cable connects, a character drops in, a logo breaks, a headline burns. Never a still card.
  3. The claim builds word by word, in sync with the voice, big and high contrast, readable on mute.
  4. It promises a result on the viewer's own account. "Your Instagram", "edit video", "make reels", "don't post anything else until".
  5. Curiosity or contrarian words. "Doesn't make sense", "can't see your Instagram by default", "don't post anything else until", "99% don't know", "just broke Instagram". In the same two months, hooks with these words had a median of 6,950 views, against 4,352 without.
  6. The real product appears fast. The real Claude app, the real connector, the real Instagram.

Losers:

  1. Abstract backgrounds with no brand the viewer knows (tunnels, space, clouds, gradients).
  2. A static card. The frames at 0.5s and 3s look the same.
  3. An empty or black frame 0.
  4. Small, low-contrast text (thin serif, pale colours).
  5. About AI or Claude in general, the future, or "me", not about the viewer's account. "Claude took over my Instagram" and "2,000 messages to my leads" both flopped.

The checklist (every hook must pass all eight)

  1. Frame 0 is already moving. No fade-in, no black frame, no empty frame.
  2. Frame 0 shows something the viewer instantly recognises (the platform logo, the app, their problem), not abstract art.
  3. The biggest element owns at least 40% of the frame and moves from frame 1.
  4. Something extraordinary happens before 3 seconds: it explodes, burns, breaks, builds itself, collapses, or a number races and locks.
  5. The claim lands around 1.2 to 1.6 seconds, word by word, big, high contrast. Never at 0, never after 3.
  6. The first spoken word is within 0.5 seconds, and it is the subject ("Business owners:", "Claude just…"), not filler.
  7. It works on mute.
  8. It is about the viewer's account or business, not about you or AI in general.

If a hook does not pass all eight, rewrite it before writing anything else.

Rule 2: Talk about their thing, not your tool

In the same two months, posts that named the viewer ("you", "your") in the first line had a median of 5,186 views, against 3,930 for those that did not. Our biggest posts were all about what happens to the viewer's own account.

  • Bad: "7 Claude tricks that feel illegal to know" (335 views).
  • Good: "Editing a video? Just tell Claude" (306,575 views).

The viewer is the main character. The tool is the vehicle.

Rule 3: Every line is shown, never just said

  • The visual changes on every spoken line.
  • Each sentence gets its own mechanism on screen: a screen that types, a counter that climbs, a phone that receives a message, a character that walks to the next step.
  • Nothing on screen is ever static. If two frames a second apart look the same, add motion.
  • Text appears word by word, in sync with the voice.
  • Show real proof: real screens, real numbers, real results. A fake number gets caught and kills trust.
  • With stock footage, pick the clip where something is visibly happening (a person reacting, celebrating, shocked), not a still scene. Search for the action or emotion ("woman jumping with joy"), not the noun ("woman"). Cut the person out and put the words behind them.

Rule 4: Give them a reason to comment

In the same two months, posts with a comment keyword in the first line had a median of 5,684 views, against 4,311 without.

  • End with one keyword: "Comment SETUP and I'll send you the setup."
  • The keyword must deliver something real in the DM. If you promise it, send it.
  • The link goes in the DM, never in a public comment.
  • Keep the reel short and put the depth in the caption.

Rule 5: Rotate the angle

The same hook framing twice in a row fatigues fast. Rotate between:

  • Result first: open on the outcome, then show how.
  • Self-proving: "Nobody filmed this video. It's me, Claude." The post proves the claim by existing.
  • Contrarian: "Stop paying an agency for Instagram."
  • Pain first: "Business owners: you're losing leads in your DMs every night."
  • Something breaks: "Claude just broke Instagram." The thing on screen literally breaks.

How to use this skill

When the user asks for a reel, a hook, or a script:

  1. Ask who it is for and what they should get. One sentence.
  2. Write three hooks. For each, describe frame 0 and every half second up to 3 seconds, and check all eight points of the checklist.
  3. Pick the strongest and say why, naming the winning pattern it uses.
  4. Write the script line by line. Next to every line, write what happens on screen. No line without a visual.
  5. Write the comment keyword and the real thing the DM delivers.
  6. Write the caption: problem, solution, the steps, then the keyword.

When the user asks why a post flopped:

  1. Look at frame 0, 0.5s, 1s, 2s and 3s only.
  2. Compare against the loser patterns: abstract background, static card, empty frame 0, small text, about AI instead of the viewer.
  3. Check Rules 2, 3 and 4.
  4. Give the one change that would have mattered most, then a rewritten hook that passes the checklist.

Output format for a reel plan

WHO IT'S FOR: ...
HOOK (0-3s):
  0.0s  [what is on screen, already moving, recognisable]
  0.5s  [first spoken word] ...
  1.2s  [the extraordinary event lands] + [the claim, word by word]
  3.0s  [transition into the body]
CHECKLIST: 1 ✓ 2 ✓ 3 ✓ 4 ✓ 5 ✓ 6 ✓ 7 ✓ 8 ✓
SCRIPT:
  line 1 -> on screen: ...
  line 2 -> on screen: ...
CTA: Comment <KEYWORD> -> DM delivers: ...
CAPTION: ...

Made by Ootto (ootto.ai). Free and MIT licensed.

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.