Awesome-omni-skills apify-ultimate-scraper

Universal Web Scraper workflow skill. Use this skill when the user needs AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/apify-ultimate-scraper" ~/.claude/skills/diegosouzapw-awesome-omni-skills-apify-ultimate-scraper && rm -rf "$T"

manifest: skills/apify-ultimate-scraper/SKILL.md

Universal Web Scraper

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/apify-ultimate-scraper

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

Universal Web Scraper AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Error Handling, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

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.
Use when the request clearly matches the imported source intent: AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`reference/scripts/run_actor.js`	Starts with the smallest copied file that materially changes execution
Supporting context	`reference/scripts/run_actor.js`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

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
Actor ID - Best For
apify/instagram-profile-scraper - Profile data, follower counts, bio info

Imported Workflow Notes

Imported: 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
`apify/instagram-profile-scraper`	Profile data, follower counts, bio info
`apify/instagram-post-scraper`	Individual post details, engagement metrics
`apify/instagram-comment-scraper`	Comment extraction, sentiment analysis
`apify/instagram-hashtag-scraper`	Hashtag content, trending topics
`apify/instagram-hashtag-stats`	Hashtag performance metrics
`apify/instagram-reel-scraper`	Reels content and metrics
`apify/instagram-search-scraper`	Search users, places, hashtags
`apify/instagram-tagged-scraper`	Posts tagged with specific accounts
`apify/instagram-followers-count-scraper`	Follower count tracking
`apify/instagram-scraper`	Comprehensive Instagram data
`apify/instagram-api-scraper`	API-based Instagram access
`apify/export-instagram-comments-posts`	Bulk comment/post export

Facebook Actors (14)

Actor ID	Best For
`apify/facebook-pages-scraper`	Page data, metrics, contact info
`apify/facebook-page-contact-information`	Emails, phones, addresses from pages
`apify/facebook-posts-scraper`	Post content and engagement
`apify/facebook-comments-scraper`	Comment extraction
`apify/facebook-likes-scraper`	Reaction analysis
`apify/facebook-reviews-scraper`	Page reviews
`apify/facebook-groups-scraper`	Group content and members
`apify/facebook-events-scraper`	Event data
`apify/facebook-ads-scraper`	Ad creative and targeting
`apify/facebook-search-scraper`	Search results
`apify/facebook-reels-scraper`	Reels content
`apify/facebook-photos-scraper`	Photo extraction
`apify/facebook-marketplace-scraper`	Marketplace listings
`apify/facebook-followers-following-scraper`	Follower/following lists

TikTok Actors (14)

Actor ID	Best For
`clockworks/tiktok-scraper`	Comprehensive TikTok data
`clockworks/free-tiktok-scraper`	Free TikTok extraction
`clockworks/tiktok-profile-scraper`	Profile data
`clockworks/tiktok-video-scraper`	Video details and metrics
`clockworks/tiktok-comments-scraper`	Comment extraction
`clockworks/tiktok-followers-scraper`	Follower lists
`clockworks/tiktok-user-search-scraper`	Find users by keywords
`clockworks/tiktok-hashtag-scraper`	Hashtag content
`clockworks/tiktok-sound-scraper`	Trending sounds
`clockworks/tiktok-ads-scraper`	Ad content
`clockworks/tiktok-discover-scraper`	Discover page content
`clockworks/tiktok-explore-scraper`	Explore content
`clockworks/tiktok-trends-scraper`	Trending content
`clockworks/tiktok-live-scraper`	Live stream data

YouTube Actors (5)

Actor ID	Best For
`streamers/youtube-scraper`	Video data and metrics
`streamers/youtube-channel-scraper`	Channel information
`streamers/youtube-comments-scraper`	Comment extraction
`streamers/youtube-shorts-scraper`	Shorts content
`streamers/youtube-video-scraper-by-hashtag`	Videos by hashtag

Google Maps Actors (4)

Actor ID	Best For
`compass/crawler-google-places`	Business listings, ratings, contact info
`compass/google-maps-extractor`	Detailed business data
`compass/Google-Maps-Reviews-Scraper`	Review extraction
`poidata/google-maps-email-extractor`	Email discovery from listings

Other Actors (6)

Actor ID	Best For
`apify/google-search-scraper`	Google search results
`apify/google-trends-scraper`	Google Trends data
`voyager/booking-scraper`	Booking.com hotel data
`voyager/booking-reviews-scraper`	Booking.com reviews
`maxcopell/tripadvisor-reviews`	TripAdvisor reviews
`vdrmota/contact-info-scraper`	Contact enrichment from URLs

Actor Selection by Use Case

Use Case	Primary Actors
Lead Generation	`compass/crawler-google-places` , `poidata/google-maps-email-extractor` , `vdrmota/contact-info-scraper`
Influencer Discovery	`apify/instagram-profile-scraper` , `clockworks/tiktok-profile-scraper` , `streamers/youtube-channel-scraper`
Brand Monitoring	`apify/instagram-tagged-scraper` , `apify/instagram-hashtag-scraper` , `compass/Google-Maps-Reviews-Scraper`
Competitor Analysis	`apify/facebook-pages-scraper` , `apify/facebook-ads-scraper` , `apify/instagram-profile-scraper`
Content Analytics	`apify/instagram-post-scraper` , `clockworks/tiktok-scraper` , `streamers/youtube-scraper`
Trend Research	`apify/google-trends-scraper` , `clockworks/tiktok-trends-scraper` , `apify/instagram-hashtag-stats`
Review Analysis	`compass/Google-Maps-Reviews-Scraper` , `voyager/booking-reviews-scraper` , `maxcopell/tripadvisor-reviews`
Audience Analysis	`apify/instagram-followers-count-scraper` , `clockworks/tiktok-followers-scraper` , `apify/facebook-followers-following-scraper`

Multi-Actor Workflows

For complex tasks, chain multiple Actors:

Workflow	Step 1	Step 2
Lead enrichment	`compass/crawler-google-places` →	`vdrmota/contact-info-scraper`
Influencer vetting	`apify/instagram-profile-scraper` →	`apify/instagram-comment-scraper`
Competitor deep-dive	`apify/facebook-pages-scraper` →	`apify/facebook-posts-scraper`
Local business analysis	`compass/crawler-google-places` →	`compass/Google-Maps-Reviews-Scraper`

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 `vdrmota/contact-info-scraper` 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

Imported: 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
```

Examples

Example 1: Ask for the upstream workflow directly

Use @apify-ultimate-scraper to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @apify-ultimate-scraper against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @apify-ultimate-scraper for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @apify-ultimate-scraper using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/apify-ultimate-scraper

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@00-andruia-consultant
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@10-andruia-skill-smith
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@20-andruia-niche-intelligence
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@3d-web-experience
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

scripts/run_actor.js

Imported Reference Notes

Imported: 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

Imported: 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.