Lensmor Contact Finder
v1.2.0Find decision-makers and key contacts at exhibitor companies using the Lensmor API. "Who should I contact at this company?" / "找联系人" / "Entscheidungsträger f...
⭐ 0· 86·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, declared requirement (LENSMOR_API_KEY), and runtime instructions all align. The skill only needs the Lensmor API key to query contacts and produce prioritized outreach lists; no unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs the agent to check the LENSMOR_API_KEY, collect company and role inputs, call https://platform.lensmor.com/external/contacts/search with a Bearer token, and format results. This stays within the stated purpose. Note: the skill will transmit company names, role filters, and receive PII (names, titles, LinkedIn URLs, inferred seniority) to/from a third-party API — review data sharing and privacy implications before use.
Install Mechanism
No install spec or code is provided (instruction-only), so nothing is downloaded or written to disk during install. This is the lowest-risk install model.
Credentials
Only a single credential (LENSMOR_API_KEY) is required and declared as the primaryEnv. That is proportionate to the described API integration. The SKILL.md uses the key only for Authorization header to the Lensmor endpoint. Treat the key as sensitive and store/rotate it appropriately.
Persistence & Privilege
always:false and no config paths or system modifications are requested. The skill does not request persistent, elevated, or cross-skill configuration changes.
Assessment
This skill appears to do what it says: it uses your Lensmor API key to query Lensmor's contacts API and formats results for LinkedIn outreach. Before installing: 1) Confirm you have a legitimate Lensmor API key and understand the vendor's privacy/usage terms — the skill will send company names and role filters and receive personal data (names, titles, LinkedIn URLs). 2) Ensure sending that data to Lensmor complies with your organization's privacy rules and local regulations. 3) Store the LENSMOR_API_KEY securely, limit its scope if possible, and rotate it if exposed. 4) Review any downstream skills (e.g., trade-show-linkedin-templates) that will receive contact data or generate outreach to ensure their behavior and permissions are acceptable. Because this is instruction-only (no install), it won't write code to disk, but it will cause outbound API requests when used.Like a lobster shell, security has layers — review code before you run it.
latestvk9751qy86mz5mhrk9fctahj6yn841r25
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
EnvLENSMOR_API_KEY
Primary envLENSMOR_API_KEY