Overview Install Files 2 SecuritySummary This source did not publish a separate summary. Review SKILL.md before using the skill.
Lead Generation
Scrape leads from multiple platforms using Apify Actors.
When to Use
You need business, creator, or contact leads from maps, search, social, or video platforms.
The task involves selecting an Apify Actor to discover prospects and extract outreach data.
You need exported lead data plus a concise summary of lead quality or segmentation.
Prerequisites
(No need to check it upfront)
.env file with APIFY_TOKEN
Node.js 20.6+ (for native --env-file support)
mcpc CLI tool: npm install -g @apify/mcpc
Workflow
Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Determine lead source (select Actor)
- [ ] Step 2: Fetch Actor schema via mcpc
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the lead finder script
- [ ] Step 5: Summarize results
Step 1: Determine Lead Source
Select the appropriate Actor based on user needs:
User Need Actor ID Best For Local businesses compass/crawler-google-placesRestaurants, gyms, shops Contact enrichment vdrmota/contact-info-scraperEmails, phones from URLs Instagram profiles apify/instagram-profile-scraperInfluencer discovery Instagram posts/comments apify/instagram-scraperPosts, comments, hashtags, places Instagram search apify/instagram-search-scraperPlaces, users, hashtags discovery TikTok videos/hashtags clockworks/tiktok-scraperComprehensive TikTok data extraction
TikTok hashtags/profiles clockworks/free-tiktok-scraperFree TikTok data extractor
TikTok user search clockworks/tiktok-user-search-scraperFind users by keywords
TikTok profiles clockworks/tiktok-profile-scraperCreator outreach
TikTok followers/following clockworks/tiktok-followers-scraperAudience analysis, segmentation
Facebook pages apify/facebook-pages-scraperBusiness contacts
Facebook page contacts apify/facebook-page-contact-informationExtract emails, phones, addresses
Facebook groups apify/facebook-groups-scraperBuying intent signals
Facebook events apify/facebook-events-scraperEvent networking, partnerships
Google Search apify/google-search-scraperBroad lead discovery
YouTube channels streamers/youtube-scraperCreator partnerships
Google Maps emails poidata/google-maps-email-extractorDirect email extraction
Step 2: Fetch Actor Schema Fetch the Actor's input schema and details dynamically using mcpc:
export $(grep APIFY_TOKEN .env | xargs) && mcpc --json mcp.apify.com --header "Authorization: Bearer $APIFY_TOKEN" tools-call fetch-actor-details actor:="ACTOR_ID" | jq -r ".content"
Replace ACTOR_ID with the selected Actor (e.g., compass/crawler-google-places).
Actor description and README
Required and optional input parameters
Output fields (if available)
Step 3: Ask User Preferences
Output format :
Quick answer - Display top few results in chat (no file saved)
CSV - Full export with all fields
JSON - Full export in JSON format
Number of results : Based on character of use case
Step 4: Run the Script Quick answer (display in chat, no file):
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT'
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT' \
--output YYYY-MM-DD_OUTPUT_FILE.csv \
--format csv
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT' \
--output YYYY-MM-DD_OUTPUT_FILE.json \
--format json
Step 5: Summarize Results After completion, report:
Number of leads found
File location and name
Key fields available
Suggested next steps (filtering, enrichment)
Error Handling APIFY_TOKEN not found - Ask user to create .env with APIFY_TOKEN=your_token
mcpc not found - Ask user to install npm install -g @apify/mcpc
Actor not found - Check Actor ID spelling
Run FAILED - Ask user to check Apify console link in error output
Timeout - Reduce input size or increase --timeout
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.