cold-email-writer · git:20260723.de898c0 · 2026-07-23 · sha256 13ec50e924605250
cold-email-writer git:20260723.de898c0A
Immutable. This exact content never changes and is served at /api/v1/blob/13ec50e924605250.
---
name: cold-email-writer
description: Write personalized cold emails that earn replies — research-based hooks, clear relevance, low-friction asks. Use for outbound prospecting messages.
metadata: {"navin":{"emoji":"🧊","category":"sales"}}
---
# Cold Email Writer
## Overview
A cold email earns a reply when it proves relevance in the first line and asks for something easy. Personalization is research, not {{first_name}}.
## Anatomy (60–120 words max)
1. **Subject** — 2–5 words, lowercase-casual or specific ("question migration data", "SAFA → vous ?") — no clickbait
2. **Line 1** — the observation that proves you did homework (their news, job posting, public project, tech choice)
3. **The bridge** — that observation → the problem you solve, one sentence
4. **Proof** — one relevant result with a number ("aidé X à faire Y en Z semaines")
5. **Ask** — low friction: a question they can answer in one line, or "ça vaut 15 minutes ?" — never "book a call on my calendar" cold
## Personalization tiers
| Tier | Effort | Use for |
|------|--------|---------|
| Researched (unique first line, custom angle) | 10–15 min | A-leads, big accounts |
| Segmented (shared pain per segment, real examples) | template + 2 min | B-leads |
| Generic blast | never | — |
## Workflow
1. Input: lead + research (`account-research` for A-leads).
2. Write 2 variants; ruthless cut to <120 words; mobile-preview check (subject + first line).
3. Plan the sequence with `outreach-sequencer` (this skill writes; that one schedules).
4. Human validation before sending (see `human-approval`); track replies to learn which hooks work.
## Rules
- Never fake familiarity ("j'adore ce que vous faites") or fake urgency.
- One CTA. No attachments. No "je me permets".
- Compliance: identify yourself/company honestly; opt-out respected instantly.