Agent skill · software engineering · jeremylongshore
apify-upgrade-migration
Upgrade Apify SDK, apify-client, and Crawlee versions safely. Use when migrating between SDK versions, handling breaking changes, or updating from Apify SDK v2 to v3 (Crawlee split). Trigger with "upgrade apify", "apify migration", "apify breaking changes", "update apify SDK", "crawlee upgrade", "apify v2 to v3".
Why this skill is useful
Adds specific upgrade procedures and code transformation patterns for migrating between Apify SDK versions that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apify Upgrade & Migration Overview Guide for upgrading apify, apify-client, and crawlee packages. The biggest migration in Apify's history was SDK v2 to v3, which split crawling functionality into the crawlee package. This skill covers that migration plus general upgrade procedures. Read and edit source files with Grep/Read/Edit to apply the rename-heavy changes, then verify with the packaged script. Prerequisites Before starting, confirm the working tree is in a recoverable state: A dedicated git branch for the upgrade, so a bad bump can be reverted cleanly. A runnable test suite (npm test) plus a build step (npm run build) to catch TypeScript interface changes. The current installed versions recorded (npm list apify apify-client crawlee) so rollback targets are known. APIFYTOKEN in the environment if the verification script's API-connection check will run. Instructions Step 1: Check Current Versions Step 2: Create Upgrade Branch Step 3: Upgrade Packages Step 4: Apply Code Changes If crossing the v2→v3 boundary, use Grep to find every Apify. reference and Edit each call site. The full before/after set — imports, Actor.main, crawler option renames (handlePageFunction → requestHandler), proxy config, request queues, and the new router pattern — is in the v2-to-v3 migration guide. Minimal shape: Step 5: Verify and Test Then run the packaged verification script from verify-and-rollback.md, which checks imports resolve, the client connects, and a crawler instantiates. Output A successful upgrade produces: Updated package.json / package-lock.json with the new apify, crawlee, and apify-client versions on the upgrade/apify-packages branch. Migrated source files with all Apify. call sites converted to Actor. / crawlee imports (only when crossing v2→v3). A passing verification run, e.g.: If any check fails, follow the rollback procedure to restore the previous versions before investigating. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apify-upgrade-migration