Lead Contact Finder
PassAudited by ClawScan on May 12, 2026.
Overview
The provided artifacts show a coherent public-contact search helper that uses Prismfy; the main user considerations are API-key handling, external query disclosure, and an optional persistent reminder hook.
Before installing, confirm you are comfortable sending the requested contact-search terms to Prismfy, keep the API key protected, and only enable the optional hook if you want recurring agent startup guidance for contact discovery.
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.
Your Prismfy API key will be used for searches and quota checks.
The helper authenticates to Prismfy with the user's API key. This is expected for the stated provider integration, but it means the skill uses a credential tied to the user's Prismfy account or quota.
-H "Authorization: Bearer $PRISMFY_API_KEY"
Use a dedicated or revocable Prismfy key if possible, avoid sharing shell history or dotfiles containing the key, and rotate the key if it is exposed.
Lead names, company names, domains, and related search terms may be visible to the Prismfy service.
The helper sends generated search payloads to Prismfy's external API endpoint. This is purpose-aligned, but person, company, domain, role, or geo search terms may leave the local environment.
API_URL="${PRISMFY_API_URL:-https://api.prismfy.io/v1/search}"Do not use the skill for confidential leads unless Prismfy's handling of that data is acceptable, and leave endpoint override variables unset unless you intentionally trust the alternate endpoint.
After enabling the hook, the agent may be more likely to remember and use this workflow for future outreach/contact tasks.
If the optional hook is copied and enabled, it adds a contact-discovery reminder to the agent's bootstrap context. This is disclosed and scoped, but it is persistent agent-context modification.
if (event.type !== "agent" || event.action !== "bootstrap") return; ... event.context.bootstrapFiles.push({ path: "CONTACT_DISCOVERY_REMINDER.md", content: REMINDER_CONTENT, virtual: true, });Enable the hook only if you want this recurring reminder, and disable or remove the hook if you do not want contact-discovery guidance injected at startup.