跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
数据与分析

enrich-lead

Enrich one professional or a supplied lead list/CSV and return a sourced contact card or enriched table with name, current title, employer, location, professional profile URL and employment history. Use for a name and company, a role at a named company, a professional profile URL or an email, even without an explicit search request. Include work email when asked, and company size, funding or technologies on request. Excludes discovering new prospects, organizational inboxes, private personal details and sending outreach.

firecrawl · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add firecrawl/firecrawl-claude-plugin --skill enrich-lead

技能说明


name: enrich-lead description: Enrich one professional or a supplied lead list/CSV and return a sourced contact card or enriched table with name, current title, employer, location, professional profile URL and employment history. Use for a name and company, a role at a named company, a professional profile URL or an email, even without an explicit search request. Include work email when asked, and company size, funding or technologies on request. Excludes discovering new prospects, organizational inboxes, private personal details and sending outreach.

Enrich supplied leads

Handle one professional or the people in a supplied list or CSV. Apply the workflow to each supplied identity without adding new prospects; use find-leads to build a new prospect list, not to resolve a supplied person or role.

  1. Use the Firecrawl MCP to look up the professional with people_company_enrich. Start from the supplied identifiers and requested fields. Give people (a name with a company or domain, a professional profile URL, an email or a phone) or companies (a domain, name or profile URL), up to 10 records per call in total. One call covers the provider choice: for each requested field Firecrawl tries the providers that accept those inputs one at a time, least expensive first, and stops when the field is found. A provider that finds the value is charged its listed price; a miss is free. Enrich companies only when employer identity needs resolution or requested company context needs enrichment. Set max_credits to the user's credit limit, or what remains of it, on every people_company_search and people_company_enrich call. people_company_enrich tries a provider only while its listed price fits what remains of max_credits, so read credits_used and report the fields the limit left unfilled. If a people_company_search call is refused with max_credits_exceeded, request fewer records or use a cheaper provider within the limit; if none fits, treat the providers as unavailable. Use people_company_search to find candidates when the supplied identifiers cannot identify the person. If the connection does not expose these tools, use Alexandria's people sources: discover people sources with alexandria_library_search using cat /library/people/README.md, and company sources using cat /library/companies/README.md when employer identity needs resolution or requested company context needs enrichment, unless complete matching contracts are already in context. Choose business person-search or enrichment sources whose filters, identifiers and fields fit the request. Read the selected input, output and billing contracts; use only their returned provider, capability and inputs. Take the least expensive path that answers the question. Catalogue matches are not person records.
  2. Resolve identity before enriching. For an ambiguous request such as a role at a company, search with supported title and company-domain filters, read the previews and select the matching person. Use the strongest supplied identifier the tool or selected contract accepts: a professional profile URL, an email, a phone number, or, for an Alexandria contract, that provider's person ID. For a name, include the employer and any supported location context; resolve a required company domain rather than guessing it. Check the returned identity and any match-confidence metadata against the supplied context; a successful response alone does not establish the match. Reuse an already resolved identity rather than searching again. Provider IDs are specific to their source; resolve identity again when switching providers. If a match returns no person, search with looser supported filters while retaining known identity constraints. For a single lead, if identity remains uncertain, show up to three plausible candidates and ask the user to choose. Never enrich a list of guesses or merge conflicting profiles.
  3. Run the needed searches and enrichment with those tools, or for Alexandria sources through alexandria_library_read with calls: [{provider, capability, options}], and inspect each result. For people_company_enrich, read each record's results and fields: fields names the provider behind each answer, whether an email was verified and whether its domain matched the company, and complete: false on a profile or firmographics marks the best partial answer, to report as partial. Empty results mean no provider returned a requested field, which is a missing field, not proof that the person does not exist. For other calls, read each provider's result, including inputs it reports as unmatched. Retrieve only missing requested fields or recheck existing values the user asked to correct or refresh; enrich the employer only for requested company context. Use field-selection options only when the contract supports them. Request work email only when the user asks for it, with contact_fields: ["work_email"], which returns the profile in the same call. Never request personal email or mobile, leave out any a provider returns anyway, and keep personal-email and phone-reveal options disabled. Show work email only when requested and returned as an actual address; masked values, unlock placeholders and availability flags are not addresses. Preserve provider verification labels without claiming independent verification or guaranteed deliverability. Do not repeatedly retry a blocked lookup. Retry a failed people or company provider only when it reports retryable: true. For each pending entry with a next_tool, call that tool after poll_after_seconds; report entries without one as pending. Never resend the original request. For Alexandria calls, if a provider reports an uncertain outcome, do not start a new request for that item: resend only the identical payload with the same requestId, which the platform treats as the same request without a second charge, or report the item as pending with its request ID. On a capacity or ra
阅读完整来源 ↗