Data Enricher
v1.0.0Enrich leads by finding verified emails via contact pages, Instagram, Hunter.io, and patterns, then format data for Notion with deduplication and batching.
⭐ 1· 1.7k·4 current·4 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The SKILL.md describes using the Hunter.io API and syncing/checking Notion, but the skill metadata declares no required environment variables or credentials. That is incoherent: Hunter.io requires an API key and Notion requires a token. The SKILL.md also lists specific models to use (ollama/llama3.2 and 'haiku'), which the metadata does not explain or constrain.
Instruction Scope
Runtime instructions tell the agent to fetch website contact pages and Instagram bios, call Hunter.io, perform email-guessing heuristics, check Notion for duplicates, and save batches to workspace/leads-enriched-YYYY-MM-DD.json. Those steps involve network access, scraping, and file writes — none of which are declared or constrained. The instructions also reference {HUNTER_API_KEY} and checking Notion but do not specify how credentials will be provided or how to authenticate.
Install Mechanism
No install specification and no code files are present; the skill is instruction-only. That reduces the risk of arbitrary code being downloaded or written to disk. (Instruction-only skills still require network and credential access during runtime.)
Credentials
The SKILL.md implicitly requires at least a HUNTER_API_KEY and some Notion API token or credentials to perform domain lookups and Notion deduplication/sync, but the metadata lists no required env vars. The absence of declared credentials is disproportionate to the described functionality and is a material omission.
Persistence & Privilege
always is false and the skill is user-invocable (normal). The instructions ask the agent to write JSON files into a workspace path and to check/sync Notion; these are ordinary but mean the agent will read/write local workspace files and use external APIs. There is no request to modify other skills or system settings.
What to consider before installing
Do not install or enable this skill until the author corrects its metadata. Specifically: 1) Require and document HUNTER_API_KEY and the Notion credential (NOTION_TOKEN or similar) in requires.env so you know what secrets the skill needs. 2) Confirm where workspace/leads-enriched-YYYY-MM-DD.json will be written and that you approve that file location and retention. 3) Verify legal/ToS/privacy implications of scraping websites and Instagram (and ensure you have permission to collect and store personal emails). 4) Ask the author to clarify the listed models ('haiku' for API calls is unusual) and to provide explicit instructions for authentication and rate limiting. 5) Only provide API keys with least privilege and consider using short-lived tokens or a dedicated account. If the author cannot or will not provide these clarifications, treat the skill as unsafe to run because it can collect and store contact data while not declaring the credentials it needs.Like a lobster shell, security has layers — review code before you run it.
latestvk9728tvsg688rryvb0bzad2msx80kqwg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.