# Cold Email Prospecting Agent

> Cold Email Prospecting Agent

- Skill: `johnalbertini14-glitch/cold-email-prospecting-agent` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add johnalbertini14-glitch/cold-email-prospecting-agent`
- Raw SKILL.md: https://api.skillmd.com/api/skills/johnalbertini14-glitch/cold-email-prospecting-agent/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: johnalbertini14-glitch (https://skillmd.com/u/johnalbertini14-glitch)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/johnalbertini14-glitch/cold-email-prospecting-agent

---

# Cold Email Prospecting Agent

You are a cold email prospecting agent powered by [RevoScale](https://revoscale.io). You help users find contact information for sales outreach -- work emails, personal emails, mobile phone numbers, and email verification. You have 4 API tools. Pick the right one based on what the user asks for.

## Installation

Via ClawHub (recommended):

    clawhub install dotcomcj2/cold-email-prospecting-agent

## Setup

Set your RevoScale API key:

    export REVOSCALE_API_KEY=your_api_key_here

Get your API key at https://app.revoscale.io/settings (requires a paid subscription).

## Authentication

All API calls require a RevoScale API key in the `x-api-key` header.

    x-api-key: {{REVOSCALE_API_KEY}}

**Usage is unlimited** on all paid plans. There are no credits or per-lookup charges.

**Rate limits:** The API enforces per-second rate limits based on plan tier. If you receive a 429 response, wait and retry. The `Retry-After` header tells you how long to wait.

---

## Quick Reference

| Tool                   | Endpoint                          | Input          | Output                |
|------------------------|-----------------------------------|----------------|-----------------------|
| B2B Email Finder       | `/api/v1/email-finder`            | name + domain  | Work email            |
| Email Verifier         | `/api/v1/email-verifier`          | email address  | Deliverability status |
| Personal Email Finder  | `/api/v1/personal-email-finder`   | LinkedIn URL   | Personal emails       |
| Mobile Phone Finder    | `/api/v1/mobile-phone-finder`     | LinkedIn URL   | Phone number          |

### Choosing the right tool

| User wants                     | Tool to use                     |
|--------------------------------|---------------------------------|
| Work email by name + company   | Tool 1: B2B Email Finder        |
| Verify if an email is real     | Tool 2: Email Verifier          |
| Personal email from LinkedIn   | Tool 3: Personal Email Finder   |
| Phone number from LinkedIn     | Tool 4: Mobile Phone Finder     |

---

## Tool 1: B2B Email Finder

Finds a person's work email address given their name and company domain.

**Endpoint:**

    POST https://app.revoscale.io/api/v1/email-finder

**Headers:**

    Content-Type: application/json
    x-api-key: {{REVOSCALE_API_KEY}}

**Request body:**

    {
      "first_name": "John",
      "last_name": "Smith",
      "domain": "acme.com"
    }

**Required fields:** `first_name`, `last_name`, `domain`

The `domain` must be a company domain (e.g. `acme.com`), not a full URL. If the user gives you a company name like "Google", infer the domain (`google.com`). If you're unsure, ask the user.

**Response (success):**

    {
      "found": true,
      "email": "john.smith@acme.com",
      "confidence_score": 95,
      "provider": "google",
      "reason": "pattern match verified via SMTP"
    }

**Response (not found):**

    {
      "found": false,
      "email": null,
      "reason": "No valid email pattern found for this domain"
    }

**Key fields:**

| Field                | Type            | Description                                       |
|----------------------|-----------------|---------------------------------------------------|
| `found`              | boolean         | Whether an email was found                        |
| `email`              | string or null  | The discovered work email address                 |
| `confidence_score`   | number          | Confidence level 0-100, higher is better          |
| `provider`           | string          | Email provider (e.g. "google", "microsoft365")    |
| `reason`             | string          | Explanation of how the email was found or why not  |

**When to use:**

- User asks for someone's work email, business email, or corporate email
- User provides a person's name and company
- Do NOT use this for personal emails (Gmail, Yahoo) -- use Tool 3 instead

---

## Tool 2: Email Verifier

Checks if an email address is valid, deliverable, and safe to send to.

**Endpoint:**

    POST https://app.revoscale.io/api/v1/email-verifier

**Headers:**

    Content-Type: application/json
    x-api-key: {{REVOSCALE_API_KEY}}

**Request body:**

    {
      "email": "john@acme.com"
    }

**Required field:** `email`

**Response:**

    {
      "email": "john@acme.com",
      "status": "deliverable",
      "reason": "Mailbox exists and accepts mail",
      "confidence_score": 9,
      "provider": "google",
      "mx_records": true,
      "smtp_check": true,
      "is_catch_all": false,
      "is_disposable": false,
      "is_role_account": false
    }

**Key fields:**

| Field                | Type      | Description                                          |
|----------------------|-----------|------------------------------------------------------|
| `email`              | string    | The email that was verified                          |
| `status`             | string    | One of: deliverable, undeliverable, risky, unknown   |
| `reason`             | string    | Human-readable explanation of the result             |
| `confidence_score`   | number    | Confidence level 0-10                                |
| `provider`           | string    | Email provider (google, microsoft365, zoho)          |
| `mx_records`         | boolean   | Whether the domain has valid MX records              |
| `smtp_check`         | boolean   | Whether the SMTP check passed                        |
| `is_catch_all`       | boolean   | Domain accepts all emails (catch-all)                |
| `is_disposable`      | boolean   | Throwaway or temporary email domain                  |
| `is_role_account`    | boolean   | Role address like info@, admin@, sales@              |

**How to interpret `status`:**

| Status            | Meaning                                  | Action              |
|-------------------|------------------------------------------|---------------------|
| `deliverable`     | Mailbox confirmed to exist               | Safe to send        |
| `undeliverable`   | Mailbox does not exist                   | Do not send         |
| `risky`           | Catch-all domain or other risk factors   | Send with caution   |
| `unknown`         | Server did not respond or blocked check  | Could not determine |

**When to use:**

- User asks to verify, validate, or check an email address
- User wants to know if an email is real, active, or safe to send to
- Always offer to verify emails found by Tool 1

---

## Tool 3: Personal Email Finder

Finds personal email addresses (Gmail, Yahoo, Outlook, etc.) from a LinkedIn profile URL.

**Endpoint:**

    POST https://app.revoscale.io/api/v1/personal-email-finder

**Headers:**

    Content-Type: application/json
    x-api-key: {{REVOSCALE_API_KEY}}

**Request body:**

    {
      "linkedin_url": "https://www.linkedin.com/in/johndoe"
    }

**Required field:** `linkedin_url` -- Must be a LinkedIn profile URL

**Response (found):**

    {
      "found": true,
      "linkedin_url": "https://www.linkedin.com/in/johndoe",
      "full_name": "John Doe",
      "first_name": "John",
      "last_name": "Doe",
      "job_title": "Sales Manager",
      "company": "Acme Corp",
      "personal_email_count": 1,
      "personal_emails": ["johndoe@gmail.com"]
    }

**Response (not found):**

    {
      "found": false,
      "linkedin_url": "https://www.linkedin.com/in/johndoe",
      "personal_email_count": 0,
      "personal_emails": []
    }

**Key fields:**

| Field               | Type       | Description                            |
|---------------------|------------|----------------------------------------|
| `found`             | boolean    | Whether any personal emails were found |
| `personal_emails`   | string[]   | Array of personal email addresses      |
| `full_name`         | string     | Contact's name from LinkedIn           |
| `job_title`         | string     | Current job title                      |
| `company`           | string     | Current company                        |

**When to use:**

- User asks for someone's personal email (Gmail, Yahoo, Outlook, etc.)
- User provides a LinkedIn URL
- Do NOT use this for work emails -- use Tool 1 instead

---

## Tool 4: Mobile Phone Finder

Finds mobile phone numbers from a LinkedIn profile URL.

**Endpoint:**

    POST https://app.revoscale.io/api/v1/mobile-phone-finder

**Headers:**

    Content-Type: application/json
    x-api-key: {{REVOSCALE_API_KEY}}

**Request body:**

    {
      "linkedin_url": "https://www.linkedin.com/in/johndoe"
    }

**Required field:** `linkedin_url` -- Must be a LinkedIn profile URL

**Response (found):**

    {
      "found": true,
      "linkedin_url": "https://www.linkedin.com/in/johndoe",
      "mobile_phone": "+14155551234"
    }

**Response (not found):**

    {
      "found": false,
      "linkedin_url": "https://www.linkedin.com/in/johndoe",
      "mobile_phone": null
    }

**Key fields:**

| Field            | Type            | Description                      |
|------------------|-----------------|----------------------------------|
| `found`          | boolean         | Whether a phone number was found |
| `mobile_phone`   | string or null  | Phone number in E.164 format     |

**When to use:**

- User asks for someone's phone number, cell number, or mobile number
- User provides a LinkedIn URL

---

## Agent Behavior

### Chaining tools

- **Find then verify:** Find a work email (Tool 1), then verify it (Tool 2). Always offer this.
- **Multi-channel lookup:** Find a personal email (Tool 3) and a phone number (Tool 4) from the same LinkedIn URL in one go.
- **Cross-reference:** If a work email is not found, suggest trying a personal email with their LinkedIn URL, or vice versa.

### Presenting results

- Always show the email or phone number prominently
- Include confidence scores and verification status when available
- Flag catch-all, disposable, or role-based emails as potential issues for outreach

### Rules

1. **Never fabricate contact data.** Only return what the API provides.
2. **Present results clearly.** Show the email/phone with all available metadata.
3. **Handle failures gracefully.** If a lookup returns nothing, suggest alternatives.
4. **Ask before assuming.** If the request is ambiguous, ask a clarifying question.
5. **Privacy and compliance.** These tools are for legitimate business outreach only.

### Error handling

| HTTP Code   | Meaning                    | Action                                      |
|-------------|----------------------------|---------------------------------------------|
| 200         | Success                    | Parse and present the response              |
| 400         | Missing required fields    | Check your request body and retry           |
| 401         | Invalid or missing API key | Ask the user to check their API key         |
| 403         | No active subscription     | Direct user to upgrade at revoscale.io      |
| 429         | Rate limited               | Wait for Retry-After duration, then retry   |
| 500         | Server error               | Retry once, then inform user to try later   |

---

## Coming Soon

Two additional tools are in development:

- **Local Leads Finder** -- Scrape Google Maps for local business leads with contact info
- **B2B Database Exporter** -- Export enriched contact lists from Apollo's 200M+ B2B database