Lead Gen Research
v1.0.0Qualify sales prospects from company lists with social profiling, trigger event research, and personalized outreach angles. Saves 10+ hours/week on manual pr...
⭐ 0· 58·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
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and runtime instructions align: the skill converts input company/contact lists into profiles, trigger events, pain points, and outreach lines. It requests no binaries, env vars, or installs that would be unrelated to lead research.
Instruction Scope
SKILL.md limits actions to processing provided lists/CSVs and collecting publicly available information from LinkedIn, X, and company sites. It does not instruct reading arbitrary system files, environment variables, or sending outbound messages itself. Note: scraping/platform access methods are not specified — richer data may require credentials or APIs, which are not requested here.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing is written to disk by an installer; lowest-risk installation footprint.
Credentials
The skill declares no required environment variables, credentials, or config paths. This is proportional to the stated purpose. Caveat: to access private or authenticated endpoints on LinkedIn/X or to automate outreach, the user would need to supply credentials or pair with other skills — do not provide broad tokens unless necessary.
Persistence & Privilege
always:false and no install actions or config writes are present. The skill does not request persistent system-level privileges or to modify other skills. Agent autonomous invocation is allowed by platform default (not a fault of the skill).
Assessment
This skill appears coherent and does what it says: analyze lists and produce outreach-ready profiles using public sources. Before installing: (1) Understand that collecting data from LinkedIn/X at scale may require authentication and can violate platform terms—avoid supplying full account credentials unless you intend to authorize access; prefer dedicated API keys with limited scopes. (2) The skill does not itself send outreach, but pairing it with automation (email/DM sending) can lead to real-world contacting—ensure you comply with privacy laws and anti-spam rules. (3) Test on a small, non-sensitive batch first to confirm results and to ensure any scraping or automated lookups don't cause account/rate-limit issues. (4) Never provide unrelated secrets or wide-scope tokens to this skill; only grant the minimum access needed for a specific integration.Like a lobster shell, security has layers — review code before you run it.
latestvk975xtnvxzkqvzeh3amrtx8d8s84fetp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.