UI はローカライズ済みです。スキルの紹介と説明文書は選択した言語へ AI が自動翻訳し、コード・コマンド・パス・専門用語は原文のままです。原作者の文書が優先されます。
スキルを探す
データ・研究 · SKILL.md

data-enrichment

data-enrichment

Enrich any entity — companies, domains, emails, or people — with verified data from multiple sources. Combines Apollo, Strale, LinkedIn, and Akta data to fill gaps in your CRM, lead databases, or research datasets with production-quality enrichment.

Independent GitHub snapshot · Automated classification · Original documentation governs

スキルの説明

GitHub

name: data-enrichment description: "Enrich any entity — companies, domains, emails, or people — with verified data from multiple sources. Combines Apollo, Strale, LinkedIn, and Akta data to fill gaps in your CRM, lead databases, or research datasets with production-quality enrichment."

Data Enrichment

Enrich any entity — companies, domains, emails, or people — with verified data from multiple sources. Combines Apollo, Strale, LinkedIn, and Akta data to fill gaps in your CRM, lead databases, or research datasets with production-quality enrichment. 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_company_enrich
  • strale_email_validate
  • strale_whois_lookup
  • linkedin_web_v2_company_profile
  • akta_company_enrichment

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.
保存したスキル