$npx -y skills add sales-skills/sales --skill sales-anymailfinderAnymail Finder platform help — email finder and verification tool with 97%+ delivery guarantee. Finds emails by person name, company/domain, decision-maker role, or LinkedIn URL, with bulk search up to 100K rows and a GeoLead Finder. Use when you can't find someone's email, need
| 1 | # Anymail Finder Platform Help |
| 2 | |
| 3 | Help the user with Anymail Finder platform questions — from Email Finder (by person, company, decision maker, or LinkedIn URL) through Email Verification, Bulk Email Search, GeoLead Finder, and Domain Email operations. Anymail Finder is a London-based email finder and verification tool (AMF Internet Services Limited, founded 2015) offering a 97%+ delivery guarantee on verified emails, a REST API with no rate limits, and a Chrome Extension for in-workflow lookup. |
| 4 | |
| 5 | ## Step 1 — Gather context |
| 6 | |
| 7 | |
| 8 | If `references/learnings.md` exists, read it first for accumulated knowledge. |
| 9 | |
| 10 | Ask the user: |
| 11 | |
| 12 | 1. **What area of Anymail Finder do you need help with?** |
| 13 | - A) Email Finder by Person — find a verified email from first name + last name + company/domain (1 credit per valid result) |
| 14 | - B) Email Finder by Company/Domain — find up to 20 email addresses at a company (1 credit) |
| 15 | - C) Email Finder by Decision Maker — role-based search (ceo, engineering, finance, hr, it, logistics, marketing, operations, buyer, sales) returning name, title, LinkedIn URL, email (2 credits per valid result) |
| 16 | - D) Email Finder by LinkedIn URL — extract email from a LinkedIn profile URL (1 credit) |
| 17 | - E) Email Verifier — validate an email address as valid/risky/invalid (0.2 credits) |
| 18 | - F) Bulk Email Search — process up to 100,000 rows asynchronously via JSON or CSV/Excel upload |
| 19 | - G) GeoLead Finder — location-based lead discovery |
| 20 | - H) Chrome Extension — browser-based email finding from any website |
| 21 | - I) Domain Email Count/Order/Download — count, order, and download all emails at a domain |
| 22 | - J) API — REST API setup, endpoints, authentication, webhooks |
| 23 | - K) Account / Billing — plans, pricing, credits |
| 24 | - L) Something else — describe it |
| 25 | |
| 26 | 2. **What's your role?** |
| 27 | - A) Sales / SDR / BDR |
| 28 | - B) RevOps / Sales ops |
| 29 | - C) Developer / engineer |
| 30 | - D) Growth / marketing |
| 31 | - E) Recruiter / talent acquisition |
| 32 | - F) Other |
| 33 | |
| 34 | 3. **What are you trying to accomplish?** (describe your specific goal or question) |
| 35 | |
| 36 | **If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context. |
| 37 | |
| 38 | Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit. |
| 39 | |
| 40 | ## Step 2 — Route or answer directly |
| 41 | |
| 42 | If the request maps to a specialized skill, route: |
| 43 | - Cross-platform enrichment strategy / multi-tool enrichment -> `/sales-enrich` |
| 44 | - Email deliverability / warmup strategy (not Anymail Finder-specific) -> `/sales-deliverability` |
| 45 | - Prospect list building strategy -> `/sales-prospect-list` |
| 46 | - Connecting Anymail Finder to other tools via middleware -> `/sales-integration` |
| 47 | - Hunter.io-specific questions -> `/sales-hunter` |
| 48 | - Apollo-specific questions -> `/sales-apollo` |
| 49 | - Prospeo-specific questions -> `/sales-prospeo` |
| 50 | - Tomba-specific questions -> `/sales-tomba` |
| 51 | - Enrich.so-specific questions -> `/sales-enrichso` |
| 52 | - GetProspect-specific questions -> `/sales-getprospect` |
| 53 | - Minelead-specific questions -> `/sales-minelead` |
| 54 | - Skrapp-specific questions -> `/sales-skrapp` |
| 55 | |
| 56 | Otherwise, answer directly from platform knowledge using the reference below. |
| 57 | |
| 58 | ## Step 3 — Anymail Finder platform reference |
| 59 | |
| 60 | **Read `references/platform-guide.md`** for detailed module documentation, pricing, integrations, and data model. |
| 61 | |
| 62 | *You no longer need the platform guide details — focus on the user's specific situation.* |
| 63 | |
| 64 | ## Step 4 — Actionable guidance |
| 65 | |
| 66 | Based on the user's specific question: |
| 67 | |
| 68 | 1. **Finding a specific person's email by name and company**: |
| 69 | 1. Call `POST /v5.1/find-email/person` with `full_name` and `company_name` or `domain` in the request body, with `Authorization: <your-api-key>` header (no Bearer prefix). This endpoint also accepts `linkedin_url` as a fallback |
| 70 | 2. Set your HTTP client timeout to at least 180 seconds — real-time searches can take up t |