instagram-virality-insights
Skill1 starsChanged 3 months agoMITView on GitHub
Distilled virality and retention mechanics for short-form data reels (open cognitive loops, stakes/urgency framing, share psychology, duration bands, frame-0 mechanics) with measured 2026-08 evidence. Use when designing new reel concepts/series, judging why a reel or account travels or stalls, or pressure-testing an episode idea before production. Optional live-recon appendix for gathering fresh evidence. Not for production ship-gates (high-retention-insight-reels-instagram owns those) or offline .mp4 review.
In this repository47 other files it gives its agents.
- data-apache-lakehouseSkill
- data-apiSkill
- dataSkill
- data-duckdbSkill
- data-identity-resolutionSkill
- data-pipeline-operationsSkill
- data-pokemon-tcg-foundationsSkill
- data-product-evalSkill
- data-reelsSkill
- data-semantic-qualitySkill
- data-table-lifecycleSkill
- html-designSkill
- ebay-listingSkill
- flutter-pro-ux-reviewSkill
- flutterSkill
- browser-testing-with-devtoolsSkill
- browser-verifySkill
- design-systemSkill
- frontend-designSkill
- mobile-app-echarts-visualSkill
- mobile-blog-chart-visualSkill
- mobile-chart-visualSkill
- mobile-product-uxSkill
- mockup-implementSkill
- product-designSkill
- product-ui-craftSkill
- prototypeSkill
- react-performanceSkill
- ui-exploreSkill
- visual-verifySkill
- web-qualitySkill
- high-retention-insight-reels-instagramSkill
- instagramSkill
- marketing-cashvertisingSkill
- marketing-contagiousSkill
- marketing-going-viralSkill
- marketingSkill
- marketing-offersSkill
- marketing-storybrandSkill
- quality-checkSkill
- elements-of-styleSkill
- style-clarity-graceSkill
- writer-styleSkill
- writing-docsSkill
- writing-proseSkill
- writingSkill
- writing-technicalSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 76
OPTIONAL: Use only when fresh evidence is needed, not routinely — recon findings decay and one session's sample is directional, not proof.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Instagram Virality & Retention Insight Quality
Core law: the open cognitive loop
Reels travel when frame 0 opens a question the brain must chase; they stall when frame 0 is resolved. Confrontation (belief attack) is one loop type, not the only one. A finished chart = no loop = the measured 0.003–0.09 v/f band (CardLadder/GemRate).
| Loop family | Mechanic |
| Belief attack | "You're wrong about X" |
| Unresolved wager | Outcome revealed at the end |
| Closing window | Urgency / deadline |
| Rank churn | Race, winner hidden |
| Scale violation | True-size "whoa" |
| Crisis / news | "What happens to us now?" |
Evidence table (2026-08, measured)
| Who | Size | Result | Mechanic |
| thecardscience | 56.6K | 135K views in 3 days | Price dashboard + "discounts don't last forever" urgency |
| thecardscience (same acct) | 56.6K | 2.2M pinned | Target-cancels-Pokemon crisis news |
| legalrips | 693 followers | 1.2–5K every reel | Real-money coinflip resolving on camera |
| card_dons | — | 515 comments / 184 reposts | Directive covers ("BUY THIS AVOID THAT") |
| chartosaur | 239K | 47–149K consistent, zero flops | Template-consistent tension, 14–20s |
| onlyslabs.io | 15 followers | 5–162 views | Negative control — slab data, no stakes |
| Silph July batch | — | 12/21 confrontation-worded hooks died at ~150–215 views | Wording ≠ mechanism; frame-0 visuals were calm |
| Silph Gengar (Jul 23) | 32 fol | 1,687 views, 11 shares, 99.3% non-followers | Unresolved set fight on cover (DIDN'T CRASH); cascade proofs |
| Silph gold-delta (Aug 26) | 32 fol | 7–145 views with send-asks + WRONG stamp | Resolved cover — punchline on the thumbnail |
Retention mechanics (ranked by evidence strength)
- Duration — 12–25s for data reels; 31s+ = measured losing band. Length never fixes a resolved open.
- Familiar-entity-first — a recognizable card/entity IS a hook before any claim text.
- Payoff cadence — ~3–5s; text cards that ARE the story ≠ dead air. True dead air = logo stings / empty wipes.
- Loop seam — last ~2s should visually rhyme with first ~2s (replays count as watch time).
- Data as evidence inside a story with stakes, never as the subject.
Share/save psychology
- Sends-per-reach is the top expansion signal (Mosseri-confirmed). This is a caption-layer pattern (Youshaei hook-body-send-ask; Mosseri sends-per-reach), not a VO pattern — the send-ask is mandatory but lives in the caption (and optionally a pinned comment), never spoken or on-screen in the final beat.
- Recipient-named send-asks ("send this to the friend who still…") beat quota asks, and beat polls (polls → comments = weakest lever).
- Saves come from a portable rule or reference numbers held static ~2s.
- Directive framing ("buy this, avoid that", "hold three years") gets reposted; observations don't.
- Identity/debate bait (era vs era, which side are you on) drives tagging.
Escaping the test pool (small accounts)
- Scoring is per-video, not per-account: the first pool measures skip + sends + completion regardless of follower count.
- Engineer one save reason AND one share reason into every reel.
- Trial Reels need 1,000+ followers — check before recommending.
- Collab leverage: data brands travel by powering a personality's reel (double.holo pattern) — SilphCo-as-source is a valid distribution play.
Anti-patterns
Resolved frame 0 (calm green stat) · analytics as subject · poll-only CTA ·
30s data recaps · polish iterations inside a dead template · judging hooks by wording without checking the muted frame-0 visual.
Optional appendix: live recon protocol
OPTIONAL. Use only when fresh evidence is needed, not routinely — recon findings decay and one session's sample is directional, not proof.
Goal
Find organic winner Reels on live Instagram outside the follow graph, vet whether a view count is real (v/f) or a fluke, and extract the frame-0 mechanic + CTA driving it.
Protocol
| Step | Action |
| 1. Keyword search | Open https://www.instagram.com/explore/search/keyword/?q=<query> — top results are IG's own ranking for the topic, not the follow graph |
| 2. Open winner reels | Click into top results, note the account |
| 3. Vet the account | Open /<handle>/reels/, read "View Count Icon" values vs follower count. Consistent v/f >1 at small scale beats one outlier |
| 4. Extract frame-0 | Screenshot frame-0 of winners (that IS the muted scroller's view); read caption/comments for CTA + debate patterns |
| 5. Negative controls | Also record stuck accounts (data-without-stakes accounts sitting at 5–200 views) — these disprove "just post data" |
Practical notes
| Note | Why it matters |
| Web Insights hide skip/watch-time | Only the mobile app exposes those; web/desktop shows views/interactions/shares/saves |
| Grid views are lifetime, not recent | Check post dates before treating a view count as fresh signal |
| Snapshots may need a 3–4s wait | Let the reel render before screenshotting frame-0 |
Feed (/reels/) is mostly general-viral | Search beats feed for niche recon |
| Don't interact | No likes/follows — keep the account's graph clean for repeat recon |
Findings template
| account | followers | view band | outlier | frame-0 mechanic | CTA type |
Relationship to other skills
| Skill | Role |
| high-retention-insight-reels-instagram | Consumes these mechanics for create/review/rank; owns offline .mp4 storyboard review and ship-gates |
| instagram (hub) | Routes here for concept design and why-it-travels judgments |
| marketing-going-viral | Multi-platform Gold/Silver/Bronze research, not Instagram-specific |
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.

