Install
openclaw skills install bookforge-cold-email-writerWrite a complete cold prospecting email — subject line, body, and send-time recommendation — using Blount's AMMO planning framework and Hook-Relate-Bridge-Ask body structure from Fanatical Prospecting. Trigger this skill when you need to: - Write a cold email, prospecting email, or sales introduction email - Write an email to a prospect you have never contacted before - Improve an existing prospecting email that is not getting replies - Apply the AMMO framework (Audience / Method / Message / Outcome) to email planning - Build a Hook-Relate-Bridge-Ask email body that converts - Fix a subject line that is too long, uses a question mark, or is getting ignored - Check an email against the Three Cardinal Rules: Get Delivered / Get Opened / Get Converted - Improve email open rate, reply rate, or click-to-response conversion - Write a subject line under 50 characters with an action word, not a question - Understand what spam trigger words to avoid in a prospecting email - Run an email deliverability pre-check before sending - Write a post-trigger-event email to a prospect who just changed jobs, raised funding, or announced growth - Write a new-territory introduction email to a segment you have never contacted - Produce a complete send-ready email draft the user can send as-is or edit minimally - Apply the "AMMO email", "three cardinal rules email", or "Hook-Relate-Bridge-Ask" frameworks - Increase reply rate or reduce the number of cold emails going unanswered - Understand why "Hi [Name], I was browsing LinkedIn" emails get deleted immediately NOT for: building the core WIIFM bridge and because message nucleus that feeds this email (use prospecting-message-crafter first), or setting the email objective before writing (use prospecting-objective-setter). This skill produces a complete, send-ready email — not just the message component.
openclaw skills install bookforge-cold-email-writerYou need to send a cold prospecting email to a prospect — and you want it to actually get a reply.
The average business executive receives 200+ emails per day (Harvard Business Review). Your email will be scanned in under three seconds. It will be deleted unless the subject line is compelling, the opening sentence is about the prospect (not you), and the body answers one question: What's in it for me?
This skill writes the complete email — subject line through closing ask — using three interlocking frameworks from Blount's Fanatical Prospecting:
This skill is downstream of two dependencies:
prospecting-objective-setter — defines what you are asking for (appointment / info / referral / close)prospecting-message-crafter — builds the bridge and WIIFM nucleus that feeds the email bodyIf you have not run those skills, this skill will gather the required context itself. The AMMO plan subsumes both.
Before writing, gather (or ask the user for):
Required:
Helpful (read from working directory if available):
icp.md — ideal customer profile with decision-maker roles and pain pointsvalue-prop.md — your value proposition and strongest client outcomesprospect-notes.md — any research on this specific prospectcurrent-draft.md — an existing email draft to diagnose and improveDefaults: If no files are provided, the skill asks the user directly. Two to three sentences about the prospect and what you sell is enough to begin.
WHY: Most prospecting emails fail because the sender skipped planning. A good email begins with a clear plan, not a blank subject line. AMMO prevents generic outreach that wastes time and burns sender reputation.
Answer the four AMMO questions before writing:
A — Audience
M — Method
M — Message
O — Outcome
Output of Step 1: A four-line AMMO summary that shapes every word of the email.
WHY: An email that reaches the spam folder converts at zero. Deliverability failures are silent — the prospect never sees the message and you never know why. Run this check before writing a single word of body copy.
Run through the deliverability checklist. Each item is binary pass/fail:
references/spam-trigger-wordlist.md for the full list. Key offenders: free, amazing, guaranteed, 100% guaranteed, do it today, increase sales, cash, save $, act now, click here, ALL CAPS, excessive exclamation pointsIf any item fails, fix it before proceeding.
WHY: The subject line is the gatekeeper. More than 50% of emails are opened on mobile, where the subject line is often the only thing visible. Subject lines over 50 characters see exponentially lower open rates. The three most common subject line mistakes — too long, contains a question, generic/impersonal — all send the email to the delete pile before the prospect reads a word.
Subject line rules:
After drafting the subject line: Count the characters. If it is over 50, cut it. If it ends with a question mark, rewrite it as a statement. If it contains your company name or product name, reconsider — the subject is about the prospect, not the sender.
WHY: Each of the four elements serves a specific conversion function. Skipping or collapsing any element breaks the sequence. The Hook earns the read. The Relate earns the emotional connection. The Bridge earns the time. The Ask earns the action.
Hook — the opening sentence and subject line working together
The subject line gets the email opened. The first sentence must keep them reading. You have about three seconds.
Rules for the opening sentence:
Example: "Ernst & Young recently reported that the COO has the toughest role in the C-suite." — this hooks a COO because it validates their daily reality with a credible source.
Relate — demonstrate that you understand their world
Show empathy. Demonstrate that you have done enough research to understand their situation. You are not pitching yet — you are showing that you get them.
Rules:
Example: "The COOs I work with tell me that the increasing complexity of the banking environment has made their job harder and more stressful than ever."
Bridge — answer WIIFM (What's In It For Me)
This is the most important sentence in the email. It answers the prospect's most pressing question: if I give you my time, what do I get?
Rules:
Bridge structure: [I help] [people like you] [achieve specific outcome] [by/with specific approach]
Example: "My team and I help COOs like you reduce complexity and stress with strategies to optimize growth and profit, mitigate credit risk, allocate resources effectively, and minimize regulatory surprises."
Ask — direct, specific, low-resistance
Every prospecting email must end with a direct ask. Make it easy for the prospect to say yes. Make it hard for them to avoid responding.
Rules:
Example: "While I don't know if we are a good fit for your bank, why don't we schedule a short call to help me learn more about your unique challenges? How about next Thursday at 3:00 PM?"
WHY: Before writing the final email, run the completed draft through a structured quality gate. Most prospecting emails fail one of these three rules. Catching the failure before sending saves your sender reputation and the prospect's patience.
Rule 1: Will it get delivered? Re-run the deliverability checklist from Step 2 against the drafted email. Confirm no images, no attachments, no bulk send, no spam trigger words have crept into the body or subject.
Rule 2: Will it get opened?
Rule 3: Will it convert? Check the body against the five worst email patterns (immediate disqualifiers):
Hook-Relate-Bridge-Ask completeness check:
Fix any failures before moving to Step 6.
WHY: The formatted, annotated final email is the artifact the user sends. Annotations explain the "why" behind each element so the user can adapt the structure to future emails. The send-time recommendation increases the probability the email is read when it arrives.
Output format:
Write the final email with each section labeled (for the user's reference, to be stripped before sending):
Subject: [40-50 chars, action word, no question mark]
[Prospect last name],
[HOOK — opening sentence using credible source or prospect-relevant trigger, about them not you]
[RELATE — 1-2 sentences showing you understand their specific problem, using their language]
[BRIDGE — 1-2 sentences connecting their problem to the outcome you deliver; answers WIIFM; uses their industry jargon]
[ASK — 1-2 sentences with disruption framing + specific proposed day/time]
[Your name]
[Title]
[Company]
Send-time guidance:
Write the output to cold-email-draft-{prospect-name}.md in the working directory. Include:
| Input | Required | Source |
|---|---|---|
| Prospect role, company, industry | Yes | User provides or prospect-notes.md |
| Your value prop / outcome delivered | Yes | User provides or value-prop.md |
| Desired outcome of this email | Yes | User provides or prospecting-objective-setter output |
| Known trigger events at this account | No — strengthens the Hook | User provides or WebFetch research |
| Current draft email to improve | No — skill builds from scratch | User pastes inline or file path |
| Familiarity level with this prospect | No — affects subject line strategy | User states |
| Output | Location | Description |
|---|---|---|
cold-email-draft-{prospect}.md | Working directory | Send-ready email + annotated version + AMMO plan + deliverability and quality gate results |
| Inline diagnosis | Conversation | If a draft was provided: labeled list of what failed and why, before the rewrite |
1. The Three Cardinal Rules are a funnel, not a checklist. An email that does not get delivered converts at zero. An email that gets delivered but not opened converts at zero. Only an email that clears all three rules has a chance to convert. Apply them in sequence — deliverability first, open rate second, conversion third.
2. AMMO before writing. The fastest path to a bad prospecting email is opening a blank message and typing. The fastest path to a good one is spending two minutes on AMMO: who is this person, what method fits, what message will connect, what outcome am I after. Planning takes two minutes. Rewriting a bad email that burned a prospect takes permanently.
3. Subject lines over 50 characters get deleted. Over 50% of emails are opened on mobile. A subject line cut off at character 40 on a mobile screen defeats itself. Three to six words is the target. Less is more — always.
4. Never use a question mark in a subject line. Every major email study confirms this. Questions doom emails to the delete pile. Use action words and directive statements. "COO — The Toughest Job in the Bank" outperforms "Can we help reduce your complexity?" on every metric.
5. The email is about the prospect, not you. The subject line is about them. The opening sentence is about them. The relate section is about their problems. The bridge connects their world to your solution. The ask makes it easy for them. Only the signature is about you. Read your draft and count the sentences that start with "I" or "We" — each one is a red flag.
6. Disrupt expectations in the ask. Blount's COO example uses a counterintuitive ask: "While I don't know if we are a good fit for your bank..." This disarms the prospect. They expect a pushy pitch. Getting the opposite — honesty about uncertainty — pulls them toward you instead of triggering resistance. Disruption plus a specific proposed time outperforms a confident pitch every time.
7. One-to-one only — always. Bulk-sending a prospecting email from your personal address is the fastest path to being blacklisted and looking like a beginner. One email. One recipient. One send. That discipline alone clears 90% of spam hurdles.
Situation: Software sales rep sending a cold email to the CEO of a growing software consultancy.
Original (Brandon's approach — fails all three rules):
Subject: Cloud Based Software
Hi Jeb,
I was browsing LinkedIn and wanted to reach out to you.
We build custom software solutions; web, cloud, mobile, desktop. Whether you have need to modernize outdated software, build something new from scratch, or augment your team to meet a critical deadline, I'm confident we can help.
We've been able to figure out how to maintain high quality and keep our rates competitive. It's a model that has led us to three straight years on the INC 5000.
I'd love to schedule a time to connect and outline how we're able to do this while discussing any projects or plans you might have. Just let me know a time that works with your schedule for a free consultation & quote.
What fails:
Rewritten (applying AMMO + Hook-Relate-Bridge-Ask):
Subject: Custom Software Risk in a Scaling Firm
Jeb,
Gartner reports that 72% of custom software projects at growing firms run over budget or miss deadlines — most often because augmentation decisions are made under deadline pressure rather than strategic fit.
The CEOs I work with at software consultancies tell me that managing build vs. augment decisions while keeping delivery quality consistent is one of the most stressful parts of scaling.
My team works specifically with growing software firms to reduce delivery risk and keep margins intact as headcount scales — without the 3-month ramp time of traditional augmentation.
While I don't know if we're dealing with the same issues at your firm, I'd like to spend 20 minutes finding out. How about Thursday at 2:00 PM?
Brandon Senior Account Executive SoftCo
Annotation:
Situation: SDR at a logistics software company entering the mid-market manufacturing vertical. No prior contact with any prospect in this segment.
AMMO plan:
Email:
Subject: Inventory Visibility — 3 Patterns We See in Manufacturing
[Prospect first name],
A recent APICS report found that mid-size manufacturers lose an average of 11% of annual revenue to inventory errors — most of them invisible until they hit the production floor.
Operations leaders I work with in manufacturing describe the same pain: they have data in three different systems and still can't tell in real-time where a delay is coming from.
We help VP Operations teams at mid-market manufacturers get a single real-time view across procurement, warehousing, and fulfillment — which typically cuts emergency-order costs by 20–40% in the first quarter.
I don't know if inventory visibility is a priority right now, but I've been working in this segment and have some benchmarks from your industry I thought might be worth a quick conversation. How about 20 minutes next Tuesday at 10 AM?
[Name] [Title] [Company]
Annotation:
Situation: AE at an HR platform company. LinkedIn shows a new CHRO just joined a 300-person SaaS company that recently raised a Series B. The company is publicly hiring aggressively.
AMMO plan:
Email:
Subject: New CHRO + Series B — One Decision That Compounds
Lisa,
Congratulations on joining Acme and on the Series B. A CHRO stepping in at this stage faces a specific challenge: you need to scale the team fast enough to satisfy the board while building the infrastructure that prevents a bad-hire crisis at 500 employees.
New CHROs I work with at Series B companies tell me the first 90 days are critical — whatever hiring system is in place when headcount doubles tends to harden into permanent process, good or bad.
We help CHROs at growth-stage companies build a scalable hiring system in the first 90 days — so that adding 100 people doesn't add 100 points of chaos.
I know you're early and still finding your footing, but I've worked with several CHROs at this stage and have a framework I think would be useful to share. Would 30 minutes on Friday at 9 AM work?
[Name] [Title] [Company]
Annotation:
Note: this example bends the usual "no question mark" rule in the ask — the ask sentence uses "work?" which is acceptable when embedded in a two-sentence ask block with disruption framing. The subject line contains no question mark, which is the high-stakes rule. Applies judgment accordingly.
Detailed supporting materials are in the references/ folder:
references/spam-trigger-wordlist.md — full 200+ word/phrase list that triggers spam filters in subject lines and body copy (sourced from Comm100 research cited by Blount, p. 235)references/deliverability-checklist.md — expanded deliverability pre-check with per-industry notes (sensitive industries: financial, defense, healthcare)references/subject-line-patterns.md — library of subject line patterns with character counts, use cases, and tested examples: list-based, referral, role + problem, trigger event, complimentreferences/email-examples-library.md — complete annotated email examples by prospect role (COO, CFO, VP Sales, CISO, Operations Director, CHRO) and scenario type (new territory, post-trigger, re-engagement, referral introduction)references/ammo-planning-worksheet.md — AMMO planning worksheet with decision prompts for Audience, Method, Message, and Outcome; includes Targeted vs. Strategic bridge selection guideSource chapter: Blount, Jeb. Fanatical Prospecting, Chapter 19 "E-Mail Prospecting" (pp. 232–252 / PDF pp. 232–252). Subject line data: pp. 238–241. AMMO framework: pp. 242–245. Hook-Relate-Bridge-Ask: pp. 245–252. Three Cardinal Rules: pp. 234–241. Dave vs. Brandon annotated contrast: pp. 246–250.
Referenced external sources:
Content derived from Fanatical Prospecting by Jeb Blount (Wiley, 2015). This skill is licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0). You are free to share and adapt this material provided you give appropriate credit to Jeb Blount and BookForge, and distribute any derivative works under the same license.
Upstream dependencies — use these before or alongside this skill:
The message nucleus (WIIFM bridge and because) that feeds this email:
clawhub install bookforge-prospecting-message-crafter
The objective that drives the Ask in this email:
clawhub install bookforge-prospecting-objective-setter
Downstream or parallel skills:
For handling non-replies, brush-offs, or "send me more info" responses:
clawhub install bookforge-prospecting-rbo-turnaround
For building the full 5-step telephone follow-up after this email is sent:
clawhub install bookforge-cold-call-opener-builder
Browse the full Fanatical Prospecting skill set: bookforge-skills