Individual skill
write-outreach
Cold 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.
skills/marketing/write-outreach/SKILL.md
Source commit df8298140d434a6363de0c265eb6af2e571d97a5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,315
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- claudecode Repository topic
- claudecode-skills Repository topic
- codex Repository topic
- cursor Repository topic
- gtm Repository topic
- skills Repository topic
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 17,081 bytesSKILL.mdcore · 17,081 bytesreferences/angles-by-signal.mddoc · 7,481 bytesreferences/email-craft.mddoc · 5,830 bytesreferences/handoff-and-compliance.mddoc · 9,275 bytesreferences/linkedin-craft.mddoc · 3,461 bytesreferences/outreach-by-company-type.mddoc · 3,341 bytesreferences/reading-results.mddoc · 6,029 bytesreferences/replies-and-objections.mddoc · 4,934 bytesreferences/run-memory.mddoc · 6,158 bytesreferences/sequences.mddoc · 4,772 bytesskill.meta.jsonasset · 3,758 bytestests/test-by-hand.mddoc · 3,690 bytes
Read excerpt
# write-outreach
Turns a list, or a buyer group, into words a founder or seller can send this week: **sequences per segment**, **a first line per person**, **replies and objection answers**, and later **what the replies say to fix**. The craft is in the references; this file is the order of work.
**The rule that matters most: write from evidence, send nothing.** Every first line rests on a dated fact about that person or account; every proof line is signed off; every message has one ask. The marketer sends from their own mailbox and tool, after warming it up — GooseWorks' own inbox is not a cold-email sender.
## What you get
1. **The outreach pack**, in the shape and checks of [the `write-report` skill](../write-report/SKILL.md). Outreach adds: the first move is who to send to first (with no list, that there is no one yet); decisions cover proof lines to sign off, the sender, the sending tool, daily volume and timing; with no list or on a first pack, the whole path and who does each step ([references/handoff-and-compliance.md](references/handoff-and-compliance.md) § The whole path); per segment the angle, the full sequence once (email and LinkedIn, with days) and 3 sample first lines; replies and objection answers; the before-you-send checklist with the one-line country summary; Sources say where each first line's facts came from and which proof was signed off and which cut. Every row's first line and finished messages go in the send file (and an appendix table when the marketer has no tool).
2. **A send file** the marketer imports into their tool (one subject and body column per touch, merge fields filled) — [references/handoff-and-compliance.md](references/handoff-and-compliance.md).
3. **Later, on request:** reply drafts for real replies, and a read of results — what to fix in targeting, timing or message.
## Before you start