outbound-prospecting-engine
End-to-end outbound prospecting: detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign.
Best use case
outbound-prospecting-engine is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
End-to-end outbound prospecting: detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign.
Teams using outbound-prospecting-engine should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/outbound-prospecting-engine/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How outbound-prospecting-engine Compares
| Feature / Agent | outbound-prospecting-engine | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
End-to-end outbound prospecting: detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Outbound Prospecting Engine Build and run a complete outbound prospecting system: signal detection → company research → contact finding → personalization → campaign launch. ## When to Use - "Set up outbound prospecting for [client]" - "Build a lead gen engine targeting [ICP]" - "Find and reach out to companies that need [solution]" ## Prerequisites - Client context.md with ICP, value props, positioning - Signal keywords (what to monitor for intent) - Approved messaging / email sequences (or generate them) ## Steps ### 1. Define Signal Sources Based on the client's ICP and motion, select which signals to monitor: | Signal Source | Best For | Skill | |--------------|---------|-------| | Job postings | Companies with allocated budget | job-posting-intent | | Funding announcements | Companies with fresh capital | funding-signal-monitor | | LinkedIn posts/comments | Practitioners discussing the problem | linkedin-post-research + linkedin-commenter-extractor | | Conference attendees | People actively engaged with the space | luma-event-attendees | | Competitor customers | Companies already buying similar solutions | competitor-post-engagers | ### 2. Run Signal Detection Execute selected signal skills with client-specific keywords. Run in parallel. **Output**: Raw signal list — companies + signal context. ### 3. Qualify & Score **Skill**: lead-qualification Filter against ICP criteria. Score each lead: - Multi-signal leads = highest priority - Job posting + funding = strongest intent - Single social mention = lowest (awareness only) ### 4. Find Decision-Maker Contacts **Skill**: company-contact-finder For top qualified companies, find the specific decision-makers: - Target titles from client's ICP - Get email addresses and LinkedIn URLs ### 5. Deduplicate **Skill**: contact-cache Check all leads against the contact cache. Add new leads to cache. Skip any that have been contacted before. ### 6. Personalize Outreach For each lead, generate personalized email sequence using: - The signal that surfaced them (the "why now") - Their company context (what they do, their pain) - The client's value proposition (how it solves their pain) ### 7. Launch Campaign **Skill**: cold-email-outreach Set up the outreach campaign in your chosen tool: - Create campaign with name and schedule - Upload lead list - Configure 2-3 email sequence (personalized per lead or per segment) - Allocate mailboxes - Set sending schedule ### 8. Monitor & Iterate - Track open rates, reply rates, meeting bookings - A/B test subject lines and messaging - Re-run signal detection weekly to add new leads - Update contact cache with outcomes ## Ongoing Cadence - **Weekly**: Re-run signal detection, qualify new leads, add to campaign - **Bi-weekly**: Review campaign metrics, adjust messaging - **Monthly**: Review overall pipeline contribution, adjust signal sources ## Human Checkpoints - **After Step 3**: Review qualified lead list before finding contacts - **After Step 6**: Review personalized email copy before launching campaign - **After Step 8**: Review campaign performance metrics
Related Skills
client-packet-engine
Batch client packet generator. Takes company names/URLs, runs intelligence + strategy generation, presents strategies for human selection, executes selected strategies in pitch-packet mode (no live campaigns or paid enrichment), and packages into local delivery packets.
seo-content-engine
Build and run an SEO content engine: audit current state, identify gaps, build keyword architecture, generate content calendar, draft content.
event-prospecting-pipeline
Find attendees at conferences/events, research their companies, qualify against ICP, and launch outreach
orthogonal-targeted-prospecting
Build a prospect list of companies with decision makers, verified contact info, and hiring/intent signals. Use when asked to find leads by industry, build an account list with specific titles, prospect companies that are actively hiring, or create a targeted outreach list filtered by company size, location, and hiring activity.
orthogonal-sales-prospecting
Build targeted prospect lists with verified contact information
competitor-monitoring-system
Set up and run ongoing competitive intelligence monitoring for a client. Tracks competitor content, ads, reviews, social, and product moves.
client-package-notion
Package all work done for a client into a shareable Notion page with subpages and Google Sheets. Reads the client's folder (strategies, campaigns, content, leads, notes) and builds a structured Notion workspace the client can browse. Lead list CSVs are uploaded to Google Sheets and linked from the Notion pages. Use when you want to deliver work to a client in a polished, navigable format.
client-package-local
Package all work done for a client into a local filesystem delivery package with .md files and Google Sheets. Reads the client's folder (strategies, campaigns, content, leads, notes) and builds a structured directory with dated deliverables. Lead lists are uploaded to Google Sheets and linked from the markdown files. Use when you want to deliver work to a client in a polished, navigable format without requiring Notion.
client-onboarding
Full client onboarding: intelligence gathering, synthesis into Client Intelligence Package, and growth strategy generation. Phases 1-3 of the Client Launch Playbook.
lead-discovery
Orchestrator that runs first for lead generation requests. Gathers business context via website analysis or questions, identifies competitors, builds ICP, and routes to signal skills with pre-filled inputs.
serp-feature-sniper
Analyze SERP features per keyword (featured snippets, PAA, video carousels, knowledge panels, image packs) and produce optimized content structures to win them. Identifies which features are winnable, who currently holds them, and exactly how to format your content to steal them.
search-ad-keyword-architect
Deep keyword research for paid search. Analyzes competitor SEO keywords, review language, Reddit/community terminology, and existing site content to build a keyword architecture: branded vs non-branded, funnel stage mapping, match type recommendations, and estimated competition tiers. Use before building a Google Ads campaign or to audit an existing one.