lead-scraper
Extract business and contact information from directory pages and company websites.
What this skill does
# Lead Scraper ## Purpose Extract business and contact information from directory pages and company websites. ## Routing - Use when: Use when the user wants to extract business information, contact details, or lead data from websites. - Do not use when: Don't use for personal data harvesting without consent or for spam purposes. - Outputs: Structured business/contact data in table format. - Success criteria: Extracts accurate contact and business information from the target page. ## Trigger Examples ### Positive - Use the lead-scraper skill for this request. - Help me with lead scraper. - Use when the user wants to extract business information, contact details, or lead data from websites. - Lead Scraper: provide an actionable result. ### Negative - Don't use for personal data harvesting without consent or for spam purposes. - Do not use lead-scraper for unrelated requests. - This request is outside lead scraper scope. - This is conceptual discussion only; no tool workflow is needed. ## Parameters | Name | Type | Required | Description | |---|---|---|---| | url | string | Yes | URL of directory page or company website | ## Runtime Prompt - Current runtime prompt length: 959 characters. - Runtime prompt is defined directly in `../lead-scraper.json`.
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.