exa-lead-gen
Skill9 starsChanged 6 months agoMITView on GitHub
Generate enriched lead lists using Exa deep search. Finds companies matching an ICP, enriches with signals/news/scores, and outputs CSV. Use when generating leads, building prospect lists, finding companies to sell to, doing outbound research, or ICP-based company discovery.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Layneformalized225/ai-cofounderedited, first seen Mar 22, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Layneformalized225/ai-cofounder★ 193% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository78 other files it gives its agents.
- anti-pattern-auditSkill
- brand-storytellingSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- company-intelSkill
- competitive-analysisSkill
- competitor-researchSkill
- composio-cliSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- evening-recapSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- feedback-trackerSkill
- find-email-by-nameSkill
- focus-keeperSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- github-stars-monitorSkill
- google-calendarSkill
- grafana-monitoringSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- install-openclaw-to-digitaloceanSkill
- install-openclaw-to-hetznerSkill
- install-openclaw-to-ycSkill
- launch-marketingSkill
- lead-enrichmentSkill
- measuring-product-market-fitSkill
- meeting-prepSkill
- metrics-briefingSkill
- morning-briefSkill
- openclaw-guideSkill
- openclaw-user-onboardingSkill
- orthogonalSkill
- outreach-senderSkill
- person-lookupSkill
- ph-launch-timelineSkill
- pipeline-managerSkill
- positioning-messagingSkill
- positioning-workshopSkill
- posthog-analyticsSkill
- prepare-yc-workshopSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- product-led-salesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Call the native MCP tool exa-deep__deep_search_exa directly.
- Distinctive: line 43
Every string field must have a word limit in its description
- Distinctive: line 112
After CSV is generated, report:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lead Generation (Exa Deep Search)
Tool
Call the native MCP tool exa-deep__deep_search_exa directly. Parameters go in a JSON object.
Architecture
Main agent orchestrates; subagents run the searches. This keeps context lean.
Main Agent (orchestrator)
├── Step 1: ICP research (1 deep call)
├── Step 2: Generate micro-verticals (LLM reasoning)
├── Step 3: Design outputSchema
├── Step 4: Batch subagents (5 micro-verticals each, parallel)
│ Each subagent: runs 5 deep calls → writes JSON → reports count
├── Step 5: Python CSV compiler (reads JSON, dedupes, sorts)
└── Step 6: SummaryRequired Params on Every deep_search_exa Call
structuredOutput=true
numResults=50
highlightMaxCharacters=1
type=deepnumResults and systemPrompt must align — set numResults=50 and ask for "exactly 50 companies" in systemPrompt.
outputSchema Constraints
- Max 10 properties total across all nesting levels
- Array items: flat objects with primitive fields only (string, integer, boolean, array of strings)
- Every string field must have a word limit in its description
- Root must be
"type": "object"
Call Examples
Tool: exa-deep__deep_search_exa
# Step 1: ICP Research
{ objective: "About {company_name}, {company_name} customers",
systemPrompt: "Research the company and return ICP, sub-verticals, and useful enrichments",
structuredOutput: true, numResults: 10, highlightMaxCharacters: 1, type: "deep" }
# Step 4: Lead gen call (inside subagent)
{ objective: "B2B sales intelligence platforms using web scraping and contact data enrichment",
systemPrompt: "List exactly 50 companies. Score each 1-10 on ICP fit. Return structured enriched data.",
structuredOutput: true, numResults: 50, highlightMaxCharacters: 1, type: "deep" }Micro-Vertical Budget
Target ceil(requested_leads / 35) micro-verticals (overshoot for dedupe losses).
Step 1: ICP Research Schema
{
"type": "object",
"properties": {
"company_description": {"type": "string", "description": "What they do in 2 sentences"},
"product_description": {"type": "string", "description": "What they sell and to whom, 2 sentences"},
"existing_customers": {"type": "array", "items": {"type": "string"}},
"icp_description": {"type": "string", "description": "ICP in 12 words or less"},
"sub_verticals": {"type": "array", "items": {"type": "string"}},
"demographic_signals": {"type": "array", "items": {"type": "string"}},
"useful_enrichments": {"type": "array", "items": {"type": "string"}}
}
}Standard Lead Schema (customize per use case)
{
"type": "object",
"properties": {
"companies": {
"type": "array",
"items": {
"type": "object",
"properties": {
"company_name": {"type": "string", "description": "in 5 words or less"},
"website": {"type": "string", "description": "homepage URL"},
"product_description": {"type": "string", "description": "in 12 words or less"},
"icp_fit_score": {"type": "integer"},
"icp_fit_reasoning": {"type": "string", "description": "one-liner in 20 words or less"},
"industry_vertical": {"type": "string", "description": "in 3 words or less"},
"funding_stage": {"type": "string", "description": "Bootstrap/Seed/Series A/B/C+/Public/Unknown"},
"headquarters_location": {"type": "string", "description": "City, Country in 4 words or less"},
"recent_signals": {"type": "array", "items": {"type": "string", "description": "under 12 words each"}}
}
}
}
}
}Output Format
After CSV is generated, report:
- Total leads, duplicates removed
- ICP score distribution (8-10 / 5-7 / 1-4)
- Number of Exa calls made
- Output filename
Performance
- Each
deep_search_exacall: 4-12s - Yield: ~35-48 companies per call (avg ~42)
- For 500+ leads: confirm with user before starting
- Launch batch subagents in waves of ~6 to respect QPS limits
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

