Antigravity-awesome-skills apify-ultimate-scraper
AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.
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-ultimate-scraper" ~/.claude/skills/sickn33-antigravity-awesome-skills-apify-ultimate-scraper-f63d31 && rm -rf "$T"
manifest:
plugins/antigravity-awesome-skills/skills/apify-ultimate-scraper/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
Universal Web Scraper
AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.
When to Use
- The user needs web data extraction but has not yet chosen a specific Apify Actor.
- You need a general-purpose Apify entry point that maps a broad scraping goal to the most suitable Actor.
- The task spans multiple platforms and benefits from one unified workflow for actor selection, execution, and summarization.
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: Understand user goal and select Actor - [ ] Step 2: Fetch Actor schema via mcpc - [ ] Step 3: Ask user preferences (format, filename) - [ ] Step 4: Run the scraper script - [ ] Step 5: Summarize results and offer follow-ups
Step 1: Understand User Goal and Select Actor
First, understand what the user wants to achieve. Then select the best Actor from the options below.
Instagram Actors (12)
| Actor ID | Best For |
|---|---|
| Profile data, follower counts, bio info |
| Individual post details, engagement metrics |
| Comment extraction, sentiment analysis |
| Hashtag content, trending topics |
| Hashtag performance metrics |
| Reels content and metrics |
| Search users, places, hashtags |
| Posts tagged with specific accounts |
| Follower count tracking |
| Comprehensive Instagram data |
| API-based Instagram access |
| Bulk comment/post export |
Facebook Actors (14)
| Actor ID | Best For |
|---|---|
| Page data, metrics, contact info |
| Emails, phones, addresses from pages |
| Post content and engagement |
| Comment extraction |
| Reaction analysis |
| Page reviews |
| Group content and members |
| Event data |
| Ad creative and targeting |
| Search results |
| Reels content |
| Photo extraction |
| Marketplace listings |
| Follower/following lists |
TikTok Actors (14)
| Actor ID | Best For |
|---|---|
| Comprehensive TikTok data |
| Free TikTok extraction |
| Profile data |
| Video details and metrics |
| Comment extraction |
| Follower lists |
| Find users by keywords |
| Hashtag content |
| Trending sounds |
| Ad content |
| Discover page content |
| Explore content |
| Trending content |
| Live stream data |
YouTube Actors (5)
| Actor ID | Best For |
|---|---|
| Video data and metrics |
| Channel information |
| Comment extraction |
| Shorts content |
| Videos by hashtag |
Google Maps Actors (4)
| Actor ID | Best For |
|---|---|
| Business listings, ratings, contact info |
| Detailed business data |
| Review extraction |
| Email discovery from listings |
Other Actors (6)
| Actor ID | Best For |
|---|---|
| Google search results |
| Google Trends data |
| Booking.com hotel data |
| Booking.com reviews |
| TripAdvisor reviews |
| Contact enrichment from URLs |
Actor Selection by Use Case
| Use Case | Primary Actors |
|---|---|
| Lead Generation | , , |
| Influencer Discovery | , , |
| Brand Monitoring | , , |
| Competitor Analysis | , , |
| Content Analytics | , , |
| Trend Research | , , |
| Review Analysis | , , |
| Audience Analysis | , , |
Multi-Actor Workflows
For complex tasks, chain multiple Actors:
| Workflow | Step 1 | Step 2 |
|---|---|---|
| Lead enrichment | → | |
| Influencer vetting | → | |
| Competitor deep-dive | → | |
| Local business analysis | → | |
Can't Find a Suitable Actor?
If none of the Actors above match the user's request, search the Apify Store directly:
export $(grep APIFY_TOKEN .env | xargs) && mcpc --json mcp.apify.com --header "Authorization: Bearer $APIFY_TOKEN" tools-call search-actors keywords:="SEARCH_KEYWORDS" limit:=10 offset:=0 category:="" | jq -r '.content[0].text'
Replace
SEARCH_KEYWORDS with 1-3 simple terms (e.g., "LinkedIn profiles", "Amazon products", "Twitter").
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 and Offer Follow-ups
After completion, report:
- Number of results found
- File location and name
- Key fields available
- Suggested follow-up workflows based on results:
| If User Got | Suggest Next |
|---|---|
| Business listings | Enrich with or get reviews |
| Influencer profiles | Analyze engagement with comment scrapers |
| Competitor pages | Deep-dive with post/ad scrapers |
| Trend data | Validate with platform-specific hashtag scrapers |
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.