Install any skill in seconds. Free to start, no credit card required.
Get Started Free →apify/apify-verified-email-finder
Builds a list of verified business emails from Google Maps, Google SERPs, or a user-supplied URL list. Verification happens inside the same Apify run — no third-party verifier needed.
Passed 17 of 22 test cases with the skill, and 6 of 22 without it.
and 10 more in the full report
11 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When building the input for an actor run targeting executive leadership and technology leads, which exact department string codes should be passed in `leadsEnrichmentDepartments`?
| Checked | Without skill | With skill |
|---|---|---|
| Uses c_suite for executive leadership | Missed | Passed |
| Uses engineering_technical or information_technology for technology leads | Passed | Passed |
The instructions your model reads when the skill loads.
Return a list of verified business emails by routing the user's input to the right Apify Actor and turning on the leads enrichment + email verification add-ons in a single run. No third-party verifier (Hunter, NeverBounce, Apollo) needed — verification happens inside the same Actor run.
(No need to check it upfront)
The skill supports two execution paths. Pick the one that matches your environment — Steps 4 and 5 show commands for both.
MCP path (default in Claude sessions, recommended). If the Apify MCP server is connected, no setup is needed — auth runs through the user's Apify account. Use the call-actor and get-dataset-items MCP tools.
Script path (CLI / scheduled / non-Claude execution). Requires:
.env file with APIFY_TOKEN--env-file support)Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Collect the six required anchor inputs
- [ ] Step 2: Route to the correct Actor (confirm if ambiguous)
- [ ] Step 3: Build the Actor input (verification always ON)
- [ ] Step 4: Run the Actor and wait
- [ ] Step 5: Apply the result-scope filter, deduplicate, and render
Ask all six as one block before any Actor call. Don't bundle Actor-specific optional fields (country code, language, max pages) into this round — surface those as follow-ups.
location query / SERP keyword / URL list. This drives the routing decision.c_suite, product, engineering_technical, design, education, finance, human_resources, information_technology, legal, marketing, medical_health, operations, sales, consulting. Default is any (leave the array empty), but ask every time.maximumLeadsEnrichmentRecords. Default 3, but ask every time.CSV or JSON. Ask every time.verified-only (default) — only leads with emailVerification.result == "ok". Safest for cold email.verified-plus-catchall — ok plus catch_all. Catch-all is often deliverable but unprovable.test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.