Skip to main content
skill CX Codex official · Anthropic

outreach-composer — Claude Code skill: what it does, how to install

outreach-composer drafts prospect outreach and follow-up sequences in the sender's own voice. It checks drafts against AI slop patterns and prepares emails for review before sending.

Apache-2.0 388 installs ★ 36,654 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add anthropics/knowledge-work-plugins --skill outreach-composer -a claude-code
Open on GitHub

What outreach-composer does

The skill writes cold emails and follow-up sequences using the sender's actual tone. It inspects 15 to 30 sent emails from Gmail or Microsoft 365 to analyze sentence length and sign-off habits. If no mailbox is linked, it pauses. It will ask for three past messages instead of guessing.

Every message builds on a verified hook, such as a posted job role or a mutual connection. Data from Apollo or Clay can add extra context on company size and tech stack. The initial email stays under 120 words. Drafts then run through an anti-slop check. This removes generic praise and phrases the sender would never say out loud.

Without an active mail connector, the skill produces drafts as an HTML card or a Markdown file. It never sends a batch without an explicit manual confirmation. Inferred contacts demand a separate warning because bounced emails harm domain deliverability.

What it helps with

  • draft cold sales emails matching personal writing habits
  • build multi-step follow-up sequences with distinct angles
  • remove robotic templates and generic flattery from drafts
  • hold outbound emails for approval to protect domain health

Example prompts for the agent

  • Draft a cold outreach email for this lead and keep it under 120 words.
  • Create a 4-message follow-up sequence for this prospect list.
  • Read my sent messages in Gmail to build a voice profile.

How to install outreach-composer

1Skills CLI (Vercel)

npx skills add anthropics/knowledge-work-plugins --skill outreach-composer -a claude-code

2Manually: put the files in place

~/.claude/skills/outreach-composer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/outreach-composer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about outreach-composer

How do I install outreach-composer in Claude Code?

Run npx skills add anthropics/knowledge-work-plugins --skill outreach-composer -a claude-code. The configuration file will be stored in ~/.claude/skills/outreach-composer/SKILL.md.

How does outreach-composer learn your writing style?

It scans 15 to 30 sent emails from Gmail or Microsoft 365 to capture sentence length and greetings. If no mailbox is linked, it asks for three sample emails.

Will the skill send emails automatically?

No. It queues messages and requires an explicit confirmation before sending any batch. Without an active mail connector, it operates in draft-only mode and outputs HTML or Markdown.

Source text

SKILL.md · Apache-2.0
---
name: outreach-composer
description: >
  Writes prospect outreach and follow-up sequences that sound like the owner
  wrote them, not like an AI did. Learns a voice profile from the owner's own
  sent mail, grounds every message in something specific about that prospect,
  builds the follow-up sequence behind it, queues every send for approval, and
  logs each touch to the CRM. Runs draft-only when no mail connector is
  available, so the copy can be pasted anywhere. Use this whenever the owner
  needs to reach out to prospects or customers — including phrasings like
  "write this cold email," "draft a follow-up," "reach out to these leads,"
  "what do I say to them," "I need a sequence for this list," "nudge the people
  who didn't reply," or "write it but don't make it sound like a robot." Reach
  for it whenever outreach copy is the deliverable, even for a single message.
allowed-tools: Read, WebFetch
---

# Outreach Composer

Write outreach the owner would actually send under their own name.

The single most repeated condition owners set is some version of "without sounding like a bot." Owners will not send copy that embarrasses them, so a message that reads as generated is worth nothing regardless of how well structured it is. Voice fidelity is the product here, not a finishing touch.

## Step 1 — Learn the voice before writing anything

Read [the shared voice profile](../../shared/voice-profile.md) first. If a profile already exists there, use it and skip to Step 2 — rebuilding it every time wastes the owner's patience and produces drift.

If there is no profile, build one from evidence:

- **Gmail or Microsoft 365** — pull 15 to 30 of the owner's own sent messages to customers and prospects. This is the best source by a wide margin. Confirm the mailbox is the owner's first (`../../shared/tenant-scope.md`); another tenant's sent mail would teach the wrong voice.
- **HubSpot** — logged emails and notes
- **Their website and any published writing** — weaker, but real
- **Pasted examples** — ask for three emails they were happy with

Then extract the specific, imitable traits: sentence length, greeting and sign-off habits, contractions, whether they use exclamation marks, how direct the ask is, what they call their own product, regionalisms, and the things they never do. Save the profile so every later run inherits it.

**Without any sample, say so and ask for three.** Writing in a guessed voice produces exactly the generic copy the owner is trying to avoid.

## Step 2 — Ground each message in something real

A personalized email is not one with the company name merged into a template. It is one that could only have been sent to that person.

For each prospect, find the specific hook. In order of strength:

1. The buying signal from `lead-finder` — a permit filed, a location opened, a role posted
2. A shared connection or customer
3. Something specific about their business the owner can genuinely speak to
4. A relevant result the owner produced for a similar customer

If no hook exists beyond category fit, write a shorter, plainly cold message and say it is cold. A fake-warm opener is worse than an honest cold one, because it reads as a mail merge and destroys credibility in the first line.

**Apollo or Clay, when connected, can fill in the contact and company detail that makes a thin hook usable** — role, tenure, company size, tech stack — the kind of specific that keeps a message from reading as generic. Enrichment data, not a hook on its own.

## Step 3 — Write the sequence

Read `reference/sequence_patterns.md` for structure by scenario. Defaults:

- **Cold outreach** — 4 messages over 3 weeks
- **Warm or referral** — 3 messages over 2 weeks
- **Post-meeting follow-up** — 2 messages over 10 days
- **Re-engagement of a quiet customer** — 3 messages over 4 weeks

Each message in a sequence must add something new. A follow-up whose entire content is "just bumping this" trains people to ignore the sender. Give every touch a fresh reason to exist: a different angle, a relevant result, a genuinely useful piece of information, or a clean close-out.

Length rule: first message under 120 words. Owners in this segment sell to people who read on their phone between jobs.

## Step 4 — Self-check against the slop test

Before showing anything, run every draft against `reference/slop_test.md`. It catches the specific patterns that make copy read as machine-written.

The fastest checks:

- Would the owner say this sentence out loud? If not, rewrite it.
- Could this message be sent to any other company with two words changed? If yes, it is not personalized.
- Does it open with a compliment about the prospect's business? Delete it — everyone does this and everyone recognizes it.
- Is there a phrase here the owner has never used in their life? Cut it.

This step is not optional and it is not a formality. It is the difference between copy that gets sent and copy that gets rewritten by hand, which is the outcome the skill exists to prevent.

## Step 5 — Present for approval

Show the full sequence before anything queues. Follow `reference/output_template.md`.

Present message one in full, then the rest of the sequence with subject lines and the angle each takes. Owners want to read the first one closely and skim the shape of the rest.

**Deliver per the owner's stored output preference — never default to a markdown file.** Check the `## Business context` block's `Output preference` (shared style guide rule, `../../shared/artifact-style.md`):

- **Visual artifact (the default):** an HTML page in the house style — one card per prospect or sequence, each message as a copy block so any single message can be copied and sent by hand.
- **docx / md / notion / canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.
- **Best for skill:** use the visual artifact — the copy blocks are the point.

Chat keeps the recap and the approval question in every case.

Then ask what to change. Expect edits — the first pass is a proposal, not a delivery. Fold every edit back into the voice profile, because a correction made once should not have to be made again.

## Step 6 — Queue sends, with approval, one gate at a time

Sending email under the owner's name is the highest-consequence action in this skill.

- **Never send without an explicit yes** for that specific batch
- **State exactly what will happen** before asking: how many messages, to whom, on what schedule, from which account
- **Never send to a contact marked "inferred"** without flagging it separately. Bounces at volume damage the owner's sending domain for months, and that damage reaches their real customer mail
- **Approval for message one is not approval for the sequence.** Confirm the follow-ups separately, or set them to draft and let the owner release each

**Mailchimp is a drafting destination, not a send route.** When it is connected, an approved
sequence can be saved into Mailchimp as campaign content for the owner to schedule there.
Three things govern that:

- **It cannot send.** Nothing this skill puts into Mailchimp goes out on its own. The owner presses send in Mailchimp.
- **Its planner refuses single campaigns.** Mailchimp's campaign planner only produces multi-channel plans — email plus SMS plus social. A one-off email is written here, in the owner's voice, and saved as content. Do not route a single message through the planner and do not report a refusal as a failure.
- **Do not assume you can read the audience list.** Treat the contact list as unavailable unless a call actually returns it. Build the recipient list from the CRM or the owner's own file, as today.

**Without a mail connector, run draft-only.** Produce the copy formatted to paste anywhere. This is a complete outcome, not a degraded one — plenty of owners prefer to send from their own client anyway.

## Step 7 — Log it

Log every touch to HubSpot when connected: what was sent, when, to whom, and where it sits in the sequence. Without a CRM, keep the record in a file so the next run knows who has already been contacted.

Contacting someone twice with the same opener is a visible, avoidable mistake.

## What not to do

- **Do not write before learning the voice.** Everything downstream depends on it.
- **Do not open with flattery about their business.** It is the single clearest tell.
- **Do not send a follow-up that says only "checking in."** Every touch earns its place.
- **Do not merge a company name into a template and call it personalized.**
- **Do not send anything without an explicit approval for that batch.**
- **Do not claim results the owner has not actually produced.** Invented case studies in outreach are a serious problem, not an exaggeration.

## After the send

The sequence is approved, queued or drafted, and every touch is logged. The natural next step is "update the CRM" — `crm-autopilot` keeps the next-step queue current as replies come in. Also nearby: "leads are going cold" (`speed-to-lead`) to catch the responses fast, and "find me customers" (`lead-finder`) when this list runs dry. Offer at most three, and skip any offer the owner already declined this session.

## Reference files

- [`../../shared/voice-profile.md`](../../shared/voice-profile.md) — the owner's voice, shared by every skill that writes in their name
- `reference/sequence_patterns.md` — structure and cadence by scenario
- `reference/slop_test.md` — the checklist that catches machine-written copy
- `reference/output_template.md` — how sequences are presented for approval
- `reference/gotchas.md` — the failure modes that get owners to stop using this

## Using a tool that isn't listed

The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.

© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins

Similar skills

All skills for Marketing and content →

From the same set263

The whole set →
grant-rfp-writer grant-rfp-writer finds grants and solicitations your organization qualifies for, decides whether to bid, and drafts the response from past submissions. After an award it tracks deadlines and reports. CX Codex +1 392installs inbox-manager inbox-manager sorts incoming mail by what needs the owner, extracts deadlines, and drafts replies. It also works with pasted or forwarded messages. CX Codex +1 391installs reactivate reactivate finds customers who stopped buying, ranks them by past value and drafts a win-back sequence for each. Nothing goes out without the owner's approval. CX Codex +1 389installs crm-autopilot crm-autopilot is a Claude Code skill that updates contacts, deals, and activity from email, calendar events, and call transcripts. It also surfaces quiet deals and records that need cleanup. CX Codex +1 389installs ap-processor ap-processor reads vendor bills from the AP inbox or uploaded PDFs and photos, codes them to your accounts and jobs, checks POs, and stages a payment run. Nothing posts without your yes. CX Codex +1 387installs marketing-monday marketing-monday is a Claude Code skill that brings growth metrics, customer feedback, and competitor changes into a weekly brief. It can run once or offer a recurring schedule. CX Codex +1 386installs report-pack report-pack runs scheduled recurring briefings via report-builder and adds context from business-pulse, delivering an XLSX sheet and summary. CX Codex +1 386installs payroll-prep payroll-prep — a skill for Claude Code, Codex, Cursor and other agents that pulls timesheets from Gusto, QuickBooks Payroll, or an uploaded spreadsheet and totals regular, overtime, and PTO hours per employee. CX Codex +1 386installs

Project sponsors

Companies that keep this analytics open