Token导航 LogoToken导航

Agent Skill · 研究检索

apollo-lead-finder(阿波罗线索发现者)

apollo-lead-finder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

apollo-lead-finder 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 72,083。

总安装 190周安装 8GitHub Stars 630下载 67核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:apollo-lead-finder(阿波罗线索发现者)
来源仓库:https://github.com/gooseworks-ai/goose-skills
仓库路径:skills/apollo-lead-finder
安装命令:
npx skills add https://github.com/gooseworks-ai/goose-skills --skill apollo-lead-finder
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/gooseworks-ai/goose-skills --skill apollo-lead-finder

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

apollo-lead-finder 提供两阶段线索发现服务,先免费搜索联系人,再按需付费丰富数据以获取邮箱和电话。适合在销售拓展中快速定位潜在客户,支持创建 Apollo 列表和联系人,优先使用免费搜索降低前期成本。通过关键词筛选、结果预览和选择性丰富化,实现高效线索管理,适用于 B2B 外展和 CRM 集成场景。

使用前需配置 Apollo API Key,注意权限范围及是否涉及敏感信息访问或批量写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/apollo-lead-finder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/gooseworks-ai/goose-skills --skill apollo-lead…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

apollo-lead-finder 怎么安装?

在终端执行 npx skills add https://github.com/gooseworks-ai/goose-skills --skill apollo-lead-finder。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

apollo-lead-finder 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

apollo-lead-finder 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

apollo-lead-finder 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

apollo-lead-finder 用的人多吗?

公开数据是累计安装 190 次,近一周安装 8 次,下载 67 次,GitHub 630 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

apollo-lead-finder 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
apollo-lead-finder

阿波罗线索发现者 · 本页

190630接触敏感数据未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Apollo Lead Finder

Two-phase Apollo.io prospecting: free People Search for lead discovery, then selective paid enrichment to reveal emails and phone numbers. Creates Apollo lists and contacts.

Key advantage: Apollo People Search is free (no credits consumed). Credits are only spent when enriching contacts to reveal email/phone. This lets you search tens of thousands of leads at zero cost, review results, then selectively enrich only the best matches.

Prerequisites

Apollo API Key

Get your API key from Apollo.io Settings > Integrations > API. Add to .env:

APOLLO_API_KEY=your-api-key-here

That's it — one env var.

Phase 0: Intake

Ask the user these questions to build the Apollo filter config:

ICP Criteria

  1. What job titles are you targeting? (e.g., "VP of Sales", "Head of Growth")
  2. What seniority levels? Options: owner, founder, c_suite, partner, vp, director, manager, senior, entry
  3. Company size (employee range)? Format: "51,200" "201,500" "501,1000" "1001,5000"
  4. Geographic regions? (e.g., "United States", "San Francisco, California")
  5. Industry/keyword tags? (e.g., "SaaS", "Software", "FinTech")
  6. Any titles to exclude? (e.g., "intern", "assistant")
  7. Should we create an Apollo list with these contacts? (default: yes)
  8. How many results do you want? (test: 100, standard: 5,000, full: 50,000)

Map Answers to Config

Build the config JSON with Apollo's filter format:

{
  "client_name": "example-client",
  "search_config_name": "vp-sales-us-midmarket",
  "icp_segment": "sales-leaders",
  "apollo_filters": {
    "person_titles": ["VP of Sales", "Head of Sales", "Director of Sales"],
    "person_seniority": ["vp", "director"],
    "person_locations": ["United States"],
    "organization_num_employees_ranges": ["51,200", "201,500", "501,1000"],
    "q_organization_keyword_tags": ["SaaS", "Software"]
  },
  "enrichment_filters": {
    "exclude_titles_containing": ["intern", "assistant"]
  },
  "apollo_list_name_prefix": "example-sales-leaders",
  "create_apollo_list": true,
  "mode": "standard",
  "max_pages": 50
}

Available Apollo search filters:

  • person_titles — job title keywords (array of strings)
  • person_seniority — seniority levels: owner, founder, c_suite, partner, vp, director, manager, senior, entry
  • person_locations — geographic locations (array of strings)
  • organization_num_employees_ranges — employee count ranges, format "min,max" (e.g., "51,200")
  • q_organization_keyword_tags — company keyword tags (e.g., "SaaS", "Software")
  • person_not_titles — titles to exclude (array of strings)
  • q_organization_name — organization name search
  • organization_locations — company HQ locations

Phase 1: Search (FREE)

What the free search returns

Apollo's api_search endpoint returns limited preview data: Apollo person ID, first name, obfuscated last name, title, company name, and boolean flags (has_email, has_phone). No LinkedIn URLs, emails, or full names — those require enrichment.

Pipeline Steps

Step 1: Build Apollo search payload — Map config filters to Apollo People Search format.

Step 2: Search page 1 — Get first 100 results + total_entries for total count.

Step 3: Paginate — Fetch remaining pages (100 per page, up to mode cap). Apply title filters.

Step 4: Collect Apollo person IDs — Store the Apollo person IDs from search results for the enrich phase.

Step 5: Present preview — Show the user a sample of search results (first name, title, company) and total count. Ask for approval before enriching.

Mode Caps

ParameterTestStandardFull
Max pages150500
Max results1005,00050,000
Search credits000

Cost: FREE. People Search does not consume Apollo credits.

Database Write Policy

CRITICAL: Never export leads without explicit user approval.

The search phase is free. The enrich phase costs credits.

Required flow:

  1. Run search first (free) — review the results
  2. Present search results to the user: total matches, sample leads, title distribution
  3. Get explicit user approval before running enrich phase
  4. After enrichment, present the enriched results to the user before exporting
  5. Only export after the user confirms the results look good

Phase 2: Enrich (COSTS CREDITS)

Use the Apollo Bulk People Match API to enrich selected leads from Phase 1.

Pipeline Steps

Step 1: Load search manifest — Read the manifest JSON saved by the search phase. Contains Apollo person IDs.

Step 2: Load existing contacts for dedup — If the user has a CSV of existing contacts or a previous export, load LinkedIn URLs for dedup. If no existing data, skip dedup.

Step 3: Confirm credits — Display lead count and credit cost estimate. Wait for confirmation.

Step 4: Bulk enrich — Call /people/bulk_match with Apollo person IDs in batches of 10. Each match costs 1 credit. Returns full data: email, phone, LinkedIn URL, full name, location, company details.

Step 5: Dedup against existing contacts — Filter out leads whose LinkedIn URLs already exist in the user's contact list.

Step 6: Present results to user — Show enriched sample leads (names, titles, companies, email coverage) and ask for explicit approval before writing to the database.

Step 7: Export results — Only after user approval. Save enriched leads as CSV to the current working directory, or wherever the user prefers.

Mode Caps

ParameterTestStandardFull
Max enrichments105002,500
Credits used105002,500

Cost: 1 credit per contact enriched. Always run search first, review results, then selectively enrich.

Phase 3: Review & Refine

Present results:

  • Total matching — how many profiles match the filters in Apollo
  • New leads found — net-new profiles (after dedup)
  • Apollo list — name and link to the list in Apollo
  • Enriched — how many have emails revealed
  • Email coverage — percentage of enriched leads with valid emails
  • Top 10 leads — name, title, company preview

Common adjustments:

  • Too broad — add more filters (seniority, employee range, keyword tags)
  • Too narrow — broaden title list, remove location filters
  • Low email coverage — some contacts genuinely have no known email; try enriching more leads
  • Wrong ICP — adjust title include/exclude lists

Example Usage

Trigger phrases:

  • "Search Apollo for [titles] at [industries]"
  • "Find leads in Apollo matching my ICP"
  • "Find VP of Sales at SaaS companies in the US"
  • "Enrich the Apollo leads from last search"

Apollo API Reference

  • People Search: POST https://api.apollo.io/api/v1/mixed_people/api_search — FREE, returns Apollo IDs + preview data (first name, title, org name, boolean flags). No LinkedIn URLs or emails.
  • People Match (enrich): POST https://api.apollo.io/api/v1/people/match — 1 credit, reveals email/phone
  • Bulk People Match: POST https://api.apollo.io/api/v1/people/bulk_match — up to 10 per request, 1 credit each
  • Create List: POST https://api.apollo.io/api/v1/labels — create a named list
  • Create Contact: POST https://api.apollo.io/api/v1/contacts — add person to Apollo CRM + optional list
  • Auth: x-api-key: {APOLLO_API_KEY} header on all requests
  • Rate limit: Varies by plan. Handle 429 with Retry-After header.
  • Search Pagination: page param (1-indexed), per_page max 100

平台分布

Codex

37.12%
按下载量换算25

Claude

28.76%
按下载量换算19

Cursor

20.28%
按下载量换算14

Gemini CLI

9.9%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills