Agent skill · software engineering · apify
apify-actorization
Convert existing projects into Apify Actors - serverless cloud programs. Actorize JavaScript/TypeScript (SDK with Actor.init/exit), Python (async context manager), or any language (CLI wrapper). Use when migrating code to Apify, wrapping CLI tools as Actors, or adding Actor SDK to existing projects.
Why this skill is useful
Provides specific commands and procedures for converting existing projects into Apify Actors, which the AI wouldn't reliably generate on its own.
What it needs
Requires apify-cli installed locally. Requires apify account access. About 6k tokens when loaded. Last updated 2026-08-04. 2,326 stars on the source repository.
What this skill does
Apify Actorization Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output. Quick start 1. Run apify init in project root 2. Wrap code with SDK lifecycle (see language-specific section below) 3. Configure .actor/inputschema.json 4. Test with apify run --input '{"key": "value"}' 5. Deploy with apify push When to use this skill Converting an existing project to run on the Apify platform Adding Apify SDK integration to a project Wrapping a CLI tool or script as an Actor Migrating a Crawlee project to Apify Prerequisites Verify apify CLI is installed: If not installed, use one of these methods (listed in order of preference): Security note: Do NOT install the CLI by piping remote scripts to a shell (e.g. curl ... bash or irm ... iex). Always use a package manager. Verify CLI is logged in: If not logged in, authenticate using OAuth (opens browser): If browser login isn't available (headless environment or CI), ensure the APIFYTOKEN environment variable is exported (note: the variable is APIFYTOKEN, not APIFYAPITOKEN). The CLI reads it automatically - no explicit login needed. If the user doesn't have a token, generate one at https://console.apify.com/settings/integrations. Apify platform environment: When the Actor runs on the Apify platform, APIFYTOKEN is auto-injected as an environment variable and the Apify SDK reads it automatically — you do not need to pass it explicitly. Locally, apify login stores credentials in ~/.apify and the SDK uses them. Security note: Avoid passing tokens as command-line arguments (e.g. apify login -t <token>). Arguments are visible in process listings and may be recorded in shell history. Prefer OAuth login or environment variables instead. Never log, print, or embed APIFYTOKEN in source code or configuration files. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills apify/apify-actorization