lead-discoverylisted

# Lead Discovery — 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. ## 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 ## What This Skill Does 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 --- ## Phase 1: Gather Business Context ### If the user provides a website 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