event-prospecting-pipeline
Find attendees at conferences/events, research their companies, qualify against ICP, and launch outreach
Best use case
event-prospecting-pipeline is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Find attendees at conferences/events, research their companies, qualify against ICP, and launch outreach
Teams using event-prospecting-pipeline 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/event-prospecting-pipeline/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How event-prospecting-pipeline Compares
| Feature / Agent | event-prospecting-pipeline | 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?
Find attendees at conferences/events, research their companies, qualify against ICP, and launch outreach
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
# Event Prospecting Pipeline End-to-end workflow: find event attendees → research → qualify against ICP → deduplicate → outreach. ## When to Use - "Find leads from [event name/URL]" - "Who's speaking at [conference]? Get me their contact info" - "Find AI events in SF and get me decision-maker contacts" - "Find leads from upcoming conferences and launch outreach" > **For Luma-only qualified lead gen** with built-in Google Sheets + Slack alerting, use [[skills/composites/get-qualified-leads-from-luma/SKILL.md]] instead. This playbook is the full pipeline including outreach. ## Steps ### 1. Find Attendees / Speakers **Skills:** luma-event-attendees OR conference-speaker-scraper - If user provides a Luma event URL or topic → use `luma-event-attendees` - If user provides a conference website → use `conference-speaker-scraper` - If user provides a topic/location → use `luma-event-attendees` Apify search mode to find events first **Output:** Person list with names, bios, LinkedIn/Twitter URLs, companies. ### 2. Research & Enrich **Capability:** Web search For each person/company: - Company funding stage, size, product - Person's current role and seniority - Recent news or activity Skip if user just wants a raw attendee list. ### 3. Qualify Against ICP **Skill:** lead-qualification Filter the enriched list against the client's ICP criteria. Score each lead. ### 4. Find Decision-Maker Contacts **Skill:** company-contact-finder For qualified companies, find the specific decision-makers with email addresses. ### 5. Deduplicate **Skill:** contact-cache Check all leads against the contact cache to prevent duplicate outreach across strategies. ### 6. Output Results **Capability:** Google Sheets or CSV export Export qualified, deduplicated leads with columns: Name, Title, Company, LinkedIn URL, Email, Signal, Score. ### 7. Launch Outreach (optional) **Skill:** setup-outreach-campaign OR agentmail If approved, set up personalized outreach via Smartlead campaign or direct AgentMail. ## Human Checkpoints - **After Step 3**: Review qualified lead list before finding contacts - **After Step 6**: Review final list and email copy before launching outreach
Related Skills
signal-detection-pipeline
Detect buying signals from multiple sources, qualify leads, and generate outreach context
outbound-prospecting-engine
End-to-end outbound prospecting: detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign.
event-signals
Extract leads from conferences, meetups, hackathons, and podcasts by analyzing speaker lists, sponsor lists, hackathon entries, and podcast guests. Discovers events via Sessionize, Confs.tech, Meetup, Luma, ListenNotes, and Devpost. Looks back 90 days and forward 180 days.
pipeline-review
Pipeline analysis composite. Pulls deal/meeting data from any CRM or tracking system, analyzes the pipeline over a user-defined period (weekly, fortnightly, monthly, quarterly), and produces both an executive summary and a detailed diagnostic report. Covers volume, qualification rates, source effectiveness, stage velocity, stuck deals, and actionable recommendations. Tool-agnostic — works with any CRM (Salesforce, HubSpot, Pipedrive, Close, Supabase, CSV).
luma-event-attendees
Find speakers, hosts, and guest profiles at conferences and events on Luma. Two modes - free direct scrape for hosts, or Apify-powered search for full guest profiles with LinkedIn/Twitter/bio.
seo-content-engine
Build and run an SEO content engine: audit current state, identify gaps, build keyword architecture, generate content calendar, draft content.
competitor-monitoring-system
Set up and run ongoing competitive intelligence monitoring for a client. Tracks competitor content, ads, reviews, social, and product moves.
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.
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.