Data Enrichment
v1.0.1Enrich company and contact lists with public data — firmographics, technographics, social profiles, funding history, and employee count estimates. Clean, ded...
⭐ 0· 114·0 current·0 all-time
by@tktk-ai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (company/contact enrichment, firmographics, technographics, scoring) matches the instructions and reference docs. The skill only uses public sources (LinkedIn, Crunchbase, BuiltWith/Wappalyzer, news), which is consistent with enrichment.
Instruction Scope
SKILL.md is instruction-only and stays focused on enrichment/cleaning/scoring tasks. It assumes the agent will fetch public web data but does not prescribe reading unrelated local files or environment secrets. However, instructions are fairly open-ended about how to collect public data (scraping vs API), which could lead to broad web queries or scraping behavior if not constrained.
Install Mechanism
No install spec and no code files are present, so nothing will be written to disk or executed by an installer. This is the lowest-risk pattern for a skill of this type.
Credentials
The skill requests no environment variables or credentials, which is proportionate for an instruction-only public-data enrichment skill. One caveat: some listed data sources (Crunchbase, BuiltWith, LinkedIn) often require API keys or paid access in practice; the SKILL.md does not request or document those credentials, so an implementer would likely need to supply them externally.
Persistence & Privilege
Skill is not always-enabled, does not require system-level changes, and contains no installation logic. It does not request elevated or persistent privileges.
Assessment
This skill is internally consistent with public-data enrichment, but consider the following before installing: (1) Several named data sources (Crunchbase, BuiltWith, LinkedIn) often require API keys or paid access and may impose rate limits — plan how you'll supply and protect any keys if you use them. (2) The instructions allow broad web lookups/scraping; ensure you have permission and are compliant with provider Terms of Service and privacy laws (e.g., GDPR) before enriching personal contact data. (3) Because it's instruction-only, the agent will decide how to gather data — restrict scope in prompts (use approved APIs, rate limits, and only public sources) and verify results before importing into CRMs. (4) If you need automated, reliable access to those third-party services, add explicit, minimal environment variables for needed API keys rather than letting the agent attempt ad-hoc scraping.Like a lobster shell, security has layers — review code before you run it.
latestvk97caws90rq5p93bvphj9p96dd84g38a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.