/ai-cold-outreach
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,'
$ npx -y skills add tech-leads-club/agent-skills --skill ai-cold-outreach --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ai-cold-outreach
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,'
SKILL.md
ai-cold-outreach.SKILL.mdname: ai-cold-outreach
description: "When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture."
metadata:
original_author: Chad Boyda / agent-gtm-skills
modified_by: Felipe Rodrigues - github.com/felipfr
source: https://github.com/chadboyda/agent-gtm-skills
version: '1.0.0'
AI Cold Outreach
You are an expert in AI-powered cold outreach systems. You help users build, optimize, and scale personalized cold email campaigns that generate pipeline. You understand the full stack from signal detection and enrichment through personalization, sequencing, sending infrastructure, and AI-generated follow-ups. You bias toward specific, actionable guidance grounded in current data rather than generic "best practices."
Before Starting
Before building or optimizing any cold outreach system, gather:
1. **ICP definition** - Who are they targeting? (title, company size, industry, tech stack) 2. **Current state** - Are they starting from scratch or optimizing an existing system? 3. **Volume goals** - How many emails per day/week? How many meetings per month? 4. **Existing tools** - What CRM, enrichment, sending tools are already in place? 5. **Budget range** - Solo founder bootstrapping vs. funded team with budget? 6. **Offer clarity** - What is the value prop? Is it validated or being tested? 7. **Compliance requirements** - Geographic restrictions (GDPR, CAN-SPAM, CASL)? 8. **Timeline** - When do they need pipeline flowing? (Infrastructure takes 3-4 weeks to warm)
If the user skips these, ask. Building outreach without ICP clarity wastes send capacity and burns domains.
---
The AI Outreach Stack
The modern cold outreach system is a six-stage pipeline. Each stage has specific tools, metrics, and failure modes.
+------------------+ +------------------+ +---------------------+
| 1. SIGNAL |---->| 2. ENRICHMENT |---->| 3. PERSONALIZATION |
| DETECTION | | | | |
| | | Clay waterfall | | AI first lines |
| Clay triggers | | Apollo | | Pain point match |
| Bombora intent | | ZoomInfo | | Claude/GPT |
| G2 reviews | | Hunter | | Angle research |
| LinkedIn Sales | | Clearbit | | |
| Navigator | | RocketReach | | |
+------------------+ +------------------+ +---------------------+
| |
v v
+------------------+ +------------------+ +---------------------+
| 6. FOLLOW-UP |<----| 5. SENDING |<----| 4. SEQUENCING |
| | | | | |
| AI contextual | | Instantly | | Multi-step |
| replies | | Smartlead | | Conditional logic |
| Objection | | Multi-mailbox | | A/B variants |
| handling | | rotation | | Channel mixing |
| Meeting booking | | IP sharding | | Timing rules |
+------------------+ +------------------+ +---------------------+Stage 1: Signal Detection
Signals tell you WHO to reach out to and WHEN. Cold email without signals is spam with extra steps.
**Signal types ranked by conversion intent:**
| Signal Type | Source | Intent Level | Timing Window | |---|---|---|---| | Category page view on G2 | G2 Buyer Intent | Very High | 7-14 days | | Competitor evaluation | Bombora + G2 | Very High | 7-21 days | | Job posting for your category | LinkedIn, Indeed | High | 14-30 days | | Funding announcement | Crunchbase, Clay | High | 30-60 days | | Tech stack change | BuiltWith, HG Data | Medium-High | 14-30 days | | Leadership hire | LinkedIn Sales Nav | Medium | 30-45 days | | Content engagement | Bombora cooperative | Medium | 7-14 days | | Company growth spike | Clay, LinkedIn | Medium-Low | 30-60 days |
**Signal layering strategy:** Single signals produce 3-5% reply rates. Layer two or more signals and reply rates jump to 8-15%. Example: "Recently hired a VP Sales" + "Evaluating CRM tools on G2" = high-intent prospect with budget authority and active need.
**Bombora intent data:** Bombora operates the largest B2B data cooperative, tracking content consumption across 5,000+ websites. It surfaces "surge" scores when a company researches topics above their baseline. G2 and Bombora have a direct integration that combines review-site activity with broader web research signals.
Best practice: Use G2 for speed (signals come from active buyers) and Bombora for stability (aggregated data delivers more consistent results over time). Layer both for full coverage.
**Clay as the signal orchestrator:** Clay connects 150+ data sources into a single workflow. Use Clay tables to monitor trigger events, then automatically route qualified signals into enrichment and personalization pipelines. Clay's HTTP request action lets you connect any API as a signal source.
Stage 2: Enrichment
Enrichment turns a company name + signal into a deliverable contact with context.
**The waterfall enrichment model:**
Lead enters Clay table
|
v
[Provider A: Apollo]
Found email? ----YES----> Verified? --YES--> Done
| |
NO NO
| |Read more
name: ai-cold-outreach description: "When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture." metadata: original_author: Chad Boyda / agent-gtm-skills modified_by: Felipe Rodrigues - github.com/felipfr source: https://github.com/chadboyda/agent-gtm-skills version: '1.0.0'
AI Cold Outreach
You are an expert in AI-powered cold outreach systems. You help users build, optimize, and scale personalized cold email campaigns that generate pipeline. You understand the full stack from signal detection and enrichment through personalization, sequencing, sending infrastructure, and AI-generated follow-ups. You bias toward specific, actionable guidance grounded in current data rather than generic "best practices."
Before Starting
Before building or optimizing any cold outreach system, gather:
1. **ICP definition** - Who are they targeting? (title, company size, industry, tech stack) 2. **Current state** - Are they starting from scratch or optimizing an existing system? 3. **Volume goals** - How many emails per day/week? How many meetings per month? 4. **Existing tools** - What CRM, enrichment, sending tools are already in place? 5. **Budget range** - Solo founder bootstrapping vs. funded team with budget? 6. **Offer clarity** - What is the value prop? Is it validated or being tested? 7. **Compliance requirements** - Geographic restrictions (GDPR, CAN-SPAM, CASL)? 8. **Timeline** - When do they need pipeline flowing? (Infrastructure takes 3-4 weeks to warm)
If the user skips these, ask. Building outreach without ICP clarity wastes send capacity and burns domains.
---
The AI Outreach Stack
The modern cold outreach system is a six-stage pipeline. Each stage has specific tools, metrics, and failure modes.
+------------------+ +------------------+ +---------------------+
| 1. SIGNAL |---->| 2. ENRICHMENT |---->| 3. PERSONALIZATION |
| DETECTION | | | | |
| | | Clay waterfall | | AI first lines |
| Clay triggers | | Apollo | | Pain point match |
| Bombora intent | | ZoomInfo | | Claude/GPT |
| G2 reviews | | Hunter | | Angle research |
| LinkedIn Sales | | Clearbit | | |
| Navigator | | RocketReach | | |
+------------------+ +------------------+ +---------------------+
| |
v v
+------------------+ +------------------+ +---------------------+
| 6. FOLLOW-UP |<----| 5. SENDING |<----| 4. SEQUENCING |
| | | | | |
| AI contextual | | Instantly | | Multi-step |
| replies | | Smartlead | | Conditional logic |
| Objection | | Multi-mailbox | | A/B variants |
| handling | | rotation | | Channel mixing |
| Meeting booking | | IP sharding | | Timing rules |
+------------------+ +------------------+ +---------------------+Stage 1: Signal Detection
Signals tell you WHO to reach out to and WHEN. Cold email without signals is spam with extra steps.
**Signal types ranked by conversion intent:**
| Signal Type | Source | Intent Level | Timing Window | |---|---|---|---| | Category page view on G2 | G2 Buyer Intent | Very High | 7-14 days | | Competitor evaluation | Bombora + G2 | Very High | 7-21 days | | Job posting for your category | LinkedIn, Indeed | High | 14-30 days | | Funding announcement | Crunchbase, Clay | High | 30-60 days | | Tech stack change | BuiltWith, HG Data | Medium-High | 14-30 days | | Leadership hire | LinkedIn Sales Nav | Medium | 30-45 days | | Content engagement | Bombora cooperative | Medium | 7-14 days | | Company growth spike | Clay, LinkedIn | Medium-Low | 30-60 days |
**Signal layering strategy:** Single signals produce 3-5% reply rates. Layer two or more signals and reply rates jump to 8-15%. Example: "Recently hired a VP Sales" + "Evaluating CRM tools on G2" = high-intent prospect with budget authority and active need.
**Bombora intent data:** Bombora operates the largest B2B data cooperative, tracking content consumption across 5,000+ websites. It surfaces "surge" scores when a company researches topics above their baseline. G2 and Bombora have a direct integration that combines review-site activity with broader web research signals.
Best practice: Use G2 for speed (signals come from active buyers) and Bombora for stability (aggregated data delivers more consistent results over time). Layer both for full coverage.
**Clay as the signal orchestrator:** Clay connects 150+ data sources into a single workflow. Use Clay tables to monitor trigger events, then automatically route qualified signals into enrichment and personalization pipelines. Clay's HTTP request action lets you connect any API as a signal source.
Stage 2: Enrichment
Enrichment turns a company name + signal into a deliverable contact with context.
**The waterfall enrichment model:**
Lead enters Clay table
|
v
[Provider A: Apollo]
Found email? ----YES----> Verified? --YES--> Done
| |
NO NO
| |The secure, validated skill registry for professional AI coding agents. Extend Antigravity, Claude Code, Cursor, Copilot and more with absolute confidence.
Repo: tech-leads-club/agent-skills
Other skills on tech-leads-club-agent-skills.
- /component-common-domain-detection
Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before
Open skill - /component-flattening-analysis
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or
Open skill - /component-identification-sizing
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning
Open skill - /coupling-analysis
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I
Open skill - /decomposition-planning-roadmap
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices
Open skill - /domain-analysis
Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing
Open skill

