Data Enricher
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent for lead enrichment, but users should be aware it implies use of Hunter.io/Notion credentials, external lookups, and storage of enriched contact data.
Before installing, confirm you are comfortable with the agent looking up lead contact details on external sites and Hunter.io, using scoped Hunter.io/Notion access, writing to the intended Notion database only, and retaining enriched lead files in the workspace.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may use a third-party API key to look up email addresses for lead domains.
The skill expects use of a Hunter.io API key for domain-search calls. This is purpose-aligned, but users should provide a scoped key and note that the registry metadata declares no required credentials.
api_key={HUNTER_API_KEY}Use a dedicated Hunter.io key with limited scope or quota, and avoid sharing keys across unrelated workflows.
The agent could add lead records to a Notion workspace or database if connected to one.
The skill implies reading from and writing to a Notion lead database. This matches the purpose, but it is still a writable business-data integration that should be scoped by the user.
Before adding any lead: ... Check if domain_key exists in Notion ... Format all data before Notion sync
Confirm the intended Notion database, review batches before sync, and use permissions limited to the relevant lead pipeline.
Enriched email/contact data may remain in the workspace after the task is complete.
The skill persists enriched lead data, including contact emails, to a workspace file. This is expected for batching but creates a retained copy of contact data.
Save formatted batch to workspace/leads-enriched-YYYY-MM-DD.json
Store the workspace file in an appropriate location, restrict access, and delete old batches when no longer needed.