B2B Outbound Sniper

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...

Security Scan

The skill's code, required credentials, and runtime instructions line up with its stated purpose (scrape job boards, verify emails via Hunter, and add leads to a Hunter campaign); nothing in the package requires unrelated credentials or installs arbitrary third-party code.

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.

Turn job board hiring signals into qualified outbound pipeline — fully automated, end-to-end. Built and battle-tested by Lemnos AI over 30 days of live production outreach.

The core insight: When a company posts a $70-80K admin role, they're 72 hours away from committing that budget. Show up before they sign the offer letter.

What's Included

All scripts are bundled in this package — no external dependencies beyond Python + pip:

File	Purpose
scripts/scrape.py	Daily Apify scrape → Hunter verify → campaign load
scripts/hunter_campaigns.py	Campaign metrics, add/remove leads
config/apis.json.example	Config template — copy to config/apis.json, never commit

Required Credentials

Three API keys needed — set as environment variables or copy config/apis.json.example → config/apis.json:

Key	Where to get it	Cost
APIFY_TOKEN	console.apify.com	~$0.25/day at 50 results/keyword
HUNTER_API_KEY	app.hunter.io/api-key	Starter $49/mo (2,000 verifications)
HUNTER_CAMPAIGN_ID	app.hunter.io/campaigns	Included with Hunter account

Security note: Never commit config/apis.json with real keys. Add it to .gitignore. All scripts accept env vars as first priority — no keys ever need to touch source files.

Setup (5 minutes)

# 1. Copy config template
cp config/apis.json.example config/apis.json

# 2. Fill in your keys
nano config/apis.json

# 3. Edit your target keywords in scripts/scrape.py
#    Change the KEYWORDS array to match your vertical + geography

# 4. Run your first scrape
python3 scripts/scrape.py

How It Works

Daily (7 AM, Mon–Fri via OpenClaw heartbeat)
  → Apify scrapes KW-1 (50 results max)
  → Filter: target geography only, exclude job board domains
  → Hunter domain-search: 90%+ confidence emails only
  → Dedup: fetch all existing campaign recipients via API (ground truth)
  → Add net-new verified leads to Hunter campaign
  → Log to references/hunter-tracking.jsonl
  → 15-min gap → KW-2 → repeat for all keywords

Hunter handles the full send sequence automatically:

• Day 1: Initial outreach
• Day 3: Follow-up bump
• Day 7: Breakup email

Campaign Metrics

python3 scripts/hunter_campaigns.py metrics YOUR_CAMPAIGN_ID

Production Results (30-Day Run, CRE Vertical)

• 52.9% open rate on cold outreach
• Sub-3% bounce rate enforced by 90%+ confidence gate
• 0 spam complaints across 150+ sends
• Fully autonomous: scrape → verify → load → send → follow-up, no human in the loop

Customizing Keywords

Edit KEYWORDS in scripts/scrape.py:

KEYWORDS = [
    {"label": "KW-1", "query": "office manager",           "location": "New Jersey"},
    {"label": "KW-2", "query": "operations coordinator",   "location": "New York"},
    {"label": "KW-3", "query": "executive assistant",      "location": "South Florida"},
]

Any Indeed-searchable query + US location works. One keyword per run, 15-min gap between each.

A/B Testing

Run multiple Hunter campaigns with different CTAs and compare open/reply rates:

python3 scripts/hunter_campaigns.py metrics 111111   # Version A
python3 scripts/hunter_campaigns.py metrics 111112   # Version B

Compliance Note

This tool sends commercial email. You are responsible for compliance with CAN-SPAM, GDPR, and your jurisdiction's anti-spam laws. Use only verified business email addresses and always include an unsubscribe mechanism (Hunter.io handles this automatically in campaigns).

Infrastructure Cost

Service	Cost
Apify (50 results × 5 KWs/day)	~$7.50/month
Hunter.io Starter	$49/month
Total	~$57/month

Full Source Code

github.com/getlemnos32/b2b-outbound-sniper

Full production scripts, reference files, webhook listener, and docs. Review before deploying — all code is open source and auditable.

⭐ If This Fills Your Pipeline

Star it on ClawHub: clawhub.com/skills/b2b-outbound-sniper

Built by Lemnos AI — AI operations for businesses that can't afford to hire.