🎁 Get the FREE AI Skills Starter Guide — Subscribe →
BytesAgainBytesAgain
BytesAgain › Skills › Cold Email Writer
🦀 ClawHub

Cold Email Writer

by @quochungto

Write a complete cold prospecting email — subject line, body, and send-time recommendation — using Blount's AMMO planning framework and Hook-Relate-Bridge-As...

Versionv1.0.0
#crypto#clawhub
⚡ When to Use
TriggerAction
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*:
1. **AMMO plan** — audience, method, message, outcome — before writing a word
2. **Deliverability pre-check** — so the email reaches the inbox, not the spam folder
3. **Hook-Relate-Bridge-Ask body** — the four-element structure that converts
**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 body
If you have not run those skills, this skill will gather the required context itself. The AMMO plan subsumes both.
💡 Examples

Example 1 — Bad-to-Good Rewrite (Based on Dave vs. Brandon, Fanatical Prospecting pp. 246–250)

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:

  • Subject line: "Cloud Based Software" — about the sender, not the recipient; contains a spam-adjacent term; says nothing about the prospect's world
  • "Hi Jeb" — "Hi" is a sales turnoff; no one in business uses this except salespeople
  • "I was browsing LinkedIn and wanted to reach out" — about the sender; "wanted" is past tense and self-focused; gives the prospect zero reason to keep reading
  • Body: feature dump — *web, cloud, mobile, desktop* — answers nobody's question
  • Relate attempt: company cheerleading about INC 5000 — "so what?" — why does the prospect care?
  • Ask: "I'd love to..." — self-centered; "just let me know a time" puts the burden on the prospect; "free consultation" signals desperation
  • No AMMO planning visible; same email could be sent to anyone

    • 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:

  • Subject: 43 characters, action word ("Risk"), prospect-centric, no question mark
  • Hook: third-party data, relevant to CEO's world, no "Hi"
  • Relate: surrogate empathy ("The CEOs I work with tell me..."), emotional language ("most stressful"), speaks CEO language
  • Bridge: answers WIIFM with specific outcome (delivery risk + margins + ramp time), uses their jargon
  • Ask: disruption framing ("I don't know if..."), specific day/time, assumes the meeting happens

    • Example 2 — New Territory Introduction Email (SDR / SaaS / VP of Operations Target)

    Situation: SDR at a logistics software company entering the mid-market manufacturing vertical. No prior contact with any prospect in this segment.

    AMMO plan:

  • Audience: VP Operations, 200-500 person manufacturer, likely managing inventory and fulfillment
  • Method: standalone cold email, Targeted bridge (large pool, inferred pain from industry trends)
  • Message: operational complexity during inventory unpredictability is their primary stress point
  • Outcome: 20-minute discovery call

    • 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:

  • Subject: 45 characters, "3 Patterns" creates curiosity, prospect-centric
  • Hook: APICS data + manufacturing-specific (not generic software pitch)
  • Relate: "Operations leaders I work with tell me..." — surrogate empathy + their language (three systems, real-time, production floor)
  • Bridge: specific outcome (20–40% emergency-order cost reduction) + connects to their role jargon
  • Ask: disruption framing, "benchmarks from your industry" adds curiosity value, specific Tuesday at 10 AM

    • Example 3 — Post-Trigger-Event Email (AE / HR Tech / New CHRO at a Growth-Stage Company)

    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:

  • Audience: newly appointed CHRO, starting fresh at high-growth company with mandate to build
  • Method: strategic 1:1 email, personalized to trigger event
  • Message: new CHROs in high-growth environments face hiring speed vs. quality tradeoff under board pressure
  • Outcome: 30-minute discovery call

    • 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:

  • Subject: 42 characters, two trigger events (New CHRO + Series B) connected with an outcome word ("Compounds")
  • Hook: congratulates without being sycophantic, immediately pivots to their challenge
  • Relate: new-CHRO-specific empathy, 90-day language reflects her reality
  • Bridge: "100 people doesn't add 100 points of chaos" — speaks her language, emotional + logical value
  • Ask: "I know you're early" — disruption, respects her onboarding reality; specific Friday at 9 AM

    • *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.*

    View on ClawHub
    TERMINAL
    clawhub install bookforge-cold-email-writer

    🧪 Use this skill with your agent

    Most visitors already have an agent. Pick your environment, install or copy the workflow, then run the smoke-test prompt above.

    Manus
    Task-oriented agent. Great for testing AI skills end-to-end.
    Try Manus →
    OpenClaw
    Local-first agent. Install skills via ClawHub CLI.
    Set up OpenClaw →
    Claude Code
    Anthropic's coding agent. Paste the prompt or SKILL.md into your session.
    Claude Code docs →
    Cursor
    AI-powered IDE. Use the smoke-test prompt in Cursor Agent.
    Open Cursor →
    Continue.dev
    Open-source AI code assistant. Add SKILL.md as a custom tool.
    Continue docs →
    Windsurf
    Agentic IDE by Codeium. Paste the prompt into Cascade.
    Try Windsurf →
    Cline
    VS Code extension for autonomous coding with MCP tools.
    Cline on GitHub →
    Copilot Workspace
    GitHub's AI dev environment. Suitable for code-generation skills.
    Copilot Workspace →

    🔍 Can't find the right skill?

    Search 60,000+ AI agent skills — free, no login needed.

    Search Skills →