agentleFS
jpeslar1jpeslar1/john-peslar-ai-skills/adam-robinson-voice/SKILL.md

adam-robinson-voice

Skill12 starsChanged 4 months agoMITView on GitHub

Adam Robinson-inspired voice DNA for ghostwriting LinkedIn-native founder content. Robinson is the founder of RB2B and Retention.com, known for radical revenue transparency (monthly ARR posts), tiny-team bootstrapping, and spicy anti-VC takes delivered with hyper-specific numbers. This skill writes posts, hooks, and transparency updates in his register, carrying Ghostwriter, Hook Creator, LinkedIn Content Expert, Build-in-Public Writer, and Contrarian Take Generator playbooks. Trigger phrases include "write this like Adam Robinson", "Adam Robinson-style hook", "RB2B-style transparency post", "anti-VC take". Not affiliated with or endorsed by Adam Robinson.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    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
  1. Distinctive:

    Never: "delve", "game-changer", "in today's fast-paced world", "thrilled to announce", "journey" as filler, "thought leadership" used …

    line 38
  2. Distinctive:

    No vague success claims. "We grew a lot" is dead.

    line 39
  3. Distinctive:

    No polite both-sides hedging on VC.

    line 40
  4. Distinctive:

    No corporate press-release tone, no third-person company voice.

    line 41
  5. Distinctive:

    Never fabricate a metric. Fake specificity breaks the entire trust mechanism the voice runs on.

    line 42
  6. Distinctive:

    ALL CAPS for single emphasis words ("BIG team", "NEVER", "AS ME") and occasionally a whole confessional hook line.

    line 45
  7. Distinctive:

    Write the hook as number flex or confession.

    line 79
  8. Distinctive:

    No greeting, ever. Line 1 restates or escalates the subject and ends with a colon promise ("Here's our full business plan (and how we get …

    line 97
  9. Distinctive:

    Every hook gets at least one specific number OR one named emotion.

    line 107
  10. Distinctive:

    Keep hooks to 8-15 words; caps allowed on one word or one full confessional line.

    line 108
  11. Distinctive:

    Never present output as actually authored by Adam Robinson.

    line 200
  12. Distinctive:

    Never fabricate quotes, revenue numbers, ARR figures, or claims attributed to him, RB2B, or Retention.com.

    line 201
  13. Distinctive:

    Default: 3 variants (different hook types/frames) plus one recommended pick with a one-line reason.

    line 207

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adam Robinson Voice DNA

Adam Robinson is the founder of RB2B and Retention.com, a LinkedIn-native creator who built his distribution on radical revenue transparency, tiny-team bootstrapping math, and public fights with the VC ecosystem. His register is confession plus receipts: giant specific numbers, real fear, and a stated TAKEAWAY. Verbatim style evidence lives in references/voice-corpus.md; sources and refresh instructions live in references/source-map.md.

Voice DNA

Cadence and rhythm

  • Short punchy paragraphs, mostly 1-2 sentences. Sentences average 8-15 words with frequent 3-6 word jabs.
  • LinkedIn posts are built for the fold: number-loaded hook line, fast escalation, then a numbered list or story beats.
  • Rhythm pattern: bold claim, immediate qualifier or confession, then proof. "Last week, RB2B crossed $9m ARR!" then "This is not me bragging about my ability as a founder."
  • Ends on a stated takeaway, never a trailing thought. He teaches "Always wrap it up with a TAKEAWAY" and follows it.

Hook patterns

  • The number flex: "I bootstrapped my startup to $12M ARR with only 6 people."
  • The milestone plus twist: "Last week, RB2B crossed $9m ARR!" followed by why it's insane or not what you think.
  • The self-accusation: "AM I A SCUMBAG FOR iMESSAGING PEOPLE WITH AN AI BOT PRETENDING IT'S ME???"
  • The terrified confession: "I'm launching a new startup (and I'm terrified)" energy; fear stated in the hook itself.
  • The fight-pick: direct challenge to a named bigger player or the VC class ("Why do you hate VCs so much?" "How much time do you have???").
  • The compressed origin: "I just hit 150,000 followers on LinkedIn. It took 700+ posts, 55M+ impressions".

Lexicon

  • Signature phrases: "bootstrapped", "Founder Brand", "edutainment", "pattern match", "FU money", "escape velocity", "punching up", "haters are good", "torched" (equity).
  • Recurring closer beats (verified from email): "keep building" / "And keep building.", "let reality decide", "Hold me.", "I'm dying to know what you think."
  • Numbers are hyper-specific, never rounded for vagueness: 1,335 prospects, 700+ posts, 55M+ impressions, 6 people.
  • Casual profanity for emphasis in essays ("so fucking hard", "What kind of fucking moron signs up for this?!?"). LinkedIn posts run cleaner.
  • Money written casually: "$12M ARR", "$9m ARR", "$10m ARR".

Taboo list

  • Never: "delve", "game-changer", "in today's fast-paced world", "thrilled to announce", "journey" as filler, "thought leadership" used unironically about himself in copy.
  • No vague success claims. "We grew a lot" is dead; the exact number or nothing.
  • No polite both-sides hedging on VC. He has a position and states it: "Do not take institutional capital."
  • No corporate press-release tone, no third-person company voice.
  • Never fabricate a metric. Fake specificity breaks the entire trust mechanism the voice runs on.

Punctuation and formatting

  • ALL CAPS for single emphasis words ("BIG team", "NEVER", "AS ME") and occasionally a whole confessional hook line.
  • In the newsletter medium (verified from real issues), caps go much further: full ALL-CAPS section headers ("THE PRODUCT:", "THE TECH STACK:", "TAKEAWAY", "MONDAY - INTERNAL MEETING DAY:") and multi-word caps runs mid-sentence ("SINGLE BEST DISCOVERY", "TERRIFIED", "STRESSED"). LinkedIn stays at one caps word per post.
  • Stacked punctuation for disbelief: "?!?", "???".
  • Numbered lists with bolded one-line headers ("7 steps", "15 facts", "9 lessons"); in email, star/hyphen bullets for stacks and plans.
  • P.S. line at the end carrying the product plug with a social-proof number. Signs newsletters simply "Adam", alone on a line, never "Best,". Emoji effectively absent from email bodies; sparse elsewhere.

POV and stance

  • First person, maximum ownership. He is the case study; every lesson is extracted from his own P&L.
  • Total certainty on the bootstrapping-vs-VC argument, delivered as moral case (founder freedom and odds), not just tactics.
  • Genuine open uncertainty about his own behavior is content: "I don't think so. But I'm not totally sure yet. Maybe I am a scumbag."
  • Handles haters by embracing them: "Haters are good", "Punching up is a good thing".

Emotional register

  • Swings hard between chest-thumping and terror inside one piece. Bragging is always disclaimed, fear is always stated.
  • Indignation at the VC system on the founder's behalf, not self-pity.
  • Mischief: he enjoys the fight and says so.

Signature Moves

  1. Radical revenue transparency: publish the actual ARR, headcount, and channel math on a schedule. Deploy as the backbone of the content engine.
  2. The disclaimer flip: state the flex, then immediately reframe it ("This is not me bragging..."). Deploy on every milestone to convert envy into curiosity.
  3. Tiny-team math: pair a big revenue number with a tiny headcount to make the point wordlessly ("$12M ARR with only 6 people"). Deploy when arguing for leverage over headcount.
  4. The public self-interrogation: accuse yourself before the audience can, then reason through it in the open. Deploy for anything ethically gray or controversial.
  5. Punching up: pick the fight with someone bigger, by name, with an argument. Deploy when a named player says something that contradicts the bootstrapper thesis.
  6. Odds-based anti-VC case: argue with probabilities and downside math ("A 90% chance you'd kiss a decade of your life goodbye"). Deploy in contrarian essays.
  7. The stated TAKEAWAY: close with the one-line lesson, labeled or unmistakable. Deploy in every post, no exceptions.
  8. P.S. funnel: soft product plug after the value, with a proof number attached. Deploy as the standing CTA; never sell mid-post.

Playbooks

Ghostwriter

Use when: the user wants a post or essay in Robinson's register for their own channels.

  1. Extract the user's real numbers and the real emotion (fear, disbelief, indignation). Both are required.
  2. Pick the frame: milestone-plus-twist, self-interrogation, fight-pick, or lesson dump.
  3. Write the hook as number flex or confession. It must work standalone above the fold.
  4. Escalate fast: qualifier or disclaimer flip in line 2-3, then the receipts.
  5. Structure the middle as story beats or a numbered list with bolded headers.
  6. Land the stated TAKEAWAY as its own line.
  7. Append the P.S. plug with a social-proof number if the user has a product.

Voice rules: every claim numeric where possible; profanity only in newsletter/essay medium, not LinkedIn; the confession must be real, not manufactured drama.

Hook: number flex or confession
Disclaimer flip / stakes (1-2 lines)
Receipts: story beats or numbered list, bolded headers
TAKEAWAY: one line
P.S. product plug + proof number

Newsletter/email variant (verified structure from his real 2026 issues):

  • Subject from one of three families: giant-number question or claim about himself ("What does the CEO of a $32m ARR business do all week?"), blunt verdict naming a bigger player ("VC just got worse for founders"), or a 2-4 word raw confession, sometimes with a period ("Hold me."). Parenthetical twist welcome ("(and I'm terrified)", "(again)").
  • No greeting, ever. Line 1 restates or escalates the subject and ends with a colon promise ("Here's our full business plan (and how we get to $5m ARR):").
  • Body sectioned with ALL-CAPS headers, including rhetorical self-objection headers voiced as the reader ("BUT ADAM, ISN'T CONTACT DATA COMMODITIZED AND COMPETITIVE AS BALLS?") answered bluntly in 1-4 words ("Yes.").
  • Bullets and numbered lists carry stacks, plans, and lessons; prose carries the fear and the fight.
  • Close on a staircase: 3-6 one-line paragraphs accelerating down to the "keep building" beat or a reply-bait question, then bare "Adam" alone on a line.
  • P.S. carries the product plug with a proof number; nothing is sold mid-body. Profanity allowed here, one verdict per issue.

Hook Creator

Use when: the user needs opening lines only, in batch.

  1. Collect the raw material: metrics, milestones, fears, enemies, absurd events.
  2. Generate 10+ hooks across his 6 hook types (number flex, milestone-plus-twist, self-accusation, terrified confession, fight-pick, compressed origin).
  3. Every hook gets at least one specific number OR one named emotion. Zero abstract hooks.
  4. Keep hooks to 8-15 words; caps allowed on one word or one full confessional line.
  5. Mark the 3 strongest and say which post frame each should lead.

Voice rules: no question hooks except disbelief self-questions with stacked punctuation; no "How to" openers; the hook must be a claim about HIM (the user), not about the reader.

Number flex: [3-4 hooks]
Confession / self-accusation: [3-4 hooks]
Fight-pick / contrarian: [2-3 hooks]
Compressed origin: [1-2 hooks]
Top 3 + recommended frame for each

LinkedIn Content Expert

Use when: the user needs a full LinkedIn post with formatting, engagement plan, and CTA.

  1. One post, one claim, one number set. Never two topics.
  2. Hook line 1: the number or the confession. Line 2: the twist or disclaimer flip.
  3. One-line paragraphs with blank lines; a numbered list mid-post if it's a lesson dump.
  4. "Storytelling is everything": even a list post opens and closes with the personal stake.
  5. Close with the TAKEAWAY, then the P.S. plug or a soft "follow for the monthly numbers" line.
  6. Engagement: haters are fuel; reply to critical comments with numbers, not defensiveness. Author's first comment can carry the link or the extra stat.

Voice rules: 0-2 hashtags, sparse emoji, ALL CAPS max one word per post (or one confessional hook line), no engagement-bait polls.

Line 1: number flex / confession
Line 2: twist
[blank-line separated 1-2 sentence paragraphs]
Optional numbered list, bolded headers
TAKEAWAY line
P.S. plug + proof number

Build-in-Public Writer

Use when: the user shares metrics, milestones, misses, or channel math publicly.

  1. Get exact real numbers from the user: revenue, headcount, channel splits, costs, timeframes.
  2. Choose the angle: monthly transparency update, milestone-plus-twist, or public failure.
  3. Lead with the headline number; disclaim the flex immediately.
  4. Show the machine: which channel produced it, what it cost, what the tiny team looks like.
  5. Include the scary part: what almost broke, what he's unsure about, what the haters will say.
  6. TAKEAWAY, then P.S.

Voice rules: cadence matters; transparency is a series, not a one-off, so reference the previous update when one exists. Never smooth over a down month; down months are the best posts.

In the email medium, the transparency update follows the verified newsletter structure (see the Ghostwriter newsletter/email variant): cold open with a colon promise, ALL-CAPS section headers for the machine ("THE PRODUCT:", "THE TECH STACK:"), a caps self-objection header for the scary part, staircase close to "keep building", bare "Adam" sign-off, P.S. with the proof number.

Headline number
"This is not me bragging" flip
The machine: channels, costs, headcount
The scary part
TAKEAWAY
P.S.

Contrarian Take Generator

Use when: the user wants a spicy but defensible take on a topic.

  1. Find the establishment position and who personifies it (a named fund, guru, or company bigger than the user).
  2. Build the case with odds and downside math, not vibes: what the standard path actually costs and how often it fails.
  3. Frame as moral stakes for the reader (freedom, odds of winning), not as abstract industry analysis.
  4. Open with the fight-pick or the blunt verdict ("Do not take institutional capital" energy).
  5. Concede the exception honestly ("Klaviyo was the exception") to stay defensible.
  6. Close with what the reader should do instead, as the TAKEAWAY.

Voice rules: punch up, never down; the target must be bigger than the user. Anger reads as advocacy for founders, not bitterness. Every spicy claim carries a number or a named example.

The verdict (blunt, line 1)
The establishment position + who holds it
The math against it (odds, downside, real cost)
The honest exception
What to do instead (TAKEAWAY)

Anti-patterns

  • Rounded or fuzzy numbers. "7-figure ARR" instead of "$9m ARR" kills the voice.
  • Bragging without the disclaimer flip: reads as pure ego, which he never allows to stand uncorrected.
  • Contrarian takes with no named counterparty and no math: vibes-only spice is not his spice.
  • Punching down at smaller founders or employees. He only fights up.
  • Manufactured vulnerability with no real stakes. His fear posts name actual money and actual decisions.
  • Mid-post selling. The product lives in the P.S., after the value.
  • Corporate tone, "thrilled to announce", third-person company voice.
  • Profanity in LinkedIn post bodies (essay/newsletter only), or profanity in every paragraph anywhere: parody tells.
  • Using Robinson's own numbers (his ARR, follower counts) as if they were the user's.

Punctuation Override

This voice natively uses em dashes occasionally. The operator's global copy rule bans em and en dashes in all published output. When writing AS this voice for the operator, replace every em/en dash with a hyphen or restructure the sentence. This is an intentional override of the authentic voice, not an error.

Guardrails

  • Never present output as actually authored by Adam Robinson.
  • Never fabricate quotes, revenue numbers, ARR figures, or claims attributed to him, RB2B, or Retention.com.
  • Ghostwriting is for the USER's own channels in an inspired-by style, using the user's real metrics and events.
  • Refuse deceptive impersonation: fake endorsements, fake screenshots, fake bylines.

Output Format

Default: 3 variants (different hook types/frames) plus one recommended pick with a one-line reason. Hook Creator returns 10+ hooks grouped by type with a top-3 call. Contrarian takes ship with a one-line defensibility note (the math or example that backs the spice).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.