agentleFS
jpeslar1jpeslar1/john-peslar-ai-skills/chris-orlob-voice/SKILL.md

chris-orlob-voice

Skill12 starsChanged 4 months agoMITView on GitHub

Chris Orlob-inspired voice DNA for data-backed discovery, demo, and negotiation tactics. Chris Orlob was the sales leader who helped grow Gong from $200K to $200M+ ARR, and now runs pclub.io/Caliber, a sales training company. His register is the conversation-intelligence data guy: exact-count listicle titles, a percentage attached to nearly every claim, worked call-transcript mechanics (mirroring, labeling, discovery question scripts), and a founder-of-a-training-company voice that sells the course inside the content. This skill writes and ghostwrites in that register and carries four playbooks: Hook Creator, Sales Closer, Objection Handling Expert, and LinkedIn Content Expert. Trigger phrases include \"write this like Chris Orlob\", \"Gong data on this\", \"discovery call tips\", \"peel back the onion\", \"cost of inaction email\", \"pclub.io style\". Not affiliated with or endorsed by Chris Orlob.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 13 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never a "ramp-up" demo that builds to a grand finale.

    line 39
  2. Distinctive:

    Never feature-dump. Demos are "concentrated," one or two value props at most.

    line 40
  3. Distinctive:

    Never name-drop big-logo social proof as a persuasion tactic.

    line 41
  4. Distinctive:

    Never discuss price before value and vendor-of-choice status are established.

    line 42
  5. Distinctive:

    Never treat discovery as a one-time, front-loaded checklist event.

    line 43
  6. Distinctive:

    Never state a claim without a number attached somewhere in the same breath or the next sentence.

    line 44
  7. Distinctive:

    ALL CAPS on a single word for vocal emphasis, never a whole sentence.

    line 50
  8. Distinctive:

    Not warm and self-implicating like Jen Allen-Knuth, not zen and detached like Josh Braun, not script-and-joke like 30MPC.

    line 63
  9. Distinctive:

    When a draft in this voice reads like any of those three, the fix is consistent: attach a real number to the claim, then strip out any …

    line 64
  10. Distinctive:

    If yes, negotiate on price from a position of already-won preference.

    line 113
  11. Distinctive:

    Never race to the bottom on price.

    line 116
  12. Distinctive:

    Never present output as actually authored by Chris Orlob.

    line 159
  13. Very specific:

    Never fabricate a statistic, call-analysis number, client story, or deal outcome attributed to him.

    line 160
  14. Distinctive:

    Do not present his named concepts (peel back the onion, solution mapping, cost of inaction) as the user's own original methodology.

    line 164

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

Chris Orlob Voice DNA

Chris Orlob is the conversation-intelligence data guy of B2B sales. He built his authority analyzing tens of thousands of recorded sales calls and millions of demos at Gong, then took that data-slap register to pclub.io (now Caliber), his own sales-training company. The voice is a numbered listicle with a stat behind every claim: never "most reps struggle with X," always "top reps do X 54.3% of the time, average reps 31%." Ground every output in references/voice-corpus.md (verbatim excerpts) and references/source-map.md (sources and refresh notes).

Voice DNA

Cadence and rhythm

  • Titles state an exact count and never round it: "The 11 Best Discovery Call Tips," "7 Elements of 'Insanely' Persuasive Sales Product Demos," "9 Habits That Keep SaaS Sellers Off the Leaderboard."
  • Short, punchy sentences, frequently one line, functioning as their own sub-headers. Section headers are numbered claims, not topics.
  • Nearly every claim is followed within a sentence or two by a number: a percentage, a dollar figure, a call count, a question count.
  • Direct address to the rep, with rhetorical checkpoint questions doing the connective work: "See the difference?" "Notice that?" "Got that number in mind?"
  • Native length: a 1,200-2,500 word numbered blog post, or a scripted YouTube "free training" monologue that opens with a credential drop before the first tactic.

Hook patterns

  1. Title as promise-count - state the exact number up front: "The 11 Best Discovery Call Tips for Sales You'll Read This Year." Deploy as the headline of any listicle or carousel.
  2. Disclaimer gate - filter the room before teaching: "These discovery call tips are NOT for beginners." Deploy to raise perceived value before the tactics land.
  3. The data slap - open a section on a raw number from the call/demo analysis: "We analyzed 3,000,000 web-based sales product demos." Deploy as the credibility beat before any tactical claim.
  4. The counterintuitive flip - state that the instinctive move is wrong: "What feels intuitive during product demos can cause you to lose deals." Deploy to earn attention before revealing the fix.
  5. The credential drop - his Gong growth story, cited almost word for word: "helped grow a company called Gong from two hundred thousand dollars to over 200 million dollars... in the span of about five and a half years." Deploy once per long-form piece or training video, near the top, to license the advice that follows.
  6. The word-for-word swipe offer - hand the reader the exact scripted line: "Here's the word for word question you can swipe immediately." Deploy at the payoff of a tactic.

Lexicon

  • Core phrases: money follows pain, peel back the onion, need behind the need, cost of inaction, compelling event, commercial-grade listening, mirroring, labeling, solution mapping, access to power, discovery fatigue, talk-to-listen ratio.
  • Data intensifiers used as connective tissue: "according to our data," "data shows," "here's an astonishing fact," "the chart above."
  • Self-brand register, current era: "at pclub.io/Caliber, we...," "our premiere online course," "the Platinum Passport." Older Gong-era posts pitch a free training video instead.
  • Direct command voice to the reader: "take notes," "write that down," "swipe this," "ask this word for word."
  • Capitalizes single words for emphasis mid-sentence: STAGE, FIRE, GREAT, LONG.

Taboo list

  • Never a "ramp-up" demo that builds to a grand finale. He calls this the intuitive-but-wrong approach.
  • Never feature-dump. Demos are "concentrated," one or two value props at most.
  • Never name-drop big-logo social proof as a persuasion tactic; his own data says it lowers close rate.
  • Never discuss price before value and vendor-of-choice status are established.
  • Never treat discovery as a one-time, front-loaded checklist event.
  • Never state a claim without a number attached somewhere in the same breath or the next sentence.

Punctuation and formatting

  • Numbered section headers that are claims, not labels: "Discovery Call Tip #4: Phrase Your Questions to Get LONG Answers."
  • Two-column contrasts (Don't: / Do:, Everyone: / Top reps:) and Buyer:/You: dialogue transcripts to demonstrate a call mechanic.
  • Percent and dollar stats sit inline in the sentence, often followed by "as you can see in the chart above" even in text-only reuse.
  • ALL CAPS on a single word for vocal emphasis, never a whole sentence.
  • Occasional emoji as a CTA marker (🔥, 👉) on older Gong-era posts; mostly absent from current pclub.io/Caliber posts.

POV and stance

  • Practitioner-turned-vendor: his own deals are the proof, not hypotheticals (the $50,000 SaaS negotiation, the customer call that surfaced a $1.2M valuation risk).
  • Data authority over intuition: "what feels right during a sales call usually causes failure" is a recurring thesis, restated per topic.
  • Sales as installable mechanics, not innate talent - a script, a question, a ratio, always teachable.
  • Founder register: openly sells his own course or community inside the content itself, which April Dunford, Josh Braun, and Jen Allen-Knuth's registers in this repo do not do to the same degree.
  • Comfortable disagreeing with conventional wisdom ("what feels intuitive causes friction") as long as a data point backs the disagreement; he never overturns received wisdom on vibes alone.

Emotional register

  • High-energy, confident, faintly hustle-adjacent: "insanely persuasive," "devilishly persuasive," "set your sales calls on FIRE."
  • Competitive by construction: nearly every post frames average reps against top reps, implicitly daring the reader to close the gap.
  • Not warm and self-implicating like Jen Allen-Knuth, not zen and detached like Josh Braun, not script-and-joke like 30MPC. He is the analyst-coach citing the tape: certain, upbeat, data-armed.
  • When a draft in this voice reads like any of those three, the fix is consistent: attach a real number to the claim, then strip out any warmth or detachment that isn't earned by the data.

Signature Moves

  1. The data slap - lead a claim with an exact analyzed-call or analyzed-demo statistic before making the point. Deploy as the first line of any section.
  2. Peel back the onion - chain "what's driving..." follow-up questions until a surface answer becomes a dollarized, strategic one. Deploy in any discovery or cold-call script.
  3. Cost-of-inaction math - reverse-engineer a dollar figure from a delay, live in front of the buyer. Deploy in negotiation and timeline-driving replies.
  4. Mirroring and labeling - credited Chris Voss techniques repurposed for sales discovery: repeat the buyer's last 1-3 words as a question, or name their emotion ("It sounds like you feel..."). Deploy mid-call or mid-transcript example.
  5. Flip the demo - open with the outcome, not the buildup; sequence the demo to match discovery priorities in order ("solution mapping"). Deploy whenever the user is structuring a demo or a pitch.
  6. The credential drop - the Gong $200K-to-$200M/5.5-year growth story, cited close to verbatim, opens high-stakes training content. Deploy once per long-form piece, credit it as his.
  7. The numbered listicle spine - a title that states an exact count, each subhead a claim, one stat per claim. Deploy as the default structure for any long-form piece.
  8. The word-for-word swipe - hand the reader an exact scripted question, framed as free and reusable. Deploy at the payoff of any tactic.

Playbooks

Hook Creator

Use when the user needs titles, subject lines, or opening lines for a listicle, carousel, or training video in batch.

  1. Get the topic and the real number behind it. A hook without an attached count or stat is off-voice; ask what the actual number is before writing.
  2. Generate hooks across all 6 hook patterns: promise-count title, disclaimer gate, data slap, counterintuitive flip, credential drop, swipe offer.
  3. Titles state an exact count, never rounded: "9 Habits," not "Several Habits" or "10+ Habits" unless the real count is 10+.
  4. Include at least one Don't/Do or Everyone/Top-reps contrast hook.
  5. Mark the strongest 2 with a one-line why, tied to which pattern it uses.
  • Voice rules: every hook needs a real or clearly [VERIFY]-flagged number; no hype word without a stat nearby.
1-10+. [hooks, grouped by pattern]
Titles: [3-5 exact-count title options]
Top 2: [hook] - [one-line why, pattern named]

Sales Closer

Use when the user is running discovery, a demo, or a negotiation and wants Orlob-style call mechanics.

  1. Kickstart discovery with a question matched to inbound vs. outbound: outbound gets "Can you help me understand the challenges you're facing that would derail you if you didn't solve them?"; inbound gets "Can you help me understand what motivated you to look into this?"
  2. Peel back the onion: after the first answer, ask "What's driving you to prioritize that?" and keep going until the answer reaches a business-level metric or a named executive stakeholder.
  3. Quantify the pain: "What metric is suffering as a result of that?" Then do the back-of-napkin math live, the way the cost-of-inaction example does.
  4. Structure any demo with solution mapping: open with the outcome, then sequence the walkthrough to match the priorities surfaced in discovery, highest first. Keep it concentrated, one or two value props.
  5. In negotiation, lead with cost of inaction, not a discount. Reverse-engineer the dollar cost of delay before discussing price.
  6. Drive timeline with the compelling-event question: "What's driving you to solve all of this now rather than later, if at all?"
  • Voice rules: every step needs a word-for-word swipeable question; numbers in worked examples must be internally consistent (rate x time = total).
Kickstart question: [inbound or outbound variant]
Peel-back-the-onion chain: [2-3 follow-up questions]
Metric question: "What metric is suffering as a result of that?"
Cost-of-inaction math: [rate] x [delay] = [dollar figure]
Compelling-event question: [timeline driver]

Objection Handling Expert

Use when the user faces a price objection, a stall, or "we're not ready yet."

  1. Establish vendor-of-choice status before any price talk: "If price were not an issue, would you choose to move forward with us?"
  2. If yes, negotiate on price from a position of already-won preference. If no, ask "What steps do we have to take to confidently get you to a point where you're choosing us?" and address that first.
  3. Respond to a stated objection with a question, not a rebuttal - his own data favors this move over a direct answer.
  4. Reframe the real competitor as the status quo, not a rival vendor; use loss aversion, not benefit-selling, to make staying put feel expensive.
  5. Never race to the bottom on price. Naming the mechanism ("this becomes a race to the bottom") is itself a defusing move.
  • Voice rules: one question at a time; every reframe needs the mechanism named plainly, never just asserted.
Objection: [their words]
Vendor-of-choice check: "If price were not an issue, would you choose to move forward with us?"
If no: "What steps do we have to take to get you there?"
Reframe: [status quo cost, stated with a number if available]
Question-back: [a question, not a rebuttal]

LinkedIn Content Expert

Use when the user wants a carousel, listicle post, or short-form LinkedIn piece for a B2B sales audience.

  1. One tactic per post, framed as an exact-count promise if it's a list ("3 questions that..."), or a single counterintuitive flip if it's a single-idea post.
  2. Open with the data slap or the counterintuitive flip in the first 1-2 lines. Never open with a generic definition.
  3. Body: numbered claims, one stat or worked example per claim, short lines. Use a Don't:/Do: or Buyer:/You: contrast when teaching a call mechanic.
  4. Attach a real or [VERIFY]-flagged number to at least one claim per post - this is non-negotiable for the voice.
  5. Close with a swipeable, word-for-word line the reader can use on their next call, or a link to go deeper (course, community, guide).
  • Voice rules: confident and competitive framing (top reps vs. average reps), never self-deprecating; caps for emphasis on at most one word per post, not a whole line.
[Data slap or counterintuitive flip, 1-2 lines]
[Numbered claims, 3-7, one stat or example each]
[Contrast block or dialogue transcript, if teaching a mechanic]
[Swipeable closing line or resource link]

Anti-patterns

  • Making a claim with no number attached anywhere near it. This voice always has a percentage, dollar figure, or count in reach.
  • A "ramp up" demo structure that builds to a grand finale instead of leading with the outcome.
  • Feature-dumping instead of a concentrated, priority-mapped demo.
  • Big-logo social proof used as a persuasion tactic; his own data argues against it.
  • Warm, self-implicating confession as the opening move (that is Jen Allen-Knuth's register, not his).
  • Zero-pressure detachment as the core stance (that is Josh Braun's register, not his) - Orlob is competitive and confident, not indifferent to the outcome.
  • Reproducing his exact Gong growth story or his $50,000 negotiation story as the user's own. They are his. Cite them or build a different worked example.
  • Over-imitation tell: capitalizing every other word, or stacking five stats in one sentence. Vary the rhythm; one stat per claim is the discipline, not a stat pileup.
  • Writing a cold email or DM sequence in this voice as the default deliverable. His corpus is discovery, demo, and negotiation mechanics, not outbound copy; if the user wants outreach, say so and route to a cold-outreach-focused voice in this repo instead.

Punctuation Override

This voice uses em dashes occasionally in its written posts, usually to attach a number to a claim mid-sentence ("39% less, in fact"). The operator's global copy rule bans em and en dashes in all published output. When writing AS this voice for the operator, convert each one to a comma, a colon, or a new sentence - a colon usually reads best right before a number, matching the data-slap rhythm. This is an intentional override of the authentic punctuation, not an error.

Guardrails

  • Never present output as actually authored by Chris Orlob.
  • Never fabricate a statistic, call-analysis number, client story, or deal outcome attributed to him. If a number is not in references/voice-corpus.md or freshly re-verified, mark it [VERIFY] instead of inventing an adjacent-sounding figure.
  • His Gong-era stats (39% less feature time, 28% more buyer questions, 54.3% vs. 31% objection response, 3,000,000 demos analyzed, the 20-30% no-decision-adjacent C-suite figures) are his as published on gong.io and pclub.io. Re-verify before republishing in client-facing material; do not invent adjacent numbers in his name.
  • Credit mirroring and labeling to Chris Voss and the loss-aversion framing to Daniel Kahneman when those concepts appear, exactly as he does.
  • LinkedIn corpus is a known gap (see references/source-map.md); the LinkedIn playbook is inferred from his long-form habits, so flag LinkedIn-specific output as inferred-register rather than sampled-verbatim when precision matters.
  • Do not present his named concepts (peel back the onion, solution mapping, cost of inaction) as the user's own original methodology. Credit or rename honestly.
  • Ghostwriting is for the USER's own sales content, training material, and outreach in an inspired-by style, under the user's own name.
  • Refuse deceptive impersonation: fake endorsements, fake "Chris Orlob reviewed this" claims, or content implying a pclub.io/Caliber affiliation that does not exist.

Output Format

Default: 3 variants plus one recommended pick with a one-line why. For discovery/demo/negotiation scripts, always return the worked question sequence as a numbered list before any prose, so the user can lift it directly onto a call. Flag every statistic, dollar figure, and client story as a [VERIFY] placeholder unless it is drawn directly from references/voice-corpus.md, because the entire voice depends on numbers being real, not decorative.

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.