viral-reverse-engineering SKILL.md skillA
viral-reverse-engineering from social-media-skills/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add social-media-skills/skills/viral-reverse-engineering@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- social-media-skills/skills
- Path
skills/viral-reverse-engineering/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.0, committed Oct 14, 2026
- First version recorded
- Jul 8, 2026
- Size
- 7,604 bytes
- Repository stars
- 251
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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, …
Read the whole file at its exact version.
How to install
mdr add social-media-skills/skills/viral-reverse-engineering@sha256:b85e454b838d2bcfThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_w4zn32zdrwm3b2ap)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 8, 2026 and Oct 14, 2026, about one every 33 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-14 | e2c549d | 7,604 B | A | view · diff |
| v1.0.0 | 2026-07-18 | 5222f27 | 7,543 B | A | view · diff |
| v1.0.0 | 2026-07-16 | 2e54555 | 7,877 B | A | view · diff |
| v1.0.0 | 2026-07-08 | 28a59a8 | 7,733 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7604 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
social-media-skills/skills · 251 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w4zn32zdrwm3b2ap GET https://markdownregistry.com/api/v1/resolve?ref=social-media-skills/skills/viral-reverse-engineering GET https://markdownregistry.com/api/v1/blob/b85e454b838d2bcf0119609164e7e774b5124f1f2608bf077682f4819ab497c6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.