email-outreach
Writes personalized B2B cold emails at a steady daily volume: researches real prospects against your ideal customer profile (ICP), drafts a genuinely 1:1 email for each, and dedupes against a permanent contact log that updates itself from real Gmail replies, bounces, and unsubscribes. Each email is timed to the prospect's local business hours, checked for deliverability and anti-spam compliance, and A/B-tracked by subject line, with the outreach strategy re-confirmed monthly. Queues everything for approval (or creates Gmail drafts if connected) and never sends on its own. Use for cold email, cold outreach, sales prospecting, lead generation, or sales outreach to new contacts. Not for drip or nurture emails to people who already opted in; that is email-sequence.
marcosmodly · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add marcosmodly/marketing-skill --skill email-outreach技能说明
name: email-outreach description: "Writes personalized B2B cold emails at a steady daily volume: researches real prospects against your ideal customer profile (ICP), drafts a genuinely 1:1 email for each, and dedupes against a permanent contact log that updates itself from real Gmail replies, bounces, and unsubscribes. Each email is timed to the prospect's local business hours, checked for deliverability and anti-spam compliance, and A/B-tracked by subject line, with the outreach strategy re-confirmed monthly. Queues everything for approval (or creates Gmail drafts if connected) and never sends on its own. Use for cold email, cold outreach, sales prospecting, lead generation, or sales outreach to new contacts. Not for drip or nurture emails to people who already opted in; that is email-sequence." allowed-tools: Read, Grep, Glob, Write, Edit, WebSearch, WebFetch
Email Outreach
Purpose
Turn "find prospects and email them" into a repeatable daily job rather than a one-off batch: research real prospects against a defined ICP, write each one an email that could not be sent unchanged to anyone else, check every candidate against a permanent contact log so nobody gets emailed twice (or ever again, once they've unsubscribed or replied) — keeping that log accurate on its own by reading real Gmail replies and bounces instead of relying on someone remembering to update it — time each send to the prospect's own local business hours, hold every draft to a deliverability and compliance bar before it ships, and re-confirm the underlying strategy at least once a month instead of running the same angle forever unexamined. This skill drafts and queues only — it never sends anything, even when a connected Gmail account makes sending technically one tool call away.
Step-by-step process
Plugin root: if a path below still shows an unexpanded
CLAUDE_PLUGIN_ROOT placeholder (Claude Code fills it in; other agents
such as Codex don't), resolve it before using any of them: take the
output of printenv CLAUDE_PLUGIN_ROOT if it prints a path, otherwise
walk up from this file's folder to the first folder that contains
references/brand-voice.md, and if neither works, ask the user where
this plugin lives. Use that absolute path in every file path and shell
command below.
-
Check onboarding status. Read
${CLAUDE_PLUGIN_ROOT}/references/brand-voice.md. If it doesn't exist, or its first line is<!-- MARKETING-SKILL:UNCONFIGURED -->, pause and ask the user this plugin's 4 setup questions (priority task; content types to produce; target audience + tone; default output format — same as/marketing-skill:marketing-setup) before continuing, then save the answers into that file and flip the marker toCONFIGUREDwith today's date. Otherwise, read it for tone, audience, and banned words to apply below. -
Check outreach-strategy status. Read
${CLAUDE_PLUGIN_ROOT}/references/outreach-strategy.md.- If it doesn't exist, or its first line is
<!-- MARKETING-SKILL:OUTREACH-UNCONFIGURED -->, run full guided setup before researching or drafting anything: ask for the Ideal Customer Profile/segment(s), the value proposition/angle per segment, the offer and primary CTA, sender identity and compliance (a real physical mailing address — required, don't invent or skip past it; from name; reply-to if different), the daily outreach volume target and whether the sending mailbox is new or established (new → propose a ramp schedule instead of jumping to target volume), the send-time window preference (default: the file's placeholder), the follow-up cadence, and the suppression window. Write the answers in under the file's existing headings and set the marker to<!-- MARKETING-SKILL:OUTREACH-STRATEGY (last refreshed: YYYY-MM-DD) -->using today's date. - Otherwise, parse that date. If it's 30 or more days old, or the user explicitly asks for a strategy review, run the Monthly Strategy Refresh below before continuing to step 3. If it's fresh, proceed straight to step 3 using the file's current settings.
Monthly Strategy Refresh:
- Read
${CLAUDE_PLUGIN_ROOT}/state/outreach-log.mdand tally Status counts for rows dated since the last refresh (Sent,Replied,Bounced,Unsubscribed/Do-Not-Contact,Skipped-Duplicate), and, if there's enough volume for it to mean anything, a reply-rate split by Subject Variant (AvsB). - Show the user that tally alongside the current ICP/segment(s), angle, offer/CTA, sender identity, daily volume, send-time window, and follow-up cadence.
- Ask whether anything should change — segment, angle, offer, sender identity, volume, send-time window, cadence, or suppression window — and whether a subject-line variant has pulled clearly ahead enough to standardize on it. "No changes, keep as-is" is a valid answer; don't force a change that isn't warranted.
- Rewrite the relevant section(s) with any changes, append one new dated bullet to Performance Notes summarizing the tally (including the variant split) and what — if anything — changed because of it, and update the marker's date to today. Never delete prior Performance Notes entries.
- Report this refresh in today's output (see "Strategy Status" below) before moving on to that day's batch in the same run.
- If it doesn't exist, or its first line is
-
Sync the inbox (Gmail reply/bounce/unsubscribe detection). Check whether Gmail MCP tools are connected in this session (runtime check, same pattern as the prospecting-tool check in step 6 — never assumed). If connected: read
${CLAUDE_PLUGIN_ROOT}/state/outreach-log.mdand, for every row stillSentwith no terminal outcome yet, look up its thread using the id stored in Notes (orsearch_threadsbyEmailif none was stored) and apply the Automatic status