Going Viral logo

Going Viral

Organization
Ootto-AI
going-viral

The strategy layer for making short-form video actually go viral — pick the goal, manufacture the emotion that drives it, then build the hook + funnel around it. Use when the user says "go viral", "make it go viral", "why isn't my content getting views", "how do I get more reach / saves / shares / followers", "my reels flop", "viral strategy", "what makes a reel go viral", or "how do I grow on Instagram / TikTok / Shorts". This is the WHY/strategy above the tactical skills (viral-hook-writer writes the hook; this decides what to make it about and why).

Overview

PublisherOotto-AI
Repositoryclaude-content-skills
Skill namegoing-viral
Stars
264
Forks
53
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Ootto-AI on GitHub. Read the source before you install it.

Installation

Install the Going Viral AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/going-viral
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git /tmp/claude-content-skills
mkdir -p .claude/skills
cp -r /tmp/claude-content-skills/skills/going-viral .claude/skills/going-viral
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Going Viral in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Going Viral on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Going Viral is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Going Viral — the strategy, not just the hook

Most "go viral" advice is tactics with no spine. This is the spine: virality is engineered, not lucky. Pick ONE goal → manufacture the emotion that drives it → build the hook + funnel around it. The reel manufactures the feeling; the caption/DM delivers the value.

Distilled from 160+ analysed viral reels + the research consensus (Berger & Milkman: sharing is driven by high arousal, not positivity; ~68% of people share to signal who they are; saves = a promise to future-self; open loops must stay open past the 7–15s checkpoint).

When to use

The user has an idea (or a flopping account) and wants reach/saves/shares/followers/leads — not just a better opening line. (For only the first 1–3 seconds, use viral-hook-writer. To run the whole pipeline, use content-factory.)

Step 1 — Pick ONE goal (it dictates everything)

GOALEmotion to triggerThe mechanicHow to build it
SAVErelief + fear-of-forgettinga finite numbered system + "future-you will need this"a list/steps that assembles on one frame → "save so you don't lose it"; put the depth in the caption
SHAREawe / indignation / statusmeta self-proving · "you're being ripped off" · "almost nobody knows"open on the finished result then reveal how · "$5K agency → free" · scarcity + "send this to someone still doing it the hard way"
FOLLOWFOMO ("don't fall behind") + aspirationanti-falling-behind framing + result-first proof + a consistent brandshow the gap (manual you vs automated them), a real climbing number, a recognizable look every post
LEADgreed + terminal curiositya named free deliverable withheld behind a keywordshow the value, withhold the thing → "comment WORD" → instant honest DM

Pick the goal before scripting. Optimize for identity signal, not raw value — a share has to make the sender look smart/early/right. High-arousal beats positive: awe, anger, FOMO over calm tips.

Step 2 — The hook (the first ~1.5s decide everything)

  • Frame 0 IS the hook. The biggest element is already on screen AND moving — a count-up number, a finished artifact, a UI caught mid-action. It owns ≥40% of the frame and is legible on mute (70–85% watch sound-off). No fade-from-black, no slow logo build, no title card.
  • Order: motion → lock → claim. Let the moving element run ~1s, lock it, then spring the one-line claim. The claim lands ~1.2–1.6s — never at 0s (no payoff yet), never at 3s+ (too late).
  • Open a gap, not a fact. "The one setting that doubled my reach" — never "here are some reach tips."
  • Rotate the angle every post (contrarian / result-first / meta-self-proving / POV / numbered). The meta "this was made by AI" self-proving angle is the strongest when it's true — the post proves its own claim. The "N things nobody uses" listicle fatigues fastest; don't default to it.

Step 3 — Hold them (after the hook)

  • Show, don't tell — every line gets a visual. Never a plain text card for a how/demo line.
  • Nothing static. Every element keeps a low-amplitude idle motion the whole time. A frozen frame is where people scroll.
  • Re-hook at the dips (~4s / 9s / 15s) with a micro-loop: "but here's the part nobody tells you…", "and it gets better…", "wait for the last one."
  • Keep it short + re-watchable. The reel teases; the caption delivers. A tight loop drives replays, and replays drive reach.

Step 3.5 — Curiosity & the incentivized wait (make them watch to the END)

The single biggest watch-time lever: give them a reason to wait — promise the payoff up front, then withhold it until the end. This is exactly what made "I let Claude post for 6 days — Day 6 broke everything" work: the climax is teased in second 0, but you have to watch the whole thing to get it.

The mechanic — promise → withhold → escalate → pay off:

  1. Tease the payoff in the hook, but don't show it. Name that something big is coming and where ("Day 6 broke everything", "the 5th one is the one that 10×'d it", "wait for the last step"). The viewer now has a concrete reason to stay — an open loop that only closes at the end.
  2. Make it an escalating series with a visible finish line. Number or date the beats (Day 1 → Day 6, prompt 1 → 5, step 1 → 4) so they always know how far the payoff is. A countdown is unscrollable — quitting early feels like losing the thing you were promised.
  3. Each beat out-does the last (or raises the tension), so leaving always costs more than staying. Save the single best / most surprising moment for the very last beat.
  4. Pay it off — for real. The end must deliver the promised thing (the Day-6 result, the #5 prompt, the "secret"). Tease, never lie: an unpaid loop makes the viewer feel cheated — it kills saves + shares and trains the algorithm that you waste watch-time.

Curiosity-gap hooks (open the loop the brain must close):

  • "I did [X] for [N] days — [Day N / the last one] broke everything." ← the 6-day pattern
  • "The one [setting / prompt / step] nobody talks about — and it's #[N]."
  • "Watch till the end — the last one is the only one that actually worked."
  • "[N] ways to do [X]. #[N] should be illegal." / "save #[N] for later."
  • Withhold the mechanism: show the result, make them stay for the how.

The incentive to wait must be EXPLICIT and worth it. Name a concrete reward for reaching the end — the exact result, the secret prompt, the number. Vague "stay tuned" doesn't hold; "Day 6 hit 24k — here's the one thing that did it" does. That payoff is also the natural bridge into the CTA (comment the keyword → I'll DM you the thing).

Never resolve the loop early. If you reveal the payoff in the middle, the loop closes and they leave. Hold the climax for the final beat, then convert immediately.

Step 4 — Convert (the funnel)

The reel hooks + teases → the caption delivers the full value → a comment keyword → auto-DM turns a watcher into a lead.

  • CTA = one action. Save ("don't lose this") / Share ("send to someone still doing it by hand") / Follow ("don't fall behind") / Comment a keyword ("comment WORD → I'll DM it").
  • Keyword in the first line of the caption (most people never tap "more"). Keyword CTAs convert ~5–15% vs ~1–3% for "link in bio."
  • The link goes in the DM, never the public comment (links in comments get reach-suppressed; the DM keeps the lead in your inbox).
  • Wire the keyword→DM loop with the comment-responder skill + the open-source automation (github.com/Ootto-AI/claude-figma-stack) so it replies + DMs every lead 24/7.

The non-negotiables (every post)

  1. Honesty — any stat you show must be real/defensible; any "comment WORD → I'll DM it" must actually deliver. Tease, never lie — every loop you open must close, or reach + trust both collapse.
  2. Originality — model a proven reel's technique/structure, write your OWN words + visuals. Never copy a creator's script/voice/caption — the platforms bury copies.
  3. Identity + arousal — make it shareable because it signals who the sharer is, and because it fires a high-arousal emotion. Calm, neutral "value" doesn't spread.

The 5-step checklist

  1. Choose the goal → look up its emotion (Step 1).
  2. Manufacture that emotion with the matching mechanic; obey the hook rule (Step 2).
  3. Open a curiosity gap in the hook — promise the payoff up front, withhold it to the end (escalating series w/ a visible finish line → save the best for last → reward the wait). Never resolve it early.
  4. Decide where the payoff lives — in-reel (proof) or withheld to caption + DM (default for value/lead posts).
  5. Convert with one CTA — Save / Share / Follow / Comment-keyword — and close every loop you opened.

Works with

agent-reach (scrape Reddit demand + find/download the reel to model — the FIND step) · viral-hook-writer (the hook itself) · reel-analyzer (study a proven viral reel first) · reel-scripter + reel-builder (build it) · caption-and-hashtags (the caption funnel) · comment-responder (the keyword → DM lead loop) · content-factory (runs the whole pipeline).

Frequently asked questions

What does the Going Viral AI skill do?

The strategy layer for making short-form video actually go viral — pick the goal, manufacture the emotion that drives it, then build the hook + funnel around it. Use when the user says "go viral", "make it go viral", "why isn't my content getting views", "how do I get more reach / saves / shares / followers", "my reels flop", "viral strategy", "what makes a reel go viral", or "how do I grow on Instagram / TikTok / Shorts". This is the WHY/strategy above the tactical skills (viral-hook-writer writes the hook; this decides what to make it about and why).

Why use Going Viral on TypingMind?

Because you install it once and use it with any model. Going Viral is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Going Viral in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/going-viral. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Going Viral?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Going Viral?

As many as you like. As long as a model supports skills, you can use Going Viral with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Going Viral AI skill free?

Yes. It is published on GitHub by Ootto-AI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇