← ClaudeAtlas

06-resolution-email-personlisted

Turn a company domain (plus an optional person name or job title) into a verified, send-safe email address - the deliverability-first "resolution" layer of a cold-email pipeline. Use when the user wants to find or verify a work email, enrich a list or file of domains into decision-maker contacts, or resolve "who is the [title] at [company] and what's their email." Works standalone or as Layer 06 in the API-First GTM stack. Cost-ordered waterfall: AI Ark → Prospeo → Blitz → Findymail with ZeroBounce validation; a rung is skipped when its API key is absent, and it never spends enrichment credit without an explicit go-ahead.
Zevenue/headless-gtm · ★ 26 · AI & Automation · score 77
Install: claude install-skill Zevenue/headless-gtm
# Resolution - Email + Person Turn `{domain (required), optional person_name, optional job_title}` into a **verified, send-safe email**. The one principle that governs every decision here: **bounce rate, not find rate, is the signal that matters.** A found-but-undeliverable email is worse than no email - it burns sender reputation. So this skill optimizes for *deliverable* contacts at *minimum credit cost*, and it never spends enrichment credit without the user's explicit go-ahead. `domain` is the one mandatory input across every tool. Everything else can be asked for, inherited from upstream, or derived. ## Provider + auth setup Each provider reads its API key from an **environment variable** - `AIARK_API_KEY`, `PROSPEO_API_KEY`, `BLITZ_API_KEY`, `FINDYMAIL_API_KEY`, `ZEROBOUNCE_API_KEY` - never hardcode a key. This skill calls the providers with curl, and **a `.env` file is not visible to curl** - load it into the shell in the same command as the call, otherwise an empty auth header comes back as a provider auth error rather than a missing-key one: ```bash set -a; [ -f .env ] && . ./.env; set +a ``` An exported variable or a secrets manager takes precedence and needs no prelude. **The skill runs with as few as one key set:** at startup, detect which keys are present, use only those rungs, and skip the rest (log which rungs were skipped and why). Read **`references/providers.md`** for endpoints, request shapes, billing rules, and rate limits before making any call. -