# Write Outreach

> Create signal-led outreach and reply handling. Use for cold email, founder outreach, partnership or sales messages, LinkedIn or other DMs, proposals, follow-ups, inbound reply handling, deliverability, compliance, or evaluating whether sent outreach earned qualified conversations.

- Skill: `forsvn-labs/write-outreach` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add forsvn-labs/write-outreach`
- Raw SKILL.md: https://api.skillmd.com/api/skills/forsvn-labs/write-outreach/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: forsvn-labs (https://skillmd.com/u/forsvn-labs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/forsvn-labs/write-outreach

---


# Write trustworthy outreach

Earn relevance from an observable signal, make a small honest ask, and preserve the recipient's
control.

## Establish selection and proof

Define one segment, channel, observed selection signal, costly moment, affiliation, proof boundary,
and next action. A job title or company category alone is not personalization.

Trace target-specific statements to public, operator-supplied, or permissioned evidence. Never invent
a trigger, private deal, shared connection, customer result, or familiarity.

## Write the sequence

Create the smallest useful sequence:

- subject/opening tied to the signal;
- why the issue may matter now;
- credible mechanism or useful artifact;
- proof appropriate to the evidence available;
- one low-friction ask;
- follow-up that adds value or closes the loop.

Do not use false urgency, deceptive threading, manufactured familiarity, or an endless cadence.
Preserve founder/company voice and channel norms.

Prepare concise reply handling for interested, objection, not now, wrong person, proof question,
unsubscribe, and ambiguous responses. Never request sensitive material through an unsafe channel.

## Protect deliverability and consent

State the applicable identity, opt-out, suppression, lawful-basis, and platform-policy requirements.
Monitor delivered volume, bounce, complaint, unsubscribe, reply quality, and sender reputation. Stop
when deliverability or compliance crosses the predeclared boundary.

## Deliver

Return:

1. selection signal and exclusions;
2. finished sequence;
3. proof and personalization sources;
4. reply bank;
5. compliance/deliverability checklist;
6. qualified-conversation metric, diagnostics, batch size, and stop rule.

Do not send, enrich, upload contacts, write to a CRM, or schedule a sequence without explicit
approval for the exact action.