Viral Reverse Engineering logo

Viral Reverse Engineering

Organization
social-media-skills
viral-reverse-engineering

Use to reverse-engineer why a piece of content went viral (or overperformed) — yours or someone else's — and extract the repeatable mechanism to apply to your own content. Run when the user says "why did this go viral," "break down this viral post/video," "reverse engineer," "what made this work," or wants to learn from viral content. Sources the observable signal first (intake, transcript, screenshots, top comments, visible stats — an agent usually can't watch a video from a link) and never fabricates what it can't see. Reads brand-profile and audience first, deconstructs the piece layer by layer, isolates the real driver, runs a replicability check, extracts the transferable principle, and applies it to the user's niche via the content skills. Mechanism, never a copy; flags non-replicable virality; visible signals only (no WoopSocial analytics). Single-POST teardown only: for the account-level competitive landscape use competitor-analysis; for riding a live trend use trend-jacking.

Overview

Publishersocial-media-skills
Repositoryskills
Skill nameviral-reverse-engineering
Stars
215
Forks
44
Bundled files
6
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.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by social-media-skills on GitHub. Read the source before you install it.

Installation

Install the Viral Reverse Engineering 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/social-media-skills/skills/tree/main/skills/viral-reverse-engineering
  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/social-media-skills/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/viral-reverse-engineering .claude/skills/viral-reverse-engineering
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Viral Reverse Engineering 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 Viral Reverse Engineering 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 Viral Reverse Engineering 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.

Viral Reverse-Engineering

Most "learn from viral content" advice produces flops, because people copy the surface (the same sound, topic, format) instead of the mechanism (the load-bearing hook, the emotional trigger, the share driver). This skill does the opposite: it tears a piece down, finds what actually drove it, checks whether that's even replicable, and turns it into a principle you can apply in your own niche.

Two commitments:

  1. Mechanism, not surface. Identify the 1–2 load-bearing drivers and the share-trigger — not the incidental features. Copying noise reproduces noise.
  2. Honest about luck and survivorship. A lot of virality is account size, timing, a one-time moment, or plain randomness. When success isn't replicable, say so — a false formula is worse than none.

Step 0 — Read the foundation

Load brand-profile.md and audience.md (for the "apply to your niche" step).

Step 1 — Source the content (the step everyone skips)

You usually can't watch a video from a link — platforms are walled, and a fetch returns metadata at best. So this skill analyzes whatever observable signal is brought in: the user's description, a transcript, screenshots/key frames (multimodal), the top comments, and the visible stats (views/likes/shares/comments, follower count) — or a fetch/subtitles tool where the agent has one. Run the structured intake in references/sourcing-the-content.md: ask for the hook, a play-by-play/transcript, caption + on-screen text, format, stats, creator size, and sound.

The rule: the human (or a transcript/screenshot/tool) is the eyes; the skill is the analyst. Never fabricate frames or lines you weren't given — analyze what's provided and name the gaps. Also: patterns need multiple examples — one viral post is an anecdote. (Other people's posts are visible/native signals or pasted data. Your own posts on the covered platforms can use WoopSocial post analytics.)

Step 2 — Deconstruct (the teardown)

Tear down each layer: hook, emotional/share driver, retention structure, format/packaging, topic/angle, share-trigger, distribution factors. One line per layer; don't praise everything. See references/deconstruction-framework.md.

Step 3 — Isolate the real driver (counterfactual)

For each notable feature, ask "remove this — does it still pop?" Whatever it can't lose without collapsing is a driver; what it can lose is incidental. Usually only 1–2 layers are load-bearing (typically the hook + the emotional/share trigger). Most bad analysis credits the noise.

Step 4 — Identify the share-trigger

Virality = shares, so name why people sent it to someone else: identity/self-expression, high-arousal emotion (awe/anger/humor/inspiration), social currency, practical value, relatability, story. A piece with no share-trigger gets views, not virality. See references/why-things-spread.md. (The top comments are the best evidence here — see references/sourcing-the-content.md.)

Step 5 — Replicability check

Screen for confounds before extracting anything: account-size advantage, luck/variance, one-time moments, survivorship bias, sample size. If the success is mostly confound, flag it as non-replicable and don't invent a principle. See references/replicability-and-application.md.

Step 6 — Extract the principle + apply to your niche

State the mechanism in one line, translate it to the user's subject (same mechanism, your topic), and hand execution to the content skills (hook-writer, tiktok-script, reels-script, caption-writer, carousel-writer) in the brand voice. Output is "the lever is X; here's X applied to you" — never a copy. Build a swipe file of recurring patterns over time.

Quality bar — self-check

  • Did I source real input (intake/transcript/screenshots/comments), and not fabricate what I couldn't see — naming the gaps?
  • Did I find the mechanism (1–2 real drivers + the share-trigger), not the surface?
  • Did the counterfactual rule out incidental features?
  • Did I run the replicability check and flag confounds/luck/small-sample honestly?
  • Is the output a principle applied to the user's niche, not a copy?
  • Did I respect the ethics line (inspiration, not plagiarism/IP theft)?
  • Did I use visible/native signals with no analytics claims, and make no virality guarantees?

Edge cases & pushback

  • Bare link, nothing else → explain you can't watch the video; run the intake (ask for transcript/screenshots/stats) or use a subtitles/fetch tool if available; don't pretend you saw it.
  • Partial input (transcript only, screenshots only) → analyze what's there, name what you can't assess (e.g., pacing/edit, or the spoken layer).
  • "Copy it exactly with our product" → mechanism + your own substance, not a surface copy (derivative + IP risk).
  • "It was the sound/topic" → counterfactual-test it; usually the hook + trigger were the real lever.
  • Huge-account / one-time virality → flag non-replicable; don't extract a false formula.
  • One example → anecdote, not a pattern; tear down several to find recurring mechanisms.
  • "Guarantee us viral" → no guarantees (luck/distribution); stack the odds via mechanisms.
  • No data to judge "viral" → use visible signals; be clear about the limits.

Related skills

  • brand-profile, audience-research — relevance + the "apply to your niche" step.
  • hook-writer — the most common load-bearing driver; trend-jacking — overlapping "why it spread."
  • tiktok-script, reels-script, caption-writer, carousel-writer — execute the extracted principle.
  • competitor-analysis, analytics-and-reporting (advisory) — broader performance analysis.

References

  • references/sourcing-the-content.md — how the content gets into context (intake, transcripts, screenshots, comments, tools) + graceful degradation. Start here.
  • references/deconstruction-framework.md — the layer-by-layer teardown + the counterfactual driver test.
  • references/why-things-spread.md — the share-trigger psychology (why people share).
  • references/replicability-and-application.md — survivorship/luck/sample-size honesty; extract + apply; ethics.
  • references/examples.md — worked teardowns, including a non-replicable case.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Viral Reverse Engineering AI skill do?

Use to reverse-engineer why a piece of content went viral (or overperformed) — yours or someone else's — and extract the repeatable mechanism to apply to your own content. Run when the user says "why did this go viral," "break down this viral post/video," "reverse engineer," "what made this work," or wants to learn from viral content. Sources the observable signal first (intake, transcript, screenshots, top comments, visible stats — an agent usually can't watch a video from a link) and never fabricates what it can't see. Reads brand-profile and audience first, deconstructs the piece layer b...

Why use Viral Reverse Engineering on TypingMind?

Because you install it once and use it with any model. Viral Reverse Engineering 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 Viral Reverse Engineering in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/social-media-skills/skills/tree/main/skills/viral-reverse-engineering. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Viral Reverse Engineering?

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 Viral Reverse Engineering?

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

Is the Viral Reverse Engineering AI skill free?

Yes. It is published on GitHub by social-media-skills 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 👇