Agent skill · software engineering · jeremylongshore
apify-core-workflow-a
Build a complete web scraping Actor with Crawlee and deploy to Apify.
Why this skill is useful
Adds specific commands and patterns for building and deploying web scrapers using Apify and Crawlee that the AI wouldn't reliably generate on its own.
What it needs
Requires apify, apify-cli, crawlee installed locally. Requires apify account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apify Core Workflow A — Build & Deploy a Scraper Overview End-to-end workflow: define input schema, build a Crawlee-based Actor, extract structured data, store results in datasets, test locally, and deploy to Apify platform. This is the primary money-path workflow for Apify. Prerequisites npm install apify crawlee in your project npm install -g apify-cli and apify login completed For programmatic retrieval (Step 6), an API token in APIFYTOKEN — read it from the environment (process.env.APIFYTOKEN), never hard-code it Familiarity with apify-sdk-patterns Instructions Step 1: Define Input Schema Create .actor/INPUTSCHEMA.json: Step 2: Build the Actor with Router Pattern Use a Crawlee router that splits handling by page type: the default handler enqueues product links + pagination from listing pages, and a PRODUCT-labeled handler extracts structured fields from detail pages. The entry point wires proxy config, concurrency, a failed-request handler, and a run summary into the key-value store. Skeleton: The full typed Actor — Product/ProductInput interfaces, proxy configuration, failedRequestHandler, and the SUMMARY key-value write — is in implementation.md, Step 2. Step 3: Configure Dockerfile Use the apify/actor-node:20 base with a two-stage build (compile TypeScript in a builder stage, ship only dist/ + production deps). Full Dockerfile: implementation.md, Step 3. Step 4: Test Locally Step 5: Deploy to Apify Platform Step 6: Retrieve Results Programmatically From any client, use the apify-client SDK to call the deployed Actor, list its dataset items, and download results (JSON/CSV). The token comes from process.env.APIFYTOKEN — never hard-code it. Full retrieval code: implementation.md, Step 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apify-core-workflow-a