選項
首頁首頁 Skill 其他 lead-intelligence

lead-intelligence

affaan-m/ECC affaan-m/ECC

透過社交圖譜分析與暖線發掘,找出、鎖定並接觸高價值聯絡人,並為電子郵件、LinkedIn 及 X 生成個人化的聯繫草稿。

...展開全部
9
更新時間 2026-10-11

潛在客戶情報

這是一套由智能代理驅動的潛在客戶情報處理流程,透過社交圖譜分析與暖線路徑發掘,協助尋找、評分並接觸高價值聯絡人。

何時啟動

  • 使用者希望在特定產業中尋找潛在客戶或目標對象
  • 為建立合作夥伴關係、銷售或募資而建立外聯名單
  • 研究應聯繫的對象及最佳聯繫途徑
  • 使用者提及「尋找潛在客戶」、「外聯名單」、「該聯繫誰」、「暖場引薦」
  • 需要根據相關性對聯絡人清單進行評分或排序
  • 希望透過映射共同人脈,找出「暖介紹」的途徑

工具需求

必備

  • Exa MCP — 針對個人、企業及訊號的深網搜尋(web_search_exa)
  • X API — 追蹤者/被追蹤者關係圖、共同聯繫人分析、近期活動(X_BEARER_TOKEN,以及寫入上下文的憑證,例如 X_CONSUMER_KEY, X_CONSUMER_SECRET, X_ACCESS_TOKEN, X_ACCESS_TOKEN_SECRET)

可選(提升搜尋結果)

  • LinkedIn — 若有直接 API 則優先使用,否則透過瀏覽器控制進行搜尋、個人檔案檢視及草擬
  • Apollo/Clay API — 若使用者具備存取權限,則用於資料豐富化與交叉參照
  • GitHub MCP — 用於以開發者為中心的潛在客戶篩選
  • Apple Mail / Mail.app — 草擬冷聯絡或暖聯絡電子郵件,且不會自動發送
  • 瀏覽器控制 — 當 LinkedIn 和 X 的 API 支援不足或受限時使用

銷售管道概覽

┌─────────────┐     ┌──────────────┐     ┌─────────────────┐     ┌──────────────┐     ┌─────────────────┐
│ 1. Signal   │────>│ 2. Mutual    │────>│ 3. Warm Path    │────>│ 4. Enrich    │────>│ 5. Outreach     │
│    Scoring  │     │    Ranking   │     │    Discovery    │     │              │     │    Draft        │
└─────────────┘     └──────────────┘     └─────────────────┘     └──────────────┘     └─────────────────┘

外展前的語音準備

切勿直接套用通用銷售文案來撰寫外聯郵件。

在 brand-voice ,並重複使用其 VOICE PROFILE ,而非在該技能內臨時重新編寫風格。

若可存取 X 平台,請在起草前擷取最近的原創貼文;若不可行,則使用提供的範例或現有最佳的儲存庫/網站素材。

第一階段:訊號評分

在目標垂直領域中搜尋信號值高的人士。根據以下標準為每人分配權重:

信號 權重 來源
職務/職稱對應程度 30% Exa、LinkedIn
產業匹配度 25% Exa 公司搜尋
該主題的近期動態 20% X API 搜尋,Exa
追蹤者數/影響力 10% X API
地理位置鄰近度 10% Exa、LinkedIn
與您內容的互動 5% X API 互動

Signal 搜尋方法

# Step 1: Define target parameters
target_verticals = ["prediction markets", "AI tooling", "developer tools"]
target_roles = ["founder", "CEO", "CTO", "VP Engineering", "investor", "partner"]
target_locations = ["San Francisco", "New York", "London", "remote"]

# Step 2: Exa deep search for people
for vertical in target_verticals:
    results = web_search_exa(
        query=f"{vertical} {role} founder CEO",
        category="company",
        numResults=20
    )
    # Score each result

# Step 3: X API search for active voices
x_search = search_recent_tweets(
    query="prediction markets OR AI tooling OR developer tools",
    max_results=100
)
# Extract and score unique authors

第二階段:相互排名

針對每個已評分的目標,分析使用者的社交圖譜以找出最熱絡的路徑。

排序模型

  1. 擷取使用者的 X 追蹤清單及 LinkedIn 聯繫人
  2. 針對每個高訊號目標,檢查是否有共同聯繫人
  3. 套用 social-graph-ranker 模型來評分「橋接價值」
  4. 依據以下因素對共同聯繫人進行排序:
因素 權重
與目標的連結數 40% — 權重最高,連結數最多 = 排名最高
共同聯繫人的現任職務/任職公司 20% — 決策者 vs 個人貢獻者
聯繫對象的所在地 15% — 同城 = 更容易引薦
產業契合度 15% — 同屬垂直領域 = 自然介紹
對方的 X 帳號/LinkedIn 10% — 便於外展聯繫時辨識

標準規則:

Use social-graph-ranker when the user wants the graph math itself,
the bridge ranking as a standalone report, or explicit decay-model tuning.

在此技能中,請採用相同的加權橋接模型:

B(m) = Σ_{t ∈ T} w(t) · λ^(d(m,t) - 1)
R(m) = B_ext(m) · (1 + β · engagement(m))

解讀:

  • 第一層級:高 R(m) 且直接的橋接路徑 → 溫和引薦請求
  • 第 2 級:中等 R(m) 且為單跳橋接路徑 → 條件式引薦請求
  • 第三級:無可行橋接路徑 → 使用相同潛在客戶記錄進行直接冷聯繫

輸出格式


If the user explicitly wants the ranking engine broken out, the math visualized, or the network scored outside the full lead workflow, run `social-graph-ranker` as a standalone pass first and feed the result back into this pipeline.
MUTUAL RANKING REPORT
=====================

#1  @mutual_handle (Score: 92)
    Name: Jane Smith
    Role: Partner @ Acme Ventures
    Location: San Francisco
    Connections to targets: 7
    Connected to: @target1, @target2, @target3, @target4, @target5, @target6, @target7
    Best intro path: Jane invested in Target1's company

#2  @mutual_handle2 (Score: 85)
    ...

第三階段:暖引路徑發掘

針對每個目標,找出最短的引薦鏈:

You ──[follows]──> Mutual A ──[invested in]──> Target Company
You ──[follows]──> Mutual B ──[co-founded with]──> Target Person
You ──[met at]──> Event ──[also attended]──> Target Person

路徑類型(依關係親密度排序)

  1. 直接共同聯繫 — 雙方皆追蹤/認識同一人
  2. 投資組合連結 — 雙方皆曾投資或擔任目標公司的顧問
  3. 同事/校友 — 雙方曾任職於同一公司或就讀同一所學校
  4. 活動重疊 — 雙方皆曾參加同一場會議/計畫
  5. 內容互動 — 目標對象曾與共同聯繫人的內容互動,或反之

第 4 階段:資料豐富化

針對每條合格潛在客戶,請蒐集:

  • 全名、現任職稱、公司名稱
  • 公司規模、融資階段、近期新聞
  • 最近的 X 則貼文(過去 30 天)—— 主題、語氣、興趣
  • 與用戶的共同興趣(共同關注的對象、相似的內容)
  • 近期公司動態(產品發布、融資輪次、招聘)

資料豐富化來源

  • 範例:公司資料、新聞、部落格文章
  • X API:近期推文、個人簡介、追蹤者
  • GitHub:開源貢獻(針對以開發者為中心的潛在客戶)
  • LinkedIn(透過瀏覽器使用):完整個人檔案、工作經歷、學歷

第五階段:外聯草稿

針對每位潛在客戶生成個人化的聯繫草稿。草稿內容應符合根據來源資料所建立的語氣輪廓,並配合目標管道。

管道規則

電子郵件

  • 適用於最高價值的冷聯繫、暖介紹、投資者聯繫及合作邀約
  • 當本地桌面控制功能可用時,預設在 Apple Mail / Mail.app 中撰寫草稿
  • 請先建立草稿,除非使用者明確要求,否則勿自動發送
  • 主旨行應簡潔明確,避免花俏的措辭

LinkedIn

  • 當目標對象在該平台活躍、LinkedIn 上的共同人脈關聯性較強,或透過電子郵件聯繫的成功率較低時使用
  • 若可取得 API 存取權限,請優先使用
  • 否則,請使用瀏覽器控制功能來檢視個人檔案、近期活動,並草擬訊息
  • 內容應比電子郵件簡短,並避免虛假的專業熱情

X

  • 適用於高語境背景的操作者、創建者或投資者聯繫,此時公開發文行為至關重要
  • 搜尋、時間軸及互動分析時,應優先使用 API 存取
  • 必要時改用瀏覽器控制功能
  • 私訊與公開回覆應比電子郵件更簡潔,並應引用目標對象時間軸上的實際內容

管道選擇準則

依下列順序選擇一個主要管道:

  1. 透過電子郵件進行溫和的初步接觸
  2. 直接發送電子郵件
  3. LinkedIn 私訊
  4. X 私訊或回覆

僅在有充分理由且發送頻率不會讓人覺得像垃圾郵件時,才使用多管道策略。

暖場介紹請求(發送給共同聯絡人)

目標:

  • 一個明確的請求
  • 一個具體理由說明此引薦的合理性
  • 如有需要,應附上便於轉發的簡短說明

應避免:

  • 對公司進行過度說明
  • 堆砌社會證明
  • 聽起來像募款範本

直接冷聯繫(針對目標對象)

目標:

  • 從具體且近期的事項切入
  • 闡明為何雙方契合度極高
  • 提出一項低門檻的請求

應避免:

  • 泛泛的讚美
  • 羅列自身優點
  • 諸如「很樂意與您建立聯繫」這類籠統的請求
  • 刻意提出的修辭問句

執行模式

針對每個目標,需產出:

  1. 建議的溝通管道
  2. 該管道為何最合適的理由
  3. 訊息草稿
  4. 可選的後續草稿
  5. 若選擇電子郵件作為管道且可使用 Apple Mail,請建立草稿,而非僅回傳純文字

若可控制瀏覽器:

  • LinkedIn:檢視目標個人檔案、近期動態及雙方互動背景,然後起草或準備訊息
  • X:檢視近期貼文或回覆,接著起草私訊或公開回覆的內容

若可使用桌面自動化功能:

  • Apple Mail:建立包含主旨、內文及收件者的電子郵件草稿

未經使用者明確批准,請勿自動發送訊息。

反模式

  • 缺乏個人化設定的通用範本
  • 長篇大論地闡述貴公司整體情況
  • 在一封郵件中提出多項要求
  • 缺乏具體細節卻假裝熟稔
  • 群發訊息中可見的合併欄位
  • 在電子郵件、LinkedIn 和 X 上重複使用完全相同的內容
  • 充斥平台制式化內容,而非作者真實的語氣

設定

使用者應設定以下環境變數:

# Required
export X_BEARER_TOKEN="..."
export X_ACCESS_TOKEN="..."
export X_ACCESS_TOKEN_SECRET="..."
export X_CONSUMER_KEY="..."
export X_CONSUMER_SECRET="..."
export EXA_API_KEY="..."

# Optional
export LINKEDIN_COOKIE="..." # For browser-use LinkedIn access
export APOLLO_API_KEY="..."  # For Apollo enrichment

代理程式

此技能包含位於 agents/ 子目錄中包含專用的代理程式:

  • signal-scorer — 根據相關性訊號搜尋並對潛在客戶進行排序
  • mutual-mapper — 映射社交圖譜連結並找出潛在客戶的暖聯絡路徑
  • enrichment-agent — 擷取詳細的個人檔案及公司資料
  • outreach-drafter — 生成個人化訊息

使用範例

User: find me the top 20 people in prediction markets I should reach out to

Agent workflow:
1. signal-scorer searches Exa and X for prediction market leaders
2. mutual-mapper checks user's X graph for shared connections
3. enrichment-agent pulls company data and recent activity
4. outreach-drafter generates personalized messages for top ranked leads

Output: Ranked list with warm paths, voice profile summary, and channel-specific outreach drafts or drafts-in-app

相關技能

  • brand-voice 用於標準化語音擷取
  • connections-optimizer 用於在進行外聯前,先進行「審核優先」的網路修剪與擴展
在 GitHub 上查看
---
name: lead-intelligence
description: Finds, scores, and reaches high-value contacts through social graph analysis and warm path discovery, generating personalized outreach drafts for email, LinkedIn, and X.
---

# Lead Intelligence

Agent-powered lead intelligence pipeline that finds, scores, and reaches high-value contacts through social graph analysis and warm path discovery.

## When to Activate

- User wants to find leads or prospects in a specific industry
- Building an outreach list for partnerships, sales, or fundraising
- Researching who to reach out to and the best path to reach them
- User says "find leads", "outreach list", "who should I reach out to", "warm intros"
- Needs to score or rank a list of contacts by relevance
- Wants to map mutual connections to find warm introduction paths

## Tool Requirements

### Required
- **Exa MCP** — Deep web search for people, companies, and signals (`web_search_exa`)
- **X API** — Follower/following graph, mutual analysis, recent activity (`X_BEARER_TOKEN`, plus write-context credentials such as `X_CONSUMER_KEY`, `X_CONSUMER_SECRET`, `X_ACCESS_TOKEN`, `X_ACCESS_TOKEN_SECRET`)

### Optional (enhance results)
- **LinkedIn** — Direct API if available, otherwise browser control for search, profile inspection, and drafting
- **Apollo/Clay API** — For enrichment cross-reference if user has access
- **GitHub MCP** — For developer-centric lead qualification
- **Apple Mail / Mail.app** — Draft cold or warm email without sending automatically
- **Browser control** — For LinkedIn and X when API coverage is missing or constrained

## Pipeline Overview

```
┌─────────────┐     ┌──────────────┐     ┌─────────────────┐     ┌──────────────┐     ┌─────────────────┐
│ 1. Signal   │────>│ 2. Mutual    │────>│ 3. Warm Path    │────>│ 4. Enrich    │────>│ 5. Outreach     │
│    Scoring  │     │    Ranking   │     │    Discovery    │     │              │     │    Draft        │
└─────────────┘     └──────────────┘     └─────────────────┘     └──────────────┘     └─────────────────┘
```

## Voice Before Outreach

Do not draft outbound from generic sales copy.

Run `brand-voice` first whenever the user's voice matters. Reuse its `VOICE PROFILE` instead of re-deriving style ad hoc inside this skill.

If live X access is available, pull recent original posts before drafting. If not, use supplied examples or the best repo/site material available.

## Stage 1: Signal Scoring

Search for high-signal people in target verticals. Assign a weight to each based on:

| Signal | Weight | Source |
|--------|--------|--------|
| Role/title alignment | 30% | Exa, LinkedIn |
| Industry match | 25% | Exa company search |
| Recent activity on topic | 20% | X API search, Exa |
| Follower count / influence | 10% | X API |
| Location proximity | 10% | Exa, LinkedIn |
| Engagement with your content | 5% | X API interactions |

### Signal Search Approach

```python
# Step 1: Define target parameters
target_verticals = ["prediction markets", "AI tooling", "developer tools"]
target_roles = ["founder", "CEO", "CTO", "VP Engineering", "investor", "partner"]
target_locations = ["San Francisco", "New York", "London", "remote"]

# Step 2: Exa deep search for people
for vertical in target_verticals:
    results = web_search_exa(
        query=f"{vertical} {role} founder CEO",
        category="company",
        numResults=20
    )
    # Score each result

# Step 3: X API search for active voices
x_search = search_recent_tweets(
    query="prediction markets OR AI tooling OR developer tools",
    max_results=100
)
# Extract and score unique authors
```

## Stage 2: Mutual Ranking

For each scored target, analyze the user's social graph to find the warmest path.

### Ranking Model

1. Pull user's X following list and LinkedIn connections
2. For each high-signal target, check for shared connections
3. Apply the `social-graph-ranker` model to score bridge value
4. Rank mutuals by:

| Factor | Weight |
|--------|--------|
| Number of connections to targets | 40% — highest weight, most connections = highest rank |
| Mutual's current role/company | 20% — decision maker vs individual contributor |
| Mutual's location | 15% — same city = easier intro |
| Industry alignment | 15% — same vertical = natural intro |
| Mutual's X handle / LinkedIn | 10% — identifiability for outreach |

Canonical rule:

```text
Use social-graph-ranker when the user wants the graph math itself,
the bridge ranking as a standalone report, or explicit decay-model tuning.
```

Inside this skill, use the same weighted bridge model:

```text
B(m) = Σ_{t ∈ T} w(t) · λ^(d(m,t) - 1)
R(m) = B_ext(m) · (1 + β · engagement(m))
```

Interpretation:
- Tier 1: high `R(m)` and direct bridge paths -> warm intro asks
- Tier 2: medium `R(m)` and one-hop bridge paths -> conditional intro asks
- Tier 3: no viable bridge -> direct cold outreach using the same lead record

### Output Format

```

If the user explicitly wants the ranking engine broken out, the math visualized, or the network scored outside the full lead workflow, run `social-graph-ranker` as a standalone pass first and feed the result back into this pipeline.
MUTUAL RANKING REPORT
=====================

#1  @mutual_handle (Score: 92)
    Name: Jane Smith
    Role: Partner @ Acme Ventures
    Location: San Francisco
    Connections to targets: 7
    Connected to: @target1, @target2, @target3, @target4, @target5, @target6, @target7
    Best intro path: Jane invested in Target1's company

#2  @mutual_handle2 (Score: 85)
    ...
```

## Stage 3: Warm Path Discovery

For each target, find the shortest introduction chain:

```
You ──[follows]──> Mutual A ──[invested in]──> Target Company
You ──[follows]──> Mutual B ──[co-founded with]──> Target Person
You ──[met at]──> Event ──[also attended]──> Target Person
```

### Path Types (ordered by warmth)
1. **Direct mutual** — You both follow/know the same person
2. **Portfolio connection** — Mutual invested in or advises target's company
3. **Co-worker/alumni** — Mutual worked at same company or attended same school
4. **Event overlap** — Both attended same conference/program
5. **Content engagement** — Target engaged with mutual's content or vice versa

## Stage 4: Enrichment

For each qualified lead, pull:

- Full name, current title, company
- Company size, funding stage, recent news
- Recent X posts (last 30 days) — topics, tone, interests
- Mutual interests with user (shared follows, similar content)
- Recent company events (product launch, funding round, hiring)

### Enrichment Sources
- Exa: company data, news, blog posts
- X API: recent tweets, bio, followers
- GitHub: open source contributions (for developer-centric leads)
- LinkedIn (via browser-use): full profile, experience, education

## Stage 5: Outreach Draft

Generate personalized outreach for each lead. The draft should match the source-derived voice profile and the target channel.

### Channel Rules

#### Email

- Use for the highest-value cold outreach, warm intros, investor outreach, and partnership asks
- Default to drafting in Apple Mail / Mail.app when local desktop control is available
- Create drafts first, do not send automatically unless the user explicitly asks
- Subject line should be plain and specific, not clever

#### LinkedIn

- Use when the target is active there, when mutual graph context is stronger on LinkedIn, or when email confidence is low
- Prefer API access if available
- Otherwise use browser control to inspect profiles, recent activity, and draft the message
- Keep it shorter than email and avoid fake professional warmth

#### X

- Use for high-context operator, builder, or investor outreach where public posting behavior matters
- Prefer API access for search, timeline, and engagement analysis
- Fall back to browser control when needed
- DMs and public replies should be much tighter than email and should reference something real from the target's timeline

#### Channel Selection Heuristic

Pick one primary channel in this order:

1. warm intro by email
2. direct email
3. LinkedIn DM
4. X DM or reply

Use multi-channel only when there is a strong reason and the cadence will not feel spammy.

### Warm Intro Request (to mutual)

Goal:

- one clear ask
- one concrete reason this intro makes sense
- easy-to-forward blurb if needed

Avoid:

- overexplaining your company
- social-proof stacking
- sounding like a fundraiser template

### Direct Cold Outreach (to target)

Goal:

- open from something specific and recent
- explain why the fit is real
- make one low-friction ask

Avoid:

- generic admiration
- feature dumping
- broad asks like "would love to connect"
- forced rhetorical questions

### Execution Pattern

For each target, produce:

1. the recommended channel
2. the reason that channel is best
3. the message draft
4. optional follow-up draft
5. if email is the chosen channel and Apple Mail is available, create a draft instead of only returning text

If browser control is available:

- LinkedIn: inspect target profile, recent activity, and mutual context, then draft or prepare the message
- X: inspect recent posts or replies, then draft DM or public reply language

If desktop automation is available:

- Apple Mail: create draft email with subject, body, and recipient

Do not send messages automatically without explicit user approval.

### Anti-Patterns

- generic templates with no personalization
- long paragraphs explaining your whole company
- multiple asks in one message
- fake familiarity without specifics
- bulk-sent messages with visible merge fields
- identical copy reused for email, LinkedIn, and X
- platform-shaped slop instead of the author's actual voice

## Configuration

Users should set these environment variables:

```bash
# Required
export X_BEARER_TOKEN="..."
export X_ACCESS_TOKEN="..."
export X_ACCESS_TOKEN_SECRET="..."
export X_CONSUMER_KEY="..."
export X_CONSUMER_SECRET="..."
export EXA_API_KEY="..."

# Optional
export LINKEDIN_COOKIE="..." # For browser-use LinkedIn access
export APOLLO_API_KEY="..."  # For Apollo enrichment
```

## Agents

This skill includes specialized agents in the `agents/` subdirectory:

- **signal-scorer** — Searches and ranks prospects by relevance signals
- **mutual-mapper** — Maps social graph connections and finds warm paths
- **enrichment-agent** — Pulls detailed profile and company data
- **outreach-drafter** — Generates personalized messages

## Example Usage

```
User: find me the top 20 people in prediction markets I should reach out to

Agent workflow:
1. signal-scorer searches Exa and X for prediction market leaders
2. mutual-mapper checks user's X graph for shared connections
3. enrichment-agent pulls company data and recent activity
4. outreach-drafter generates personalized messages for top ranked leads

Output: Ranked list with warm paths, voice profile summary, and channel-specific outreach drafts or drafts-in-app
```

## Related Skills

- `brand-voice` for canonical voice capture
- `connections-optimizer` for review-first network pruning and expansion before outreach

安裝 lead-intelligence

請下載並將技能檔案解壓縮至您的 .claude/skills/ 目錄中。

下載 ZIP

複製儲存庫並將技能檔案複製到您的專案中。

git clone https://github.com/affaan-m/ECC/tree/main/skills/lead-intelligence # Copy SKILL.md to your .claude/skills/ directory

複製 複製
快速設定: 將技能資料夾複製到 .claude/skills/ Claude 會自動偵測並使用該技能
儲存庫 affaan-m/ECC

相關技能

v4-new-features
更新時間 2026-08-04
multica-creating-agents
更新時間 2026-08-12
pixijs-application
更新時間 2026-08-04
tilemaps
更新時間 2026-08-04
OR