Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

AI Cold Outreach System

v1.0.0

Complete cold email outreach system for AI agents. Handles lead generation via Apollo API, email enrichment, Saleshandy sequence creation, prospect import, w...

0· 52·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for joeytbuilds/ai-cold-outreach.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "AI Cold Outreach System" (joeytbuilds/ai-cold-outreach) from ClawHub.
Skill page: https://clawhub.ai/joeytbuilds/ai-cold-outreach
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install ai-cold-outreach

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-cold-outreach
Security Scan
Capability signals
CryptoCan make purchasesRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill's stated purpose (cold outreach using Apollo + Saleshandy) matches the included scripts and documentation, but the registry metadata claims 'Required env vars: none' and 'Primary credential: none' while both SKILL.md and the bundled scripts clearly require APOLLO_API_KEY and SALESHANDY_API_KEY (and the SKILL.md instructs exporting those keys). This mismatch is a coherence problem — the skill will not function without credentials but the package metadata doesn't declare them.
Instruction Scope
SKILL.md instructions stay within the outreach domain: searching/enriching leads with Apollo, importing to Saleshandy, checking warmup and using email templates. The instructions do not ask the agent to read unrelated system files or exfiltrate data outside the documented APIs. They do instruct full autonomous campaign operation ('no human in the loop'), which is consistent with the skill's purpose but increases operational risk (spam/compliance).
Install Mechanism
No install spec; this is instruction + shipped scripts. No downloads or archive extraction. Scripts are local Python files that call curl via subprocess — expected for this task and lower installation risk than remote fetches.
!
Credentials
Runtime requires service credentials (Apollo and Saleshandy API keys) and the SKILL.md also expects Google Workspace accounts and DNS control for sending domains. Those credentials are proportionate to the function, but the package metadata does not declare them. The omission reduces transparency and raises the chance users will accidentally supply more privileged credentials in the wrong place. No other unrelated secrets are requested in the code.
Persistence & Privilege
Skill is not marked always:true and does not request persistent installation or modification of other skills. It runs as user-invoked scripts and does not alter system-wide agent configuration.
What to consider before installing
This skill appears to implement the advertised outreach workflow, but the registry metadata omits required API keys (APOLLO_API_KEY, SALESHANDY_API_KEY). Before installing or running it: (1) treat those service API keys as sensitive and only provide the exact Apollo/Saleshandy keys this tool needs (prefer scoped/limited keys if available); (2) run the scripts in an isolated environment (separate project account and 'get-' sending domains) to avoid harming your main domain reputation; (3) verify the skill's publisher since no homepage or source is provided — lack of provenance lowers trust; (4) review and test the scripts locally to confirm they only call Apollo and Saleshandy endpoints (they do) and do not transmit data elsewhere; (5) ensure your use complies with email laws and your organization’s policies (cold outreach can trigger spam/abuse issues). If you need higher assurance, ask the publisher to update metadata to declare required env vars and provide provenance (source repo/homepage).

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

latestvk976kmbpq33gx0t0w84q6q5dbh850jve
52downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

AI Cold Outreach System

End-to-end cold email outreach managed by your AI agent. From lead discovery to sending sequences — no human in the loop.

Prerequisites

  • Apollo.io account with API key (Basic plan $59/mo for email enrichment)
  • Saleshandy account with API key (Outreach plan)
  • Google Workspace sending accounts (2+ domains recommended)
  • SPF, DKIM, DMARC configured on sending domains

Quick Start

1. Configure API Keys

Store keys in your workspace:

# Apollo
export APOLLO_API_KEY="your_key"

# Saleshandy  
export SALESHANDY_API_KEY="your_key"

Or save to a JSON config (see references/config-template.json).

2. Find Leads

Use the Apollo lead generation script to search for decision-makers:

python3 scripts/apollo-search.py --titles "Owner,Founder,CEO" --keywords "aesthetic clinic" --location "United States" --max 100

This outputs a CSV with: name, email, title, organization, city, state, country.

3. Enrich Emails

Search results don't include emails. Enrich them:

python3 scripts/apollo-enrich.py --input leads-raw.csv --output leads-enriched.csv

Uses Apollo's people/match endpoint (1 credit per enrichment). Budget ~500 credits for 300 verified emails.

4. Import to Saleshandy

python3 scripts/saleshandy-import.py --csv leads-enriched.csv --step-id "YOUR_STEP_ID" --api-key "YOUR_KEY"

5. Monitor Warmup

Check email account health before sending:

python3 scripts/check-warmup.py --api-key "YOUR_KEY"

Do NOT activate sequences until all accounts score 85+.

Architecture

Apollo API (lead gen) → CSV → Saleshandy API (import) → Email Sequence → Prospects
                                    ↑
                          Email Copy Templates (references/)

Key API Endpoints

Apollo

  • Search: POST /api/v1/mixed_people/api_search — find people by title, keyword, location
  • Enrich: POST /api/v1/people/match — get email from person ID (1 credit each)
  • Bulk Enrich: POST /api/v1/people/bulk_match — batch enrichment (use name+company, not IDs)

Saleshandy

  • Base URL: https://open-api.saleshandy.com
  • Auth Header: x-api-key: YOUR_KEY
  • List Sequences: GET /v1/sequences
  • Import Prospects: POST /v1/sequences/prospects/import-with-field-name
  • List Email Accounts: POST /v1/email-accounts
  • Add Account to Sequence: POST /v1/sequences/{id}/email-accounts/add

See references/api-reference.md for full endpoint documentation.

Email Copy Best Practices

See references/email-templates.md for proven templates.

Key rules:

  1. Short punchy lines. One thought per line.
  2. Story-driven. Every email tells a specific story with real results.
  3. Real numbers always. Never round. "$457,500" not "almost half a million."
  4. P.S. lines are punchlines. The best hook lives in the P.S.
  5. Never beg. Confident, almost amused tone.
  6. 3-step sequences minimum: Opener → Proof → Close
  7. 3-5 day gaps between steps

Deliverability Checklist

Before activating any sequence:

  • SPF record configured on sending domain
  • DKIM record configured and passing
  • DMARC record configured
  • Email accounts warming for 7-14 days minimum
  • Health scores above 85 on all accounts
  • Using "get" prefix domains for cold outreach (protect main domain)
  • Daily sending limits set conservatively (15-25/account/day to start)
  • Warmup tool running (Saleshandy built-in or TrulyInbox)

Troubleshooting

IssueFix
Apollo search returns 0 emailsEmails require enrichment — search only returns IDs
Apollo people/search returns 403Use /mixed_people/api_search endpoint instead
Saleshandy API "Invalid token"Header must be x-api-key not api-key or Authorization
Saleshandy import fails "conflictAction"Valid values: overwrite, noUpdate, addMissingFields
Emails going to spamCheck warmup scores, verify DKIM, reduce daily volume
Merge tags not renderingUse {{First Name}} format in Saleshandy content

Comments

Loading comments...