gooseworks-ai/goose-skills / skills/marketing/write-outreach
write-outreach
VerifiedCold outreach a person sends to business buyers: email and LinkedIn sequences, a first line per prospect, reply and objection answers, and a read of replies. Use when the marketer says "write a cold email sequence", "what do I send to this list", "write LinkedIn messages for these leads", "how do I reply to this prospect" or "handle this objection", "reply to this demo request", "win back or reconnect with accounts that churned or went quiet", or "why is nobody replying to my outreach". Drafts only; the marketer sends from their own tool. Not for finding the people — use research-audience; not for emails to subscribers or users, or consumer win-back — use email-lifecycle.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.7 KB |
| references/angles-by-signal.md | markdown | 7.3 KB |
| references/email-craft.md | markdown | 5.7 KB |
| references/handoff-and-compliance.md | markdown | 9.1 KB |
| references/linkedin-craft.md | markdown | 3.4 KB |
| references/outreach-by-company-type.md | markdown | 3.3 KB |
| references/reading-results.md | markdown | 5.9 KB |
| references/replies-and-objections.md | markdown | 4.8 KB |
| references/run-memory.md | markdown | 6.0 KB |
| references/sequences.md | markdown | 4.7 KB |
| skill.meta.json | config | 3.7 KB |
| tests/test-by-hand.md | markdown | 3.6 KB |
references/email-craft.md
View on GitHub# Cold email craft
Load at steps 1–4 and in outreach-qa. A cold email is read in a few seconds on a phone by someone who owes the sender nothing. It earns a reply by being about **their** situation, short, true, and easy to answer.
Numbers here are rules of thumb from outbound practice, not measured for this brand; the brand's own results (outcomes-ledger lessons) beat them as soon as they exist.
## The shape of touch 1
1. **First line — the hook.** Their signal or a fact about their work, and why it matters to the pain. Never about the sender. ("Saw Brightfold has two AP specialist roles open — usually a sign month-end close is slipping.")
2. **One or two lines — evidence.** The pain in the buyers' own words, and what we do about it. Proof only if signed off (claims-gate); otherwise a plain product fact or nothing.
3. **One line — the ask.** One low-friction question.
4. **Sign-off:** first name, or name and role. No "Best regards", no title block, no image signature.
**Length:** touch 1 is 50–90 words; follow-ups 30–50; the last touch 20–30; a warm reconnection 40–70. Two or three short paragraphs; four is the cap. Over 120 words fails QA.
## Frameworks — pick by the situation
| Framework | Shape | Use when |
|---|---|---|
| **Signal → proof → ask** | Their signal, what we do about it, a soft ask | Any signal-led touch (the default) |
| **Problem → agitate → solve** | The pain, what it costs them, the fix | A stated pain or a need implied by news |
| **Before → after → bridge** | Where they are, where they want to be, how | A growing team, a new hire, a new leader's agenda |
| **Attention → interest → desire → action** | A sharp opener, relevance, the outcome, the ask | A cold list with no signal (weakest — prefer a segment angle) |
| **Relationship → context → ask** | How you know them, why now, a light ask | Warm only: past champions, past users, win-back |
## Personalisation — how deep
| Depth | What changes per person | When |
|---|---|---|
| Segment | Pain and proof per segment; merge fields per row | Large lists with no per-person signal |
| Signal | A first line from each person's dated signal or hook | Lists from research-audience (the default) |
| Deep | Signal plus something they said or wrote | Top-value accounts, a handful a day |
A hook is useful only if it ties to the pain. "Loved your post on brand storytelling" proves research happened and nothing else. Strongest hooks, in order: something they wrote or said recently (≤60 days); their own job post; their recent move; a concrete event at their company. **Never:** school, family, health, religion, politics, location, personal accounts, "#OpenToWork", or a fact you can't link.
**Never lie about how you found them.** No "came across your profile" for a list built from search; no "we met at…" without a meeting; no fake "Re:" or "Fwd:". (Warm contacts flip this rule: name exactly how you know each other.)
## Subject lines
Under 50 characters (QA flags over 60); lower-case or sentence case; no "!", emoji or all-caps; no "quick question", "touching base", "free", "limited time". Shapes that work:
- Their signal: "before you fill the ap roles"
- Their pain as a question: "still matching invoices by hand?"
- The topic for them: "month-end close at brightfold"
- A peer angle (only with a signed-off peer example): "how <peer group> handle <pain>"
- A switch (only when they said it): "looking for an <rival> alternative?"
Follow-ups reply in the same thread (no new subject) unless the angle changes completely.
## The ask
One per message, smallest that moves things: "worth a look?", "open to a 15-minute call next week?", "want the one-page breakdown?", "who owns creative there?" Never two asks; never a calendar link in touch 1 to a stranger; never "let me know your thoughts". Later touches can build: an overview → a short walkthrough → a resource with no call at all.
## Hard rules
1. No filler opener ("hope this finds you well", "my name is", "I'm reaching out because").
2. No "just checking in", "bumping this", "circling back". Every follow-up adds something new or isn't sent.
3. Nothing in the first sentence about us.
4. One ask.
5. No invented facts, numbers, customers, results or compliments. A number needs a signed-off claim behind it.
6. No jargon: synergy, leverage, circle back, touch base, align, ping, revolutionary, game-changing, cutting-edge, best-in-class.
7. No attachments in touch 1; at most one link, and none in touch 1 when the mailbox is new.
8. Plain text, no images, no tracking pixels (open tracking hurts delivery and is unreliable — Apple Mail pre-loads images; judge on replies).
9. A real person signs and can answer.
10. The opt-out line and the sender's identity on every email (handoff-and-compliance.md).
## Tone
Peer to peer for founders and managers ("casual-direct"); crisp and brief for directors and above; empathetic when the hook is a pain; never needy. A sender's voice card, when one exists, sets the words; these rules still apply.
## Before / after (fictional seller of accounts-payable software — never reuse its values)
Weak: "Hi Jordan, I hope you're well! I'm reaching out from Ledgerly, the AI-powered platform revolutionising finance teams. We help companies like yours cut costs by 80%. Do you have 30 minutes this week for a demo?"
- About us, an invented number, a hype word, a big ask, no hook.
Better: "Hi Jordan — saw Brightfold has two AP specialist roles open since the 2nd. Teams usually add AP headcount when month-end close starts slipping. We match invoices to POs automatically, so new hires start on exceptions, not data entry. Worth a look before they start? — Robin"
- Hook from her signal, the pain, a plain product fact, one small ask, 50 words.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |