email-search

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Email Finder

Turn LinkedIn profiles into verified emails and phones. Takes the output of

people-search

and runs it through contact enrichment providers like Prospeo or Fullenrich.

将LinkedIn资料转换为已验证的邮箱和电话号码。接收

people-search

的输出结果，并通过Prospeo或Fullenrich等联系人数据增强提供商进行处理。

Related Skills

Extruct API Operations

Extruct API 操作

This skill delegates all Extruct API calls to the

extruct-api

skill.

For all Extruct API operations, read and follow the instructions in

skills/extruct-api/SKILL.md

The only Extruct operation in this skill is reading people table data. Contact enrichment uses separate providers (Prospeo, Fullenrich, etc.) with their own APIs.

本技能将所有Extruct API调用委托给

extruct-api

技能。

有关所有Extruct API操作，请阅读并遵循

skills/extruct-api/SKILL.md

中的说明。

本技能中唯一的Extruct操作是读取人脉表数据。联系人数据增强使用独立的第三方提供商（Prospeo、Fullenrich等）及其自有API。

Inputs

输入参数

Input	Source	Required
People table ID	Child table from `people-search`	yes (or CSV)
People CSV	`claude-code-gtm/csv/input/{campaign}/people_linkedin.csv`	yes (or table)
Provider preference	User choice	yes
Include mobile phones	User choice	no (default: no)

输入项	来源	是否必填
人脉表ID	`people-search` 生成的子表	是（或提供CSV文件）
人脉CSV文件	`claude-code-gtm/csv/input/{campaign}/people_linkedin.csv`	是（或提供表ID）
提供商偏好	用户选择	是
包含移动电话号码	用户选择	否（默认：否）

Choosing a Provider

选择提供商

Ask the user which contact enrichment provider they want to use. If they need guidance, consider:

Have LinkedIn URLs? → providers with LinkedIn enrichment work best
Need highest email hit rate? → waterfall providers try multiple sources
Budget-conscious? → check credit costs per match
Need mobile phones? → confirm the provider covers phone data
Want maximum coverage? → run one provider first, then a second for misses

If the user doesn't know where to start, pre-configured options with local reference docs are available in references/.

询问用户希望使用哪个联系人数据增强提供商。如果用户需要指导，请考虑以下因素：

是否有LinkedIn链接？ → 支持LinkedIn数据增强的提供商效果最佳
需要最高的邮箱命中率？ → 瀑布模式提供商可尝试多个数据源
关注预算？ → 查看每次匹配的信用成本
需要移动电话号码？ → 确认提供商是否覆盖电话数据
需要最大覆盖范围？ → 先使用一个提供商，再对未匹配的结果使用第二个提供商

如果用户不知道从何开始，[references/]目录中提供了带有本地参考文档的预配置选项。

Workflow

工作流程

Step 0: Confirm provider and learn API

步骤0：确认提供商并了解API

Ask the user which contact enrichment provider they want to use
Fetch or read the provider's API documentation and identify:
- Enrichment endpoint (single and bulk)
- Required input fields (LinkedIn URL, name, domain, etc.)
- Authentication method and credentials
- Throughput limits and request constraints
- Response format (email, phone, verification status)
- Credit/pricing model
Ask for their API credentials and confirm access
Plan the implementation and confirm with the user before proceeding

询问用户希望使用哪个联系人数据增强提供商
获取或阅读提供商的API文档，确定以下信息：
- 数据增强端点（单条和批量）
- 必填输入字段（LinkedIn链接、姓名、域名等）
- 认证方式和凭证
- 吞吐量限制和请求约束
- 响应格式（邮箱、电话、验证状态）
- 信用/定价模型
向用户索要API凭证并确认访问权限
规划实现方案，并在执行前与用户确认

Step 1: Load people data

步骤1：加载人脉数据

Option A: From Extruct people table (recommended) — Use the extruct-api skill to fetch data from the people table. Extract

full_name

profile_url

role

, and

parent_row_id

from each row. Split full name into first/last.

Option B: From CSV — Read

claude-code-gtm/csv/input/{campaign}/people_linkedin.csv

选项A：从Extruct人脉表加载（推荐） — 使用extruct-api技能从人脉表中获取数据。从每一行中提取

full_name

、

profile_url

、

role

和

parent_row_id

。将全名拆分为名和姓。

选项B：从CSV文件加载 — 读取

claude-code-gtm/csv/input/{campaign}/people_linkedin.csv

文件。

Step 2: Check credits

步骤2：检查信用额度

Before running enrichment, check the user's available credits or quota with the chosen provider (using the endpoint identified in Step 0). Present a cost estimate based on the number of contacts to enrich.

在运行数据增强之前，使用步骤0中确定的端点检查用户在所选提供商处的可用信用额度或配额。根据需要增强的联系人数量提供成本估算。

Step 3: Run enrichment

步骤3：运行数据增强

Using the chosen provider's API (from Step 0):

Prepare contact data in the format the provider expects (LinkedIn URL, name + domain, etc.)
Submit contacts in batches according to the provider's rate limits
Handle async responses if the provider uses polling
Collect results: emails, phone numbers, verification status
Track matched vs. unmatched contacts

If the user wants a waterfall (two providers), run the first provider, collect misses, then run misses through the second.

使用步骤0中选定的提供商API：

按照提供商要求的格式准备联系人数据（LinkedIn链接、姓名+域名等）
根据提供商的速率限制分批提交联系人
如果提供商使用轮询机制，处理异步响应
收集结果：邮箱、电话号码、验证状态
跟踪已匹配和未匹配的联系人

如果用户希望使用瀑布模式（两个提供商），先运行第一个提供商，收集未匹配的结果，再将这些结果通过第二个提供商处理。

Step 4: Deduplicate and clean

步骤4：去重和清洗

Deduplicate by email. Filter out:

Entries with no email
Results where the provider marks verification as invalid

按邮箱地址去重。过滤掉以下条目：

没有邮箱的条目
提供商标记为验证无效的结果

Step 5: Output contact CSV

步骤5：输出联系人CSV文件

Save enriched contacts to

claude-code-gtm/csv/input/{campaign}/contacts.csv

with columns:

first_name

last_name

email

email_verified

job_title

company_name

domain

linkedin_url

phone

location

source

将增强后的联系人数据保存到

claude-code-gtm/csv/input/{campaign}/contacts.csv

，包含以下列：

first_name

last_name

email

email_verified

job_title

company_name

domain

linkedin_url

phone

location

source

Step 6: Review with user

步骤6：与用户复核

Present summary:

Enrichment Results:
- Contacts submitted: N
- Emails found: N (X% hit rate)
- Emails verified: N
- Phones found: N
- No match: N
- Provider: [chosen provider]

Show a sample of 10 contacts for spot-checking:

Name	Title	Company	Email	Phone	Source
...	...	...	...	...	...

Ask:

"Hit rate look acceptable? (>60% is good, >80% is great)"
"Want to run the misses through another provider?"
"Ready to proceed to
```
email-generation
```
?"

展示汇总信息：

数据增强结果：
- 提交的联系人数量：N
- 找到的邮箱数量：N（命中率X%）
- 已验证的邮箱数量：N
- 找到的电话号码数量：N
- 未匹配数量：N
- 使用的提供商：[所选提供商]

展示10个联系人样本供抽查：

姓名	职位	公司	邮箱	电话	来源
...	...	...	...	...	...

询问用户：

“命中率是否符合预期？（>60%为良好，>80%为优秀）”
“是否需要将未匹配的结果通过另一个提供商处理？”
“是否准备好进入
```
email-generation
```
步骤？”

API References

API参考

Pre-configured provider docs in references/ directory. For other providers, docs are fetched during Step 0.

[references/]目录中提供了预配置的提供商文档。对于其他提供商，将在步骤0中获取相关文档。

email-search

Original

Translation

Email Finder

Email Finder

Related Skills

相关技能

Extruct API Operations

Extruct API 操作

Inputs

输入参数

Choosing a Provider

选择提供商

Workflow

工作流程

Step 0: Confirm provider and learn API

步骤0：确认提供商并了解API

Step 1: Load people data

步骤1：加载人脉数据

Step 2: Check credits

步骤2：检查信用额度

Step 3: Run enrichment

步骤3：运行数据增强

Step 4: Deduplicate and clean

步骤4：去重和清洗

Step 5: Output contact CSV

步骤5：输出联系人CSV文件

Step 6: Review with user

步骤6：与用户复核

API References

API参考