Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Healthcare Lead Generator
v1.0.0Scrapes healthcare providers and patient signals by niche and location, scores leads, extracts contacts, and generates personalized outreach and promo videos.
⭐ 0· 28·0 current·0 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 claims to use Apify scrapers, InVideo AI, and Claude for scraping, video production, and lead scoring. The SKILL.md's example input explicitly includes apify_token and invideo_api_key, yet the registry lists no required env vars/credentials and no primary credential. That is incoherent: a legitimate implementation would need API keys for Apify, InVideo, and likely an LLM/Claude key.
Instruction Scope
Runtime instructions direct large-scale scraping of Google Maps, directories, Reddit, Trustpilot, LinkedIn, forums and extraction of names, phones, emails and patient signals. This includes collection of potentially sensitive health-related posts (possible PHI) and automated outbound messaging. The SKILL.md does not define consent, de-identification, retention, encryption, or HIPAA-compliant handling despite claiming 'HIPAA-mindful' outreach.
Install Mechanism
No install spec and no code files (instruction-only), so nothing is written to disk by an installer — lower supply-chain risk. However, because all runtime behavior depends on external services/APIs, the agent will need network access and credentials; the absence of declared dependencies obscures what will actually be invoked.
Credentials
The SKILL.md shows it requires apify_token and invideo_api_key (and implicitly an LLM key for Claude and possibly LinkedIn credentials), but the registry declares no required env vars. That mismatch is disproportionate and unexplained. The skill also requests extraction of personal contact info and patient posts without specifying where/how secrets or outputs are stored.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request permanent presence or claim to modify other skills. Note: model invocation/autonomy is allowed by default; combined with the other red flags (undisclosed credentials and PHI collection) that could increase risk, but autonomy alone is not a reason to flag.
What to consider before installing
Before installing or using this skill, ask the publisher to: (1) provide a clear list of required API keys and how/where they are stored (do not paste org secrets into an unvetted skill); (2) explain data handling: how scraped data (especially health-related posts and personal contact details) will be stored, encrypted, retained, and deleted; (3) provide a documented HIPAA/compliance posture if you will process protected health information; (4) confirm which external services are actually used and obtain their ToS/robots policy compliance for scraping targets (Google, LinkedIn, etc. often prohibit automated scraping); (5) request an option to run on non-sensitive test data first and to limit scope (no patient posts) until you verify behavior; and (6) require use of a secret manager for credentials and audit logs for all external calls. If the publisher cannot answer these, do not supply real credentials or sensitive data and consider not installing.Like a lobster shell, security has layers — review code before you run it.
latestvk970c0qf68ya5s6qt4qrjshy7h84397b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.