인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
데이터 및 연구 · SKILL.md

lead-research

lead-research

Research potential leads with verified contact information, professional backgrounds, company context, and social presence. Combines LinkedIn profiling, email verification, company enrichment, and social signals for sales-ready prospect intelligence.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: lead-research description: "Research potential leads with verified contact information, professional backgrounds, company context, and social presence. Combines LinkedIn profiling, email verification, company enrichment, and social signals for sales-ready prospect intelligence."

Lead Research

Research potential leads with verified contact information, professional backgrounds, company context, and social presence. Combines LinkedIn profiling, email verification, company enrichment, and social signals for sales-ready prospect intelligence. Read the API map before selecting a capability.

Call SandBase capabilities

Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with sandbase_discover(q: "<provider and capability>"); use its returned name in sandbase_inspect(name: "<returned name>"). Read inputSchema, pricing, and execute_as, then call sandbase_run using execute_as.arguments.name and schema-defined arguments. If a run_id is returned, poll sandbase_run_get(run_id: "<returned run_id>") within the task budget until completed or failed; report pending or failed runs without resubmitting them automatically.

Capability identifiers

  • apollo_company_enrich
  • strale_lead_email_verify
  • strale_prospect_profile
  • agentbody_linkedin_email
  • agentbody_linkedin_profile
  • linkedin_web_v2_user_profile

Workflow

  1. Understand the user's research question, target, and context.
  2. Resolve each selected capability with sandbase_discover, then inspect the returned name with sandbase_inspect to confirm the schema and pricing.
  3. Follow execute_as with sandbase_run; collect async results with sandbase_run_get as described above.
  4. Synthesize findings into a clear, evidence-backed answer.
  5. Cite sources, note evidence gaps, and separate observations from interpretations.

Guidelines

  • Always call sandbase_inspect before using any capability.
  • Cite sources and preserve attribution (URLs, usernames, dates, metrics).
  • Separate factual observations from analysis and recommendations.
  • If data is unavailable, note the gap and continue with available evidence.
  • Read-only research only. Never take actions on platforms.
저장한 Skills