- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill cold-outreach-sequence -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill cold-outreach-sequence -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill cold-outreach-sequence -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill cold-outreach-sequence -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/BrianRWagner/ai-marketing-claude-code-skills/tree/HEAD/cold-outreach-sequenceDe l'éditeur
Here's what I've learned about cold outreach: the word "cold" is the problem.
Spray-and-pray templates don't work. 10 minutes of research + a specific reference = not cold anymore. This skill builds the second kind.
Detect from context or ask: "One message, full sequence, or full outreach system?"
Default: standard — use quick if they give you one name and say "draft something." Use deep if they're building a repeatable outreach engine.
Before writing any message, collect:
positioning-basics output if available)Research tool calls — run before writing:
web_search('[Company] [Founder/Name] news 2026')
web_search('[Company] funding recent')
web_search('[Person name] [Company] LinkedIn')
Personalization constraint: Do not write a Tier 1 message without a named specific signal from research. If search yields 0 signals, default to Tier 3 and say so explicitly.
For each prospect, document findings before drafting:
Signal types (ranked by message strength):
Personalization tier assignment:
Formula: [Specific observation from research] + [Simple reason to connect]
Rules:
By signal type:
Recent funding: "Congrats on the Series A — the [investor] backing is a smart signal. Would love to connect."
Recent post: "Your post on [specific topic] resonated — been thinking the same thing. Happy to connect."
News/launch: "Saw the [product] launch — [specific detail] is smart positioning. Would love to connect."
Formula: [Thanks] + [Bridge to relevance] + [Light value] + [Soft question]
Template:
Thanks for connecting. I work with [ICP description] on [specific outcome].
Curious — is [relevant function] something you own directly at [Company],
or is that still founder-led?
Happy to share what I'm seeing work at similar-stage companies either way.
Formula: [Light nudge] + [New signal or angle] + [Easy out]
Constraint: Do NOT write "following up" with nothing new. Add one new piece:
Template:
Bumping this up — came across [specific article/trend/insight] and
thought of your situation at [Company].
[One sentence on why it's relevant to them.]
Happy to share more if useful. If not, no worries.
Shift to email if LinkedIn hasn't converted, or try a different angle.
Subject line options:
Email structure:
[1-line hook tied to their specific situation]
[2-3 sentences: why you're reaching out + one proof point]
[Soft CTA — 1 sentence]
I'll assume timing isn't right — totally get it.
If [relevant pain point] becomes a priority down the road, happy to reconnect.
Best of luck with [specific thing they're working on based on research].
Post-break-up action: Add to 6-month re-engagement list with a resurface date.
After generating the full sequence, evaluate:
Flag any issue: "The first message doesn't include a soft question — it reads as a pitch. Revised to invite dialogue."
Always output a tracking table for the batch:
| Prospect | Company | Platform | Tier | Sent Date | Response | Stage | Next Action | Resurface Date |
|---|---|---|---|---|---|---|---|---|
| [Name] | [Co] | LinkedIn | 1 | [date] | — | Connection sent | Wait 24-48h | — |
| [Name] | [Co] | Email | 2 | [date] | — | First email sent | Follow-up Day 7 | — |
After each response (or non-response), ask:
## Outreach Sequence: [Prospect Name] — [Date]
### Research Summary
- Signal type: [news / post / company info / none]
- Signal found: "[Specific detail]"
- Personalization tier: [1/2/3]
- Source: [URL or platform]
### Sequence
**Connection Request (LinkedIn):**
[Text — max 300 chars]
**First Message (Day 1-2 after accept):**
[Text]
**Follow-Up #1 (Day 7):**
[Text]
**Follow-Up #2 (Day 14):**
Platform: [LinkedIn / Email]
Subject: [if email]
[Text]
**Break-Up (Day 21):**
[Text]
### Pipeline Entry
| Prospect | Company | Platform | Tier | Stage | Next Action | Resurface Date |
|---|---|---|---|---|---|---|
| [Name] | [Co] | [Platform] | [Tier] | Connection sent | Wait 24-48h | — |
### Self-Critique Notes
[Any issues flagged + revisions made]
Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com
Build personalized cold outreach sequences for LinkedIn and email. Use when someone needs to reach prospects, warm up cold leads, or build a systematic outreach engine. Covers research, connection req
---name: cold-outreach-sequencedescription: Build personalized cold outreach sequences for LinkedIn and email. Use when someone needs to reach prospects…---# cold-outreach-sequence/SKILL.mdVue d'ensemble
Build personalized cold outreach sequences for LinkedIn and email. Use when someone needs to reach prospects, warm up cold leads, or build a systematic outreach engine. Covers research, connection requests, follow-ups, and conversion.
FAQ
Téléchargez cold-outreach-sequence/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/BrianRWagner/ai-marketing-claude-code-skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.