Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use this skill when the user needs B2B lead collection via Apify actor LurATYM4hkEo78GVj (Apollo-like), including filter-based payload building, validated ru...
Use this skill when the user needs B2B lead collection via Apify actor LurATYM4hkEo78GVj (Apollo-like), including filter-based payload building, validated ru...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill runs the Apify actor LurATYM4hkEo78GVj to collect Apollo-style B2B leads with filters such as job title, seniority, location, employee size, industry, and email quality. Actor link: https://console.apify.com/actors/LurATYM4hkEo78GVj/source Use this skill when a user asks to: collect B2B contacts similar to Apollo workflows fetch leads with verified emails and optional phones build payloads for founders/execs by geo and industry run repeatable lead collection from script/API
Build validated actor input payloads. Run actor with secure token handling (APIFY_TOKEN env or --apify-token). Return normalized summary and raw lead rows. Support quick preset runs and custom JSON input.
Confirm target ICP (titles, seniority, location, company size, industries). Build payload with required lead count and enrichment switches. Run actor using scripts/apollo_like_leads_actor.py. Validate lead count and inspect sample rows. Export rows to n8n/Sheets/CSV as needed.
Preferred: export APIFY_TOKEN='apify_api_xxx' Alternative: python3 scripts/apollo_like_leads_actor.py run \ --apify-token 'apify_api_xxx' \ --input-json '{"max_results":50,"person_location_country":["United States"]}'
APIFY_TOKEN='apify_api_xxx' \ python3 scripts/apollo_like_leads_actor.py quick-founders-us-50
APIFY_TOKEN='apify_api_xxx' \ python3 scripts/apollo_like_leads_actor.py run \ --input-json '{ "max_results": 1000, "job_titles": ["CEO", "Founder", "Co-Founder"], "job_title_seniority": ["owner", "cxo"], "person_location_country": ["United States"], "employee_size": ["11-50", "51-200", "201-500"], "email_status": "verified", "include_emails": true, "include_phones": false }'
APIFY_TOKEN='apify_api_xxx' \ python3 scripts/apollo_like_leads_actor.py run \ --input-file references/sample_input.json
Script returns JSON with: ok actorId leadsCount inputUsed rows[] You can pass rows directly to n8n HTTP/Code nodes or map into Google Sheets columns.
Do not hardcode API keys in workflow templates. Keep max_results realistic for testing first (e.g., 50-200). Use email_status: "verified" for higher outreach quality. If the user wants phone-heavy output, set include_phones: true explicitly. Seniority values should match actor enum (owner, cxo, vp, director, etc.); this script auto-normalizes common Apollo values like founder -> owner.
references/actor-input-guide.md references/troubleshooting.md
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.