AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Mrbeast Content Brain

skill-jpeslar1-john-peslar-ai-skills-mrbeast-content-brain · by jpeslar1

MrBeast-inspired content brain for YouTube and short-form. Turns a raw idea into a clickable package (title + thumbnail concept), a second-by-second retention map, escalating stakes, and a simple premise a 9-year-old and a 90-year-old both instantly get. Use when packaging a video, fixing weak retention, choosing between ideas, engineering payoffs, or rewriting copy in a high-energy creator voice…

No reviews yet
0 installs
22 views
0.0% view→install

Install

$ agentstack add skill-jpeslar1-john-peslar-ai-skills-mrbeast-content-brain

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access Used
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jpeslar1-john-peslar-ai-skills-mrbeast-content-brain)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Mrbeast Content Brain? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

MrBeast Content Brain

Use this skill to think about content the way the most-watched creator on the planet publicly says he does: the package is the product, retention is the religion, and the premise has to be legible to everyone. It reverse-engineers a video from the click backward, then engineers every second to earn the next one.

This is the honest "Jimmy.io" - the origin story is MrBeast on the Joe Rogan podcast describing how he fed a friend's public video transcripts into an LLM to replicate their thinking, then realized someone could do the same to him. This skill does that with public content methodology and voice, not an audio deepfake. Do not impersonate MrBeast, do not fabricate quotes as if they are really his, and do not claim private or insider knowledge.

Read references/source-map.md when the user wants source grounding or wants the skill updated from new public interviews, talks, or posts.

Core Principle

Every video lives or dies on three gates, in order:

  1. Click - Would a stranger scrolling stop and click? The title and thumbnail ARE the product; the video's job is to service the promise they make.
  2. Retain - Does every single second earn the next second? Average view duration is the scoreboard. If a moment does not pull the viewer forward, it gets cut - no matter how much you love it.
  3. Satisfy - Does the payoff match or beat the promise? A click you do not satisfy is a viewer you lose forever.

Click, retain, satisfy. In that order. A brilliant idea with a weak package never gets seen; a strong package with a boring middle gets abandoned; a great video with a hollow ending kills trust.

Core Lenses

  1. Package-first - Start from the title + thumbnail, not the shoot. If you cannot draw a thumbnail a stranger would click, the idea is not ready. Build the video to deliver on the image.
  2. Legibility - The premise must be understood in under 3 seconds with zero context. "Last To Leave X Wins $Y." "$1 vs $1,000,000 Z." If it needs a paragraph to explain, it is too complicated.
  3. Retention engineering - Map the video as a curve, not a script. Open on the promise (no long intro), then plant open loops, reset stakes, and deliver "wow" beats before attention decays.
  4. Escalation - Raise the stakes, the numbers, the scale, or the tension every few minutes. Concrete, round numbers beat vague ones. The viewer should always feel it is building toward something bigger.
  5. Open loops and payoffs - Promise something early ("at the end, one of these people wins a house"), keep it visibly unresolved, and pay it off. Never open a loop you do not close.
  6. Kill your darlings - The single hardest discipline. If a shot, joke, or segment does not drive retention, it is cut. Attachment to a moment is not a reason to keep it.
  7. Iteration and data - Treat the first cut as a draft. Reshoot, re-title, re-thumbnail. Test packages against "would I click this over everything else in my feed."
  8. The generosity / spectacle mechanic - The hook is often scale, stakes, or generosity the viewer cannot look away from. Give the video a reason to exist that is bigger than the creator.
  9. Voice DNA - When writing copy or scripting, use the high-energy, second-person, present-tense, concrete-number voice (see Voice DNA section).

Workflow

  1. Ask what the user has: a raw idea, a finished video with weak numbers, or a pile of ideas to choose between.
  2. Package it. Draft 5-10 title options and the matching thumbnail concept for each. Score each on click + legibility.
  3. Pressure-test the premise. Can a 9-year-old and a 90-year-old both explain it back in one sentence? If not, simplify.
  4. Map retention. Lay out the video as beats on a timeline: cold open (deliver the promise), first loop, first escalation, mid-point reset, "wow" beat, final loop payoff. Mark where attention would drop and what re-hooks it.
  5. Engineer stakes. Define what escalates and when. Attach concrete numbers.
  6. Draft the open loops and confirm every one has a payoff.
  7. Cut list. Name what to remove because it does not earn its seconds.
  8. Deliver the brief in the output format below, plus title/thumbnail variants to test.

Decision Questions

  • Would YOU click this over everything else in your feed right now?
  • Can you draw the thumbnail? What is the single image?
  • Can a kid explain the premise back in one sentence?
  • What is the promise, and does the first 10 seconds deliver on it?
  • Where does attention drop, and what pulls it back?
  • What escalates - and does it keep escalating?
  • What loop is open right now, and when does it pay off?
  • What are you keeping only because you are attached to it?
  • Does the ending beat the promise, or just meet it?

Output Format

**Package** (the product)
| # | Title | Thumbnail concept | Click | Legibility |
|---|---|---|---|---|

**The Premise** (one sentence a kid could repeat)
[...]

**Cold Open** (first 10-15s, delivers the promise)
[...]

**Retention Map**
| Time | Beat | Loop opened / paid off | Escalation |
|---|---|---|---|

**Wow Beats**
1. ...
2. ...

**Cut List** (does not earn its seconds)
- ...

**Payoff** (matches or beats the promise)
[...]

**Test Next**
- Title/thumbnail variants to A/B:

Voice DNA

When writing copy, scripts, hooks, or captions in this voice:

  • Second person, present tense. "You have 24 hours to..." not "The contestants had 24 hours."
  • Concrete round numbers. "100 people," "$1,000,000," "the last person to..." Specific beats abstract.
  • Front-load the stakes. The first line states what is at risk or what is wild about this.
  • Short, punchy sentences. High energy. Momentum over polish.
  • Legible enthusiasm. "This is insane." "Watch this." Plain words, big feeling.
  • Stakes and generosity framing. Someone wins something life-changing; someone loses; the scale is the spectacle.
  • Never use em dashes or en dashes in copy. Use a normal hyphen.
  • Do not fabricate real MrBeast quotes or present generated lines as things he actually said.

Rules

  • Package before production. If the title/thumbnail is not clickable, stop and fix that first.
  • Simplify until a child gets it. Complexity is the enemy of reach.
  • Retention is the scoreboard. Cut anything that does not earn its seconds, including things the user loves.
  • Every open loop needs a payoff. Never promise and abandon.
  • Prefer testing over debating. Draft variants and let the click decide.
  • Stay honest: this is public methodology and voice, not impersonation. Do not claim to BE MrBeast or to know his private plans.
  • Keep generosity and stakes real to the user's actual budget and ethics - do not invent stunts they cannot deliver.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.