SafetyMails platform help — bulk email verification (up to 2M emails, 19-step algorithm), real-time API validation (JavaScript embed for forms), Email Finder (B2B corporate lookup), list cleaning, spamtrap/disposable/catch-all detection, integrations. Use when your email list has too many bounces, SafetyMails verification results look wrong, the JavaScript embed isn't catching bad emails on your forms, Email Finder isn't returning corporate addresses, or integrations aren't syncing verified results. Do NOT use for general deliverability strategy across tools (use /sales-deliverability), general enrichment strategy (use /sales-enrich), building prospect lists (use /sales-prospect-list), or connecting tools generically (use /sales-integration).
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
SafetyMails platform help — bulk email verification (up to 2M emails, 19-step algorithm), real-time API validation (JavaScript embed for forms), Email Finder (B2B corporate lookup), list cleaning, spamtrap/disposable/catch-all detection, integrations. Use when your email list has too many bounces, SafetyMails verification results look wrong, the JavaScript embed isn't catching bad emails on your forms, Email Finder isn't returning corporate addresses, or integrations aren't syncing verified results. Do NOT use for general deliverability strategy across tools (use /sales-deliverability), general enrichment strategy (use /sales-enrich), building prospect lists (use /sales-prospect-list), or connecting tools generically (use /sales-integration).
Help the user with SafetyMails platform questions — from bulk email verification and list cleaning through real-time API validation, Email Finder, integrations, and credit management.
SafetyMails is a Brazil-founded email verification platform with 8,000+ customers and 2B+ emails verified. ISO 27001 certified. Core strengths: bulk list cleaning (up to 2M emails), real-time JavaScript embed for form validation, and B2B corporate email finder.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
What area of SafetyMails do you need help with?
A) Bulk Email Verification — upload and clean an email list
B) Real-Time API — JavaScript embed for forms/landing pages
C) Email Finder — find corporate emails by name + domain
D) Free Tools — single email verifier, password generator, email name generator
E) Integrations — RD Station, HubSpot, Mailchimp, Zapier, etc.
F) Reporting & Analytics — verification result breakdowns
G) Account & Billing — credits, pricing, plans
H) Something else — describe it
What type of verification or lookup do you need?
A) One-time list cleaning before a campaign
B) Ongoing form validation (real-time)
C) Finding corporate email addresses (Email Finder)
D) Checking a single email address
E) Not sure yet
What's your goal? (describe your specific objective — e.g., "clean 50K contacts before a Mailchimp campaign", "add real-time validation to a WordPress form", "find emails for 200 prospects")
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.
Step 2 — Route or answer directly
If the request maps to a specialized skill, route:
General deliverability strategy (SPF/DKIM/DMARC, warmup, inbox placement) → /sales-deliverability
Enrichment strategy across tools (waterfall, CRM hygiene) → /sales-enrich
Building prospect lists / ICP definition → /sales-prospect-list
Connecting tools via Zapier/webhooks generically → /sales-integration
Otherwise, answer directly from platform knowledge using the reference below.
Step 3 — SafetyMails platform reference
Read references/platform-guide.md for the full reference — Bulk Email Verification (the 19-step algorithm, scale, credit cost), the Real-Time API (no-code <script> embed + custom HMAC-SHA256 REST call), Email Finder, free tools, reporting, the verification-status data model, the API quick reference, the integration list, and best-effort pricing. The verbatim API docs are in references/safetymails-api-reference.md.
Answer using only the relevant section for the user's question — don't dump the full reference.
Step 4 — Actionable guidance
Based on the user's specific question, provide step-by-step instructions:
Bulk list verification workflow
Prepare your list: Remove duplicates. Export as CSV, TXT, XLS, or XLSX with one email per row (or paste directly).
Upload: Log in at panel.safetymails.com → click "Verify List" → upload file or paste emails.
Wait for processing: SafetyMails runs the 19-step algorithm on every address. Small lists finish in minutes; large lists (1M+) take longer.
Review results: Check the breakdown by status (Valid, Invalid, Catch-All, Disposable, Spamtrap, Role-Based, Syntax Error, Domain Error).
Download clean list: Export only Valid emails for campaigns. Optionally include Catch-All with monitoring.
Import to your campaign tool: Upload the clean list to your ESP or campaign platform.
Re-verify regularly: Lists decay — re-verify every 3 months or before any major campaign.
Real-time API setup (JavaScript embed)
Get your API key: Log in at panel.safetymails.com → navigate to API settings → generate a key.
Requires subscription plan: API access is only available on monthly subscription plans, not pay-as-you-go.
Add JavaScript embed: Copy the JavaScript snippet from your SafetyMails dashboard and add it to your form page's HTML.
Configure validation: Set which form fields to validate, customize error messages, and define behavior for invalid entries.
Test: Submit your form with known valid, invalid, and disposable emails to confirm validation works.
Monitor: Check your SafetyMails dashboard for validation stats and credit consumption.
Email Finder workflow
Gather prospect info: You need first name, last name, and company domain for each lookup.
Run the lookup: Use the Email Finder tool in the SafetyMails panel — enter the name and domain.
Review results: Found emails are auto-verified. Note the credit cost: 7 credits per found email, 1 for risky domains, 0 if not found.
Budget credits: For a list of 200 prospects, budget up to 1,400 credits (200 x 7) in the best case. Actual cost will be lower if some emails aren't found.
Export and use: Add found emails directly to your campaign — no separate verification needed.
Gotchas
Best-effort from research — review these, especially items about pricing tiers and API limitations that may have changed.
Don't assume API access comes with every plan. The real-time JavaScript API requires a monthly subscription plan. Pay-as-you-go credits do not include API access. If you only need bulk verification, pay-as-you-go works. If you need form validation or real-time checks, you must subscribe.
Don't underestimate Email Finder credit cost. At 7 credits per found email, a batch of 500 lookups can cost up to 3,500 credits. Budget accordingly. The upside: you pay 0 credits when an email is not found, and only 1 credit for risky domains.
There IS a REST API — use HMAC, not a raw key. SafetyMails has a custom HTTP REST API for real-time validation (POST https://<TICKET_ORIGEM>.safetymails.com/api/<CODE_TICKET>) and a separate batch validation API (Swagger at panel.safetymails.com/swagger_api2.html). Auth is HMAC-SHA256: sign the email with your API Key and send the signature in the Sf-Hmac header — passing the raw API key as a token will fail. Official code examples (JS/PHP/Python/Java/Go) live at github.com/SafetyMails-Team/safetymails-sdk. The batch API needs support-issued credentials. Rate limits aren't published — confirm with support before high-volume use.
Don't send to Catch-All addresses without monitoring. Catch-All/Accept-All domains accept all emails at the SMTP level — SafetyMails cannot confirm individual mailbox existence. Including these in campaigns is a judgment call: they may be fine, or they may bounce. Monitor bounce rates closely if you include them.
Don't ignore spamtrap results. If SafetyMails flags addresses in your list as spamtraps, take it seriously. Even a single spamtrap hit can get your sending domain blocklisted. A high spamtrap rate in your list likely means the list was purchased, scraped, or hasn't been cleaned in a very long time — consider the source.
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.
/sales-integration — Connect SafetyMails to CRM and other tools via Zapier, Make, or direct integrations
/sales-prospect-list — Build targeted prospect lists with ICP definition and segmentation
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do
Examples
Example 1: Cleaning an email list before a Mailchimp campaign
User says: "I have 25,000 contacts in Mailchimp and want to verify them before sending a product launch email"
Skill does:
Recommends exporting the Mailchimp audience as CSV
Walks through uploading to SafetyMails for bulk verification (25,000 credits needed)
Explains how to interpret results — remove Invalid, Spamtrap, Disposable, Syntax Error, and Domain Error
Advises on handling Catch-All addresses (include with bounce monitoring or exclude for safety)
Points to the Mailchimp integration as an alternative to manual export/import
Result: Clean, verified list re-imported to Mailchimp with invalid and risky addresses removed
Example 2: Adding real-time validation to a landing page form
User says: "I want to stop fake emails from entering our HubSpot database through our demo request form"
Skill does:
Confirms a monthly subscription plan is needed for API access
Walks through generating an API key at panel.safetymails.com
Shows how to add the JavaScript embed to the landing page form
Recommends blocking Invalid, Disposable, and Role-Based addresses at the form level
Suggests custom error messages like "Please enter your corporate email address"
Result: Real-time form validation preventing invalid and disposable emails from entering HubSpot
Example 3: Finding corporate emails for a prospect list
User says: "I have a spreadsheet with 150 names and company domains — I need to find their email addresses"
Skill does:
Explains Email Finder: input first name + last name + domain, output is auto-verified corporate email
Calculates credit budget: up to 1,050 credits (150 x 7) for successful lookups, likely less
Walks through using the Email Finder in the SafetyMails panel for each prospect
Notes that found emails are auto-verified — no separate verification step needed
Points to /sales-enrich if the user also needs phone numbers, titles, or company data beyond what SafetyMails provides
Result: Verified corporate email addresses for the prospect list, ready for outreach
Troubleshooting
High percentage of Catch-All results
Symptom: A large portion of your list comes back as Catch-All/Accept-All, making it hard to judge list quality
Cause: Many corporate domains configure catch-all mail servers that accept all addresses — SafetyMails (and any verification tool) cannot confirm individual mailbox existence on these domains
Solution: Segment catch-all results separately. For high-value prospects on catch-all domains, include them in campaigns but monitor bounce rates per-send. For bulk campaigns, consider excluding catch-all addresses to protect sender reputation. If most of your list is catch-all, the list may skew toward large enterprises — this is normal.
API key not working / "Unauthorized" / {"Success": false, "ErrorCode": "401"}
Symptom: Script embed or REST API calls return authentication errors
Cause: Most often the HMAC signature is wrong (signing the wrong value, wrong key, or wrong header), or the key is invalid/expired, or your account is on a pay-as-you-go plan (which does not include API access)
Solution: For the custom REST API, send the signature in the Sf-Hmac header computed as HMAC_SHA256(value=email, key=API Key) — do NOT send the raw API key as the auth value. Confirm the <TICKET_ORIGEM> subdomain and <CODE_TICKET> path match the source created in the Real-time API panel, and that the body field is named exactly email. Verify your key at panel.safetymails.com → Real-time API. Confirm you are on a monthly subscription plan — pay-as-you-go does not include API access. For the script embed, check the ticket in the script URL has no extra spaces or line breaks. Cross-check against the language examples at github.com/SafetyMails-Team/safetymails-sdk.
Credits consumed faster than expected
Symptom: Credit balance dropping faster than anticipated, especially when using Email Finder
Cause: Email Finder costs 7 credits per found email (vs. 1 credit per bulk verification). Duplicate emails in uploaded lists also consume credits.
Solution: Deduplicate lists before uploading to avoid paying twice for the same email. Track Email Finder usage separately — 100 successful lookups cost 700 credits. Use the free single email verifier on the SafetyMails website for one-off checks instead of spending bulk credits. Review usage reports in your dashboard to identify where credits are going.
