Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计提醒

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

Agent Skill

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

总安装

190

周安装

8

GitHub Stars

630

下载量

67
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

apollo-lead-finder 提供两阶段线索发现服务,先免费搜索联系人,再按需付费丰富数据以获取邮箱和电话。

  • 适合在销售拓展中快速定位潜在客户,支持创建 Apollo 列表和联系人,优先使用免费搜索降低前期成本。
  • 通过关键词筛选、结果预览和选择性丰富化,实现高效线索管理,适用于 B2B 外展和 CRM 集成场景。
  • 使用前需配置 Apollo API Key,注意权限范围及是否涉及敏感信息访问或批量写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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 resultsOnly 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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

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、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills