Agent skill · software engineering · jeremylongshore
apify-core-workflow-b
Manage Apify datasets, key-value stores, and request queues programmatically, and orchestrate multi-Actor pipelines. Use when you need to read or write Apify datasets, export scraped data to CSV/JSON/XLSX, store config or binary artifacts in a key-value store, manage a resumable request queue, chain Actors into a scrape → transform → export pipeline, or monitor Actor run status and cost. Trigger with "apify dataset", "apify key-value store", "apify storage", "export apify data", "apify pipeline", "apify request queue".
Why this skill is useful
Adds specific commands and workflows for managing Apify datasets and pipelines that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. Requires apify account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apify Core Workflow B — Storage & Pipelines Overview Manage Apify's three storage types (datasets, key-value stores, request queues) and orchestrate multi-Actor pipelines using the apify-client JS SDK. Covers CRUD operations, data export, automatic pagination, and chaining Actors together (scrape → transform → export). This SKILL.md gives you the high-level workflow plus the essential first example for each storage type. Drill into the reference files for the complete, copy-ready code: Storage operations — full reference — every dataset, key-value store, and request queue operation with pagination, format export, and binary records. Pipelines & run monitoring — full reference — the multi-Actor pipeline function and Actor-run status/cost/abort monitoring. Prerequisites Node.js with apify-client installed (npm install apify-client). An Apify account token exported as APIFYTOKEN (see Authentication below). Familiarity with apify-core-workflow-a (Actor invocation and run lifecycle), since pipelines chain Actor runs and read their default storages. Authentication All operations authenticate with an Apify API token. Never hard-code it — read it from the environment and construct the client once: Generate a token at Apify Console → Settings → Integrations, then export it (export APIFYTOKEN=apifyapi...) or load it from your secrets manager. Storage Types at a Glance Storage Best For Analogy Retention --------- ---------- --------- ----------- Dataset Lists of similar items (products, pages) Append-only table 7 days (unnamed) Key-Value Store Config, screenshots, summaries, any file S3 bucket 7 days (unnamed) Request Queue URLs to crawl (managed by Crawlee) Job queue 7 days (unnamed) Named storages persist indefinitely. Unnamed (default run) storages expire after 7 days. Instructions Pick the storage type you need, use the skeleton below to get started, then open the linked reference for the full operation set. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apify-core-workflow-b