Antigravity-awesome-skills apify-lead-generation
Scrape leads from multiple platforms using Apify Actors.
install
source · Clone the upstream repo
git clone https://github.com/sickn33/antigravity-awesome-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sickn33/antigravity-awesome-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/antigravity-awesome-skills/skills/apify-lead-generation" ~/.claude/skills/sickn33-antigravity-awesome-skills-apify-lead-generation-f21e54 && rm -rf "$T"
manifest:
plugins/antigravity-awesome-skills/skills/apify-lead-generation/SKILL.mdsafety · automated scan (medium risk)
This is a pattern-based risk scan, not a security review. Our crawler flagged:
- global npm install
- dumps environment variables
- references .env files
Always read a skill's source content before installing. Patterns alone don't mean the skill is malicious — but they warrant attention.
source content
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)
file with.envAPIFY_TOKEN- Node.js 20.6+ (for native
support)--env-file
CLI tool:mcpcnpm 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 | | Restaurants, gyms, shops |
| Contact enrichment | | Emails, phones from URLs |
| Instagram profiles | | Influencer discovery |
| Instagram posts/comments | | Posts, comments, hashtags, places |
| Instagram search | | Places, users, hashtags discovery |
| TikTok videos/hashtags | | Comprehensive TikTok data extraction |
| TikTok hashtags/profiles | | Free TikTok data extractor |
| TikTok user search | | Find users by keywords |
| TikTok profiles | | Creator outreach |
| TikTok followers/following | | Audience analysis, segmentation |
| Facebook pages | | Business contacts |
| Facebook page contacts | | Extract emails, phones, addresses |
| Facebook groups | | Buying intent signals |
| Facebook events | | Event networking, partnerships |
| Google Search | | Broad lead discovery |
| YouTube channels | | Creator partnerships |
| Google Maps emails | | Direct 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).
This returns:
- Actor description and README
- Required and optional input parameters
- Output fields (if available)
Step 3: Ask User Preferences
Before running, ask:
- 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'
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.csv \ --format csv
JSON:
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.