Przejdź do treści
Biblioteka skilli
Sprzedaż i obsługa klienta · Research

lead-generation

/lead-generation

Generuje wzbogacone listy leadów według ICP z użyciem Exa Agent, ze strukturalną oceną i wynikiem w CSV, do wyszukiwania firm i prospectingu.

Repozytorium
marketing-cli ↗
Licencja
MIT
Ostatnia zmiana repozytorium
20.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
11
Przestarzałość

Brak sygnałów. Repozytorium zmienione 20.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Generuje wzbogacone listy leadów według ICP z użyciem Exa Agent, ze strukturalną oceną i wynikiem w CSV, do wyszukiwania firm i prospectingu.

Oryginalny opis (EN)

Generate enriched ICP-based lead lists with Exa Agent, including structured scoring and CSV output. Use when generating leads, building prospect lists, finding companies to sell to, outbound research, or ICP-based company discovery. Triggers on leads, lead gen, prospect list, find companies, ICP, outbound list. Distinct from lead-magnet (content asset that captures emails).

Jak działa

  1. On Activation
  2. mktg runtime note
  3. Prerequisites
  4. Tool Restriction
  5. Workflow
  6. Step 1: Understand the ICP
  7. Step 2: Create the Lead-Gen Run
  8. Step 3: Wait and Read Output
  9. Step 4: Write the CSV
  10. Step 5: Expanding the List
Sekcje z nagłówków SKILL.md, w oryginale · 215 linii, 1 307 słów
Podgląd SKILL.md
---
name: lead-generation
version: 0.1.0
description: >
  Generate enriched ICP-based lead lists with Exa Agent, including structured
  scoring and CSV output. Use when generating leads, building prospect lists,
  finding companies to sell to, outbound research, or ICP-based company
  discovery. Triggers on leads, lead gen, prospect list, find companies, ICP,
  outbound list. Distinct from lead-magnet (content asset that captures emails).
allowed-tools:
  - Bash
  - Read
  - Write
  - Skill
author: Exa Labs (ported by mktg)
license: MIT
user-invocable: true
metadata:
  openclaw:
    emoji: 🎯
---

## On Activation

1. Read `brand/audience.md`, `brand/positioning.md`, and `brand/competitors.md` if present to seed ICP + exclusions. All optional.
2. Confirm Exa MCP with Agent tools (`agent_tools` / `agent_run`) or `EXA_API_KEY`. Without Agent access, stop and surface the MCP config from this skill.
3. Confirm ICP with the user before large runs (default 200 leads is expensive).
4. Write CSV under the project (e.g. `marketing/leads/` or cwd). Never write credentials into brand/.

# Lead Generation with Exa Agent


## mktg runtime note

Prefer **Exa MCP** when available (tools: `web_search_exa`, `web_search_advanced_exa`, `web_fetch_exa`, `agent_run`).
If MCP Agent tools use the older create/wait/get names (`agent_create_run`, `agent_wait_for_run`, `agent_get_run_output`), use those equivalently.
Without MCP, call the HTTP API with `x-api-key: $EXA_API_KEY` (`POST https://api.exa.ai/search`, `/contents`, `/agent`).
Firecrawl remains the path for deep scrape of a **known URL** after Exa discovery.


Generate enriched lead lists using the Exa Agent API. An Agent run is an asynchronous, multi-step web research task: you describe the list you want plus an output schema, and Exa handles query decomposition, searching, verification, enrichment, and structured output internally. You do NOT need to orchestrate parallel searches, subagents, or manual deduplication.

For very large or continuously maintained lead lists with per-item verification, consider Exa Websets instead: https://docs.exa.ai/websets/api/overview

## Prerequisites

This skill requires the Exa MCP server with the Agent tools enabled (`agent_tools`): `agent_create_run`, `agent_wait_for_run`, `agent_get_run_output`, `agent_cancel_run`.

If the Agent tools are not available, tell the user:

> You need the Exa MCP server installed with the Agent tools and your API key.
> Instructions: https://docs.exa.ai/reference/exa-mcp

Then stop.

## Tool Restriction

Use the Exa Agent tools (`agent_create_run`, `agent_wait_for_run`, `agent_get_run_output`, `agent_cancel_run`), plus Write and Bash (for CSV output). Do NOT use generic web search for the lead list itself.

## Workflow

```
1. Confirm the ICP with the user (one small Agent run if research is needed)
2. Create the lead-gen Agent run(s) with an outputSchema
3. Wait for completion (agent_wait_for_run)
4. Read output.structured (agent_get_run_output)
5. Write the CSV
6. Optional: expand with follow-up runs (previousRunId + input.exclusion)
```

## Step 1: Understand the ICP

When the user says something like "Make a list of 200 leads for [company]", first establish the Ideal Customer Profile. If the user already described the ICP, confirm it. If not, run one small Agent run to research it:

```
agent_create_run {
  "query": "Research {company_name}: what they sell, who their existing customers are, and what their ideal customer profile is.",
  "effort": "low",
  "outputSchema": {
    "type": "object",
    "properties": {
      "company_description": { "type": "string", "description": "What the company does in 2 sentences or less" },
      "icp_description": { "type": "string", "description": "Concise ICP description that clearly defines target companies" },
      "sub_verticals": { "type": "array", "maxItems": 10, "items": { "type": "string" }, "description": "Sub-verticals breaking down the ICP" },
      "useful_enrichments": { "type": "array", "maxItems": 8, "items": { "type": "string" }, "description": "Enrichment columns useful for filtering high-signal companies" }
    },
    "required": ["company_description", "icp_description", "sub_verticals", "useful_enrichments"]
  }
}
```

Present the ICP to the user and confirm:

- Is the ICP description accurate?
- Any companies to exclude (competitors, existing customers)?
- How many leads do they want? (default 200)
- Any specific enrichment columns they care about?

## Step 2: Create the Lead-Gen Run

Design an `outputSchema` with a bounded `companies` array. Keep schemas small, flat, and explicit; always bound arrays with `maxItems`.

**Core fields to always include:**

- `company_name` (string)
- `website` (string)
- `product_description` (string, "in 12 words or less")
- `icp_fit_score` (integer, 1-10)
- `icp_fit_reasoning` (string, "compelling one-liner in 20 words or less")

Add enrichment fields tailored to the campaign (funding stage, headcount range, headquarters, hiring signals, etc.). Give string fields a length hint in their description to keep CSV output clean.

Use the run inputs for the pieces the old manual pipeline handled by hand:

- `query` - describe the list: the ICP, geography, stage, and how many companies you want
- `outputSchema` - the exact structure back, with `maxItems` bounding the companies array
- `systemPrompt` - scoring rules, source preferences, dedup/exclusion emphasis
- `input.exclusion` - companies to avoid (competitors, existing customers, results from earlier runs)
- `effort` - `"auto"` by default; `"high"` or `"xhigh"` for large or hard lists

Example:

```
agent_create_run {
  "query": "Find 100 companies matching this ICP: {icp_description}. Prioritize {sub_verticals}. For each company, score ICP fit 1-10 for {user_company}.",
  "effort": "auto",
  "systemPrompt": "Prefer official company sites and recent funding announcements. Do not include duplicates or subsidiaries of the same parent company.",
  "input": {
    "exclusion": ["{competitor_1}", "{existing_customer_1}"]
  },
  "outputSchema": {
    "type": "object",
    "properties": {
      "companies": {
        "type": "array",
        "maxItems": 100,
        "items": {
          "type": "object",
          "properties": {
            "company_name": { "type": "string" },
            "website": { "type": "string", "format": "uri" },
            "product_description": { "type": "string", "description": "in 12 words or less" },
            "icp_fit_score": { "type": "integer", "description": "1-10" },
            "icp_fit_reasoning": { "type": "string", "description": "one-liner in 20 words or less" }
          },
          "required": ["company_name", "website", "product_description", "icp_fit_score", "icp_fit_reasoning"]
        }
      }
    },
    "required": ["companies"]
  }
}
```

`agent_create_run` returns an `agent_run_...` ID immediately. Save it.

## Step 3: Wait and Read Output

1. Call `agent_wait_for_run` with the run ID. It polls until the run reaches a terminal status (`completed`, `failed`, or `cancelled`) or times out - call it again if the run is still going.
2. When `completed`, call `agent_get_run_output`. Read the companies from `output.structured`, citations from `output.grounding`, and the run cost from `costDollars`.

Do not paste the full raw output into the conversation - go straight to CSV.

## Step 4: Write the CSV

Write `output.structured.companies` to `{target_company}_leads_{YYYY-MM-DD}.csv`, sorted by `icp_fit_score` descending. Join any array fields with " | ". Use Python's `csv.writer` (handles quoting/escaping) via Bash, or Write directly for small lists.

Print a summary:

```
## Lead Generation Complete

- Total leads: {count}
- ICP score distribution: 8-10: {N} | 5-7: {N} | 1-4: {N}
- Run ID: {agent_run_id}
- Cost: ${costDollars}
- Output: {filename}
```

## Step 5: Expanding the List

If the user wants more leads than one run returned:

- Create a follow-up run with `previousRunId` set to the completed run's ID, asking for additional companies
- Put the company names already collected into `input.exclusion` so the new run avoids them
- Append the new results to the CSV and re-deduplicate by normalized company name (strip "Inc"/"Ltd"/etc., case-insensitive)

For lists in the many hundreds, run a few runs sequentially this way rather than one giant run, and confirm scope with the user first: "This will require ~{N} Agent runs. Proceed?"

## Handling Failures

- If a run ends `failed`, read the error from `agent_get_run_output`, adjust the query or schema, and retry once with different wording
- Use `agent_cancel_run` if a run is clearly researching the wrong thing
- If results are consistently below the requested count, narrow the ICP into 2-3 sub-vertical runs instead of one broad run

## MCP Configuration

Requires an Exa API key. Get yours at https://dashboard.exa.ai/api-keys

```json
{
  "servers": {
    "exa": {
      "type": "http",
      "url": "https://mcp.exa.ai/mcp?tools=agent_tools",
      "headers": {
        "x-api-key": "YOUR_EXA_API_KEY"
      }
    }
  }
}
```

## References

- Exa Agent guide: https://docs.exa.ai/reference/agent-api-guide
- Exa MCP setup: https://docs.exa.ai/reference/exa-mcp
- Websets (verified list-building at scale): https://docs.exa.ai/websets/api/overview
- Full docs for LLMs: https://docs.exa.ai/llms.txt

## Anti-Patterns

| Anti-pattern | Why it fails | Instead |
|---|---|---|
| Using Claude native WebSearch instead of Exa | Misses niche competitors, companies, and cited sources Exa ranks highly. | Use this skill (or Exa MCP) for all open-ended web research. |
| Calling Exa without `EXA_API_KEY` / MCP auth | Requests 401 and the agent invents results. | Set `EXA_API_KEY` (dashboard.exa.ai) or configure `.mcp.json`; surface the fix via `mktg doctor`. |
| Dumping raw result JSON into the user chat | Burns context and hides the answer. | Synthesize; cite URLs from grounding / result lists. |

## Attribution

Ported from [exa-labs/agent-skills](https://github.com/exa-labs/agent-skills) - adapted for mktg's drop-in contract on 2026-07-18.

Upstream commit: 390ffee2d7e1d0dce2ed8efe4994c2b3c1c0173b

Drift detection: if the upstream skill changes, re-run `mktg-steal https://github.com/exa-labs/agent-skills` to evaluate the diff.

Wersje

RepozytoriumWynikLicencja
Ta strona · MoizIbnYousaf/marketing-cli100MIT
nirholas/xactions100Apache-2.0
exa-labs/agent-skills100MIT
naveedharri/benai-skills100MIT
cogni-work/insight-wave100Apache-2.0
Navinspire-ia/navin90AGPL-3.0

Migawka bazy z 13.11.2026 · wersja paczki 059da289ac5e (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 1 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100lead-research-assistant
    Wspiera generowanie leadów B2B i research: szuka leadów, buduje listy prospektów, bada firmy, znajduje kontakty na LinkedIn i decydentów oraz eksportuje leady do CSV.
  • 90list-building
    Buduje kwalifikowane listy prospektów B2B w Clay, LinkedIn Sales Navigator i wielu źródłach: listy kont docelowych, firmy pasujące do ICP i scrapowanie źródeł leadów.
  • 95exa-people-search
    Wyszukuje konkretne osoby na wskazanych stanowiskach w firmach przez Exa, bez budowania list prospektów.
  • 100prospecting
    Pomaga znajdować, kwalifikować i układać listy prospektów do kontaktu w B2B SaaS, ogólnym B2B i lokalnych małych firmach, z targetowaniem kont zgodnych z ICP i listą outbound.
  • 10033-b2b-lead-gen-global
    Prowadzi pracę nad lejkiem B2B: listy kont, sekwencje cold mail i LinkedIn, punktację leadów i higienę CRM.
  • 95prospecting
    Znajduje i kwalifikuje potencjalnych klientów oraz buduje listę prospektów dla B2B SaaS, ogólnego B2B i lokalnych małych firm, w tym listy kont dopasowanych do ICP.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.