ClawHub

B2B Outbound Sniper

v1.0.2

Autonomous B2B outbound engine that turns job board hiring signals into qualified pipeline. 6 LLMs. Your own email. 10/10 deliverability. Battle-tested in 30...

⭐ 0· 47·0 current·0 all-time
by@getlemnos32
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (autonomous B2B outbound) match the included Python scripts and SKILL.md. The scripts only call Apify (indeed-scraper) and Hunter.io APIs, which is exactly what's needed to implement the stated workflow. Minor mismatch: marketing claims like "6 LLMs" and "10/10 deliverability" are unsupported by the code (there are no LLM calls in the included scripts), but this is a quality/marketing issue rather than a security incoherence.
✓
Instruction Scope
Runtime instructions are concrete (set APIFY_TOKEN, HUNTER_API_KEY, HUNTER_CAMPAIGN_ID, edit KEYWORDS, run scripts). The scripts only read those env/config values and operate on local files under the repo (config/apis.json, references/*.jsonl) and a /tmp lock file. They do not attempt to read unrelated system files, additional env vars, or exfiltrate data to unexpected endpoints beyond api.apify.com and api.hunter.io.
✓
Install Mechanism
No install spec; this is instruction + script delivery only. No download-from-URL or extracted archives, and all network calls in code target well-known API hosts (Apify and Hunter).
✓
Credentials
Required credentials (Apify token and Hunter API key and campaign ID) are appropriate and required by the declared functionality. The SKILL.md and code both expect the same env vars; code falls back to config/apis.json if present. There are no unrelated secrets requested.
✓
Persistence & Privilege
Skill is not forced always-on and does not modify other skills or system-wide settings. It writes tracking/results files under the repository and uses /tmp for a lock — standard behavior. Note: the skill is capable of autonomous operation (the platform default), which means it can run unattended and add leads to a campaign; this is expected for an outbound automation tool but has compliance implications.
Assessment
This package appears internally consistent for the advertised purpose, but review before running: 1) Confirm the GitHub/source link is valid and review any additional production code referenced there. 2) Keep your APIFY_TOKEN and HUNTER_API_KEY secret and do not commit config/apis.json with real keys. 3) The tool will autonomously add recipients to a Hunter campaign — ensure you control the Hunter account/campaign and that your use complies with CAN-SPAM, GDPR, and site scraping terms (Apify/Indeed). 4) The marketing claims ("6 LLMs", "10/10 deliverability") are unsupported by the included scripts — treat them as hype. 5) Run first in a safe/test environment and inspect the references/ files it creates (references/hunter-tracking.jsonl and references/scrape-results.json). 6) If you have legal or deliverability concerns, do not enable automated runs until you audit the campaign content, unsubscribe handling, and operational controls.

Like a lobster shell, security has layers — review code before you run it.

latestvk978gafgcyd3da6a1bx7dj168s83ptwf

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments