Back to Details

lead-discovery

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Lead Discovery — Orchestrator

线索发现 — Orchestrator

This is the entry point for all lead generation requests. Before any signal skill runs, this skill ensures the agent has enough business context to configure every downstream skill correctly.
这是所有线索生成请求的入口点。在任何信号skill运行之前，该skill会确保Agent拥有足够的业务上下文，以正确配置所有下游skill。

When to Use

适用场景

  • User asks to "find leads", "generate leads", "do outbound", "find prospects", or any variation
  • User mentions lead generation without specifying a particular signal source
  • User asks to run a specific signal skill but the agent has no business context yet
  • Always run this skill first — before github-repo-signals, job-signals, community-signals, competitor-signals, or event-signals
  • 用户要求「find leads」、「generate leads」、「开展外拓」、「寻找潜在客户」或任何类似表述
  • 用户提及线索生成但未指定具体信号来源
  • 用户要求运行特定信号skill但Agent暂无相关业务上下文
  • 请始终优先运行该skill — 优先级高于github-repo-signals、job-signals、community-signals、competitor-signals或event-signals

What This Skill Does

该skill的功能

  1. Learns about the user's business (via website or questions)
  2. Identifies competitors, ICP, and relevant technologies
  3. Generates the shared context object that all signal skills need
  4. Recommends which signal sources to run and in what order
  5. Hands off to individual signal skills with inputs pre-filled
  1. 了解用户的业务信息（通过网站或提问）
  2. 识别竞争对手、ICP和相关技术栈
  3. 生成所有信号skill所需的共享上下文对象
  4. 推荐需要运行的信号来源及执行顺序
  5. 携带预填的输入参数移交到各个信号skill

Phase 1: Gather Business Context

阶段1：收集业务上下文

If the user provides a website URL

如果用户提供了网站URL

Scrape the website (homepage, pricing page, about page, docs if available) and extract:
  1. Product description — one-liner of what the product does
  2. Category — the market category (e.g., observability, API platform, CI/CD, CRM)
  3. Target buyer — who the product is sold to (developers, DevOps, marketers, etc.)
  4. Key features — the 3-5 main capabilities
  5. Technology keywords — the technical terms associated with this product and space
  6. Pricing model — free tier, usage-based, seat-based, enterprise (helps qualify leads)
  7. Competitors mentioned or implied — from comparison pages, "alternative to" language, integrations
After extracting, present a summary to the user and ask them to confirm or correct.
爬取网站（首页、定价页、关于页，若有文档也一并爬取）并提取以下信息：
  1. 产品描述 — 用一句话说明产品的作用
  2. 所属类别 — 所属的市场分类（例如：可观测性、API平台、CI/CD、CRM）
  3. 目标客户 — 产品的售卖对象（开发者、DevOps、营销人员等）
  4. 核心功能 — 3-5项主要能力
  5. 技术关键词 — 和该产品及所属领域相关的技术术语
  6. 定价模式 — 免费版、按量付费、按席位付费、企业版（用于筛选合格线索）
  7. 提及或隐含的竞争对手 — 来自对比页面、「替代XX」的表述、集成列表
提取完成后，向用户展示摘要并请其确认或修正。

If the user does NOT have a website

如果用户没有网站

Ask these questions one conversational block at a time. Do NOT dump all questions at once.
Block 1 — The Basics:
  • What does your product do? (one sentence)
  • Who is your ideal buyer? (role, company size, industry)
  • What problem does it solve?
Block 2 — The Market (ask after Block 1 is answered):
  • Who are your main competitors? (even indirect ones)
  • What technologies or tools does your product integrate with or replace?
  • What does your tech stack look like? (helps identify GitHub repos)
Block 3 — Sales Context (ask after Block 2 is answered):
  • How do you sell today? (inbound, outbound, PLG, partnerships)
  • What's your price range? (helps filter lead quality — a $500/yr tool targets different companies than a $50k/yr platform)
  • Any specific companies or segments you're already targeting?
每次只询问一组对话问题，不要一次性抛出所有问题。
第一组 — 基础信息：
  • 你的产品是做什么的？（一句话说明）
  • 你的理想客户是谁？（角色、公司规模、行业）
  • 它解决了什么问题？
第二组 — 市场信息（用户回答完第一组后再提问）：
  • 你的主要竞争对手有哪些？哪怕是间接竞争对手也可以
  • 你的产品可以集成或替代哪些技术或工具？
  • 你的技术栈是什么样的？（用于识别相关GitHub仓库）
第三组 — 销售上下文（用户回答完第二组后再提问）：
  • 你目前的销售方式是什么？（ inbound、outbound、PLG、合作伙伴）
  • 你的价格区间是多少？（用于筛选线索质量 — 年费500美元的工具和年费5万美元的平台对应的目标公司完全不同）
  • 有没有你已经在触达的特定公司或细分领域？

Phase 2: Competitor & Ecosystem Research

阶段2：竞争对手与生态研究

Once you have the business context, research to fill gaps the user didn't provide:
获取业务上下文后，开展研究填补用户未提供的信息缺口：

Identify Competitors

识别竞争对手

  • Search the web for "[product category] alternatives", "[competitor name] vs", "best [category] tools 2025/2026"
  • Build a list of 5-10 direct and indirect competitors
  • For each competitor, note:
    • Name and website
    • GitHub repos (if open-source or has public repos)
    • Product Hunt slug (if launched there)
    • Greenhouse/Lever career page slug (for job signals)
  • 全网搜索「[产品类别] alternatives」、「[竞品名称] vs」、「2025/2026年最佳[类别]工具」
  • 整理5-10个直接和间接竞争对手的列表
  • 为每个竞争对手记录以下信息：
    • 名称和官网
    • GitHub仓库（如果是开源项目或有公开仓库）
    • Product Hunt标识（如果在该平台发布过）
    • Greenhouse/Lever招聘页标识（用于获取招聘信号）

Identify Relevant GitHub Repos

识别相关GitHub仓库

  • Search GitHub for repos in the product's technology space
  • Include: competitor repos, category-defining repos, popular libraries the ICP uses
  • Aim for 3-8 repos that the user's ideal buyers would star, fork, or contribute to
  • 在GitHub搜索产品所属技术领域的仓库
  • 包括：竞品仓库、定义类别的标杆仓库、ICP会使用的热门库
  • 目标是找到3-8个用户的理想客户会标星、Fork或贡献的仓库

Identify Community Watering Holes

识别社区聚集地

  • Which subreddits discuss this space?
  • Are there relevant HN threads or recurring topics?
  • Any Slack/Discord communities, forums, or newsletters? (note these even if we can't scrape them — useful context)
  • 哪些subreddit会讨论该领域的内容？
  • 有没有相关的HN帖子或 recurring话题？
  • 有没有相关的Slack/Discord社区、论坛或通讯？（哪怕我们无法爬取也要记录，是有用的上下文）

Identify Relevant Events

识别相关活动

  • What conferences does this ICP attend?
  • Any upcoming or recent events in the space?
Present your research findings to the user for confirmation before proceeding.
  • ICP会参加哪些会议？
  • 该领域有没有即将举办或近期刚结束的活动？
在继续下一步之前，向用户展示你的研究结果请其确认。

Phase 3: Build the Shared Context Object

阶段3：构建共享上下文对象

After Phases 1 and 2, you should have all of this:
SHARED CONTEXT
==============
Product:          [one-liner description]
Category:         [market category]
Website:          [URL or "none"]

ICP:
  Role:           [e.g., Backend engineers, DevOps leads, Engineering managers]
  Company size:   [e.g., 50-500 employees]
  Industry:       [e.g., SaaS, fintech, healthtech — or "any"]
  Tech stack:     [e.g., Kubernetes, Python, AWS]

Competitors:      [list with GitHub repos, PH slugs, career page slugs where found]
Technology keywords: [list of 10-20 relevant terms]
Problem statements:  [3-5 problems the product solves, as they'd appear in job posts or forum discussions]

GitHub repos to scan:    [3-8 repos]
Subreddits:              [5-10 relevant subreddits]
Job search queries:      [3-5 job title searches]
Greenhouse/Lever slugs:  [company career page slugs]
Product Hunt slugs:      [competitor PH slugs]
Conference/event names:  [if identified]
Present this to the user as a formatted summary. Ask them to confirm, add, or remove items.
完成阶段1和阶段2后，你应该获得了以下所有信息：
SHARED CONTEXT
==============
Product:          [one-liner description]
Category:         [market category]
Website:          [URL or "none"]

ICP:
  Role:           [e.g., Backend engineers, DevOps leads, Engineering managers]
  Company size:   [e.g., 50-500 employees]
  Industry:       [e.g., SaaS, fintech, healthtech — or "any"]
  Tech stack:     [e.g., Kubernetes, Python, AWS]

Competitors:      [list with GitHub repos, PH slugs, career page slugs where found]
Technology keywords: [list of 10-20 relevant terms]
Problem statements:  [3-5 problems the product solves, as they'd appear in job posts or forum discussions]

GitHub repos to scan:    [3-8 repos]
Subreddits:              [5-10 relevant subreddits]
Job search queries:      [3-5 job title searches]
Greenhouse/Lever slugs:  [company career page slugs]
Product Hunt slugs:      [competitor PH slugs]
Conference/event names:  [if identified]
将以上内容作为格式化摘要展示给用户，请其确认、补充或删除相关条目。

Phase 4: Recommend Signal Sources & Route

阶段4：推荐信号来源并路由

Based on the context, recommend which signal skills to run. Use this priority order:
基于上下文，推荐需要运行的信号skill，遵循以下优先级顺序：

Always recommend (free, high signal):

始终推荐（免费、高价值信号）：

  1. github-repo-signals — if relevant repos were identified and the ICP is technical/developer-facing
  2. job-signals (HN + RemoteOK + Greenhouse/Lever only) — free sources, detects hiring intent
  1. github-repo-signals — 如果识别到了相关仓库，且ICP是技术人员/面向开发者
  2. job-signals（仅HN + RemoteOK + Greenhouse/Lever） — 免费来源，可检测招聘意向

Recommend if relevant:

相关则推荐：

  1. community-signals (HN only — free) — if the ICP participates in developer communities
  2. competitor-signals — if competitors have PH launches, case studies, or recent press
  3. event-signals — if specific conferences/events were identified
  1. community-signals（仅HN — 免费） — 如果ICP会参与开发者社区
  2. competitor-signals — 如果竞品有Product Hunt发布、案例研究或近期媒体报道
  3. event-signals — 如果识别到了具体的会议/活动

Recommend with cost note:

推荐时标注成本：

  1. community-signals (add Reddit — ~$5-10) — broader community coverage
  2. job-signals (add LinkedIn/Google — ~$1-3) — broader job board coverage
  3. SixtyFour enrichment — after any signal skill produces output (~$0.05-0.20/lead)
Present the recommendation as a numbered plan with costs. Ask the user which sources they want to run — all of them, a subset, or just start with the free ones.
  1. community-signals（新增Reddit — 约5-10美元） — 覆盖更广的社区内容
  2. job-signals（新增LinkedIn/Google — 约1-3美元） — 覆盖更广的招聘平台内容
  3. SixtyFour 数据 enrichment — 任意信号skill生成输出后运行（约每条线索0.05-0.20美元）
将推荐内容作为带成本的编号计划展示给用户，询问用户想要运行哪些来源 — 全部、部分，或者仅从免费来源开始。

Handoff

移交执行

Once the user picks their sources, begin executing them in the recommended order. For each skill:
  • Invoke the appropriate skill (e.g., 
    /github-repo-signals
    , 
    /job-signals
    )
  • Pre-fill all inputs from the shared context (do NOT re-ask the user for information you already have)
  • Only ask skill-specific questions that weren't covered in the shared context (e.g., user limit for github-repo-signals)
  • After each skill completes, briefly summarize results and move to the next
用户选定来源后，按推荐顺序开始执行。针对每个skill：
  • 调用对应的skill（例如 
    /github-repo-signals
    、
    /job-signals
    ）
  • 从共享上下文中预填所有输入参数（不要重复询问用户你已经获取的信息）
  • 仅询问共享上下文中未覆盖的skill特定问题（例如github-repo-signals的用户数量限制）
  • 每个skill运行完成后，简要总结结果再进入下一个

Key Rules

核心规则

  1. Never jump straight to a signal skill without first understanding the business. Even if the user says "scan this GitHub repo", take 30 seconds to understand what they sell and who they sell to — it makes the output analysis 10x more useful.
  2. Don't ask all questions at once. Conversational blocks. If the user gives a website, you may not need to ask anything at all.
  3. Research fills gaps. If the user says "our competitors are X and Y", still research to find Z they may have missed. But present findings for confirmation — don't assume.
  4. Cost transparency. Always tell the user which sources are free and which cost money before running anything.
  5. Reuse context. Once the shared context is built, every downstream skill should inherit it. The user should never be asked the same question twice.
  6. Start small, scale up. Default recommendation: start with free sources, review results, then decide on paid sources. Don't push users to spend money upfront.
  1. 在未了解业务背景的情况下，绝对不要直接跳转到信号skill。即使用户说「扫描这个GitHub仓库」，也要花30秒了解他们卖什么、卖给谁 — 这会让输出分析的价值提升10倍。
  2. 不要一次性问完所有问题，要分对话块提问。如果用户提供了网站，你可能根本不需要提问。
  3. 通过研究填补信息缺口。如果用户说「我们的竞品是X和Y」，还是要做研究找出他们可能遗漏的Z，但要展示结果请用户确认 — 不要自行假设。
  4. 成本透明。运行任何内容之前，始终告知用户哪些来源是免费的、哪些需要付费。
  5. 复用上下文。共享上下文构建完成后，所有下游skill都应该继承这些信息，永远不要重复询问用户同一个问题。
  6. 从小规模开始，逐步扩展。默认推荐：从免费来源开始，查看结果后再决定是否使用付费来源，不要强迫用户 upfront 消费。