From apify-scraper
Apify web scraping platform integration — run Actors, scrape websites, manage datasets, key-value stores, schedules, and webhooks. Use this skill whenever the user asks to: scrape a website, run an Apify Actor, get scraping results, check Actor runs, manage datasets, work with key-value stores, create schedules, set up webhooks, or anything related to Apify and web scraping. Also trigger on: "scrape", "crawl", "extract data from website", "Apify", "Actor", "dataset", "run scraper", "schedule scraping", "webhook", "web automation", "data extraction".
npx claudepluginhub msapps-mobile/claude-plugins --plugin apify-scraperThis skill uses the workspace's default tool permissions.
You have full access to the Apify platform through 27 MCP tools. Use this guide to pick the right workflow.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You have full access to the Apify platform through 27 MCP tools. Use this guide to pick the right workflow.
For fast, one-off scrapes where you need results immediately:
1. apify_run_actor_sync → pass actor_id + input, get dataset items back directly
Best for: small jobs that finish in under 5 minutes. Timeout is 300s.
For bigger jobs that may take longer:
1. apify_run_actor → start the run (returns run ID + dataset ID)
2. apify_get_run → poll status until SUCCEEDED
3. apify_get_dataset_items → retrieve results using defaultDatasetId
If you don't know which Actor to use:
1. apify_list_actors (my=false) → browse available Actors
2. apify_get_actor → check details, input schema, example input
3. Then run it with apify_run_actor or apify_run_actor_sync
Popular Actors to know:
apify/web-scraper — General-purpose web scraperapify/cheerio-scraper — Fast HTML scraper (no browser)apify/puppeteer-scraper — Browser-based scraper for JS-heavy sitesapify/playwright-scraper — Modern browser scraperapify/instagram-scraper, apify/twitter-scraper, apify/google-search-scraper — Social/search1. apify_get_run → check status + error message
2. apify_get_run_log → read console output for details
3. apify_resurrect_run → retry from where it stopped (if applicable)
1. apify_create_schedule → set cron expression + Actor ID
2. apify_list_schedules → verify it's active
1. apify_create_webhook → specify URL + event types (e.g. ACTOR.RUN.SUCCEEDED)
2. apify_list_webhooks → verify configuration
Tasks are pre-configured Actor runs with saved inputs:
1. apify_list_tasks → see available tasks
2. apify_run_task → run with optional input override
| Tool | Purpose |
|---|---|
apify_list_actors | Browse your Actors or public store |
apify_get_actor | Get Actor details, input schema, versions |
apify_run_actor | Start async Actor run |
apify_run_actor_sync | Run Actor and wait for results (max 300s) |
apify_build_actor | Trigger a new Actor build |
| Tool | Purpose |
|---|---|
apify_list_runs | List runs for an Actor (filter by status) |
apify_get_run | Get full run details + resource usage |
apify_get_last_run | Get most recent run of an Actor |
apify_abort_run | Stop a running Actor |
apify_resurrect_run | Continue a finished run |
apify_get_run_log | Read console log output |
| Tool | Purpose |
|---|---|
apify_list_datasets | List all datasets |
apify_get_dataset | Get dataset metadata |
apify_get_dataset_items | Retrieve items (main way to get results) |
apify_push_dataset_items | Add items to a dataset |
| Tool | Purpose |
|---|---|
apify_list_key_value_stores | List all KV stores |
apify_list_keys | List keys in a store |
apify_get_record | Get a record (OUTPUT, INPUT, etc.) |
apify_set_record | Create/update a record |
apify_delete_record | Delete a record |
| Tool | Purpose |
|---|---|
apify_list_schedules | List all schedules |
apify_create_schedule | Create cron-based schedule |
apify_delete_schedule | Remove a schedule |
apify_list_webhooks | List all webhooks |
apify_create_webhook | Create event webhook |
| Tool | Purpose |
|---|---|
apify_list_tasks | List saved Actor tasks |
apify_run_task | Run a saved task |
apify_run_actor_sync for quick scrapes — it returns results directly.apify_run_actor and poll with apify_get_run.defaultDatasetId from a run response is your key to getting results via apify_get_dataset_items.fields and omit params in apify_get_dataset_items to control output size.OUTPUT contains the Actor's main result; INPUT has what was passed in.0 8 * * * = daily at 8am.