apify-actorization

Convert JavaScript, TypeScript, Python, and CLI projects into Apify Actors.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/cryptopafi/nexusos-skills --skill apify-actorization-cryptopafi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apify-actorization
Source: https://github.com/cryptopafi/nexusos-skills/tree/main/apify-actorization
Command: npx skills add https://github.com/cryptopafi/nexusos-skills --skill apify-actorization-cryptopafi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers convert existing applications and scripts into Apify Actors so they can run as reproducible, Dockerized serverless programs on the Apify platform. It eliminates guesswork around lifecycle integration, input/output schema design, local testing, and deployment for JavaScript/TypeScript, Python, or CLI-based projects.

Core Features & Use Cases

  • Language-specific SDK integration: Guidance for wrapping Node.js (Actor.init/exit) and Python (async with Actor:) projects, and patterns for CLI-based wrappers for other languages.
  • Schema and deployment workflow: Instructions to create and validate .actor/input_schema.json, .actor/output_schema.json, and .actor/actor.json, test locally with apify run, and deploy with apify push.
  • Real-world example: Migrate a Crawlee scraper or wrap a command-line tool into a production-ready Actor that accepts JSON input and pushes structured results to datasets or key-value stores.

Quick Start

Initialize an Apify actor in your project, wrap the entrypoint with the appropriate Actor lifecycle calls for your language, create a .actor input_schema.json, test with apify run, and deploy with apify push.

Frequently Asked Questions about apify-actorization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert an existing Python project into an Apify Actor?

To convert a JavaScript project into an Apify Actor, wrap your entrypoint with Actor.init and Actor.exit lifecycle calls. You then define input schemas and deploy using the apify push command for serverless execution.

What is the process for containerizing a CLI tool with Docker for Apify?

Containerizing a CLI tool for Apify involves using a CLI-based wrapper pattern to define input and output schemas. You create a Dockerfile to containerize the application, test locally with apify run, and deploy with apify push.

How do I define input and output schemas for an Apify Actor?

Defining Apify Actor schemas involves creating and validating the .actor/input_schema.json and .actor/output_schema.json files. This ensures your Actor accepts structured JSON input and pushes reproducible results to datasets or key-value stores.

Can I test an Apify Actor locally before deploying it to the serverless platform?

Yes, you can test an Apify Actor locally before serverless deployment by running the apify run command. This validates the Actor lifecycle integration and schema definitions before you execute the final apify push deployment.

Does Apify actorization work with TypeScript and Node.js scrapers?

Apify actorization supports JavaScript and TypeScript projects by integrating Node.js SDK lifecycle calls. This allows you to migrate Crawlee scrapers into production-ready Actors that accept JSON input and output structured results.

What are the limitations when wrapping command-line applications into Apify Actors?

When wrapping command-line applications into Apify Actors, you must use CLI-based wrapper patterns since direct SDK integration is unavailable. This requires manual Dockerfile containerization and strict schema mapping for serverless execution.