apify-actorization

Convert existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/ValorInvestigator/claude-plugin-toolkit --skill apify-actorization-valorinvestigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apify-actorization
Source: https://github.com/ValorInvestigator/claude-plugin-toolkit/tree/main/skills/apify-actorization
Command: npx skills add https://github.com/ValorInvestigator/claude-plugin-toolkit --skill apify-actorization-valorinvestigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts existing applications or CLI tools into managed Apify Actors so teams can run them reliably on the Apify platform, accept structured JSON inputs, and produce predictable outputs without manually wiring SDK lifecycle concerns.

Core Features & Use Cases

  • Actorization checklist keeps the workflow organized from apify init through schema configuration, testing, and deployment while tracking security requirements.
  • Language-specific guidance explains how to wrap JavaScript/TypeScript with Actor.init/exit, embrace async with Actor in Python, or create CLI wrappers that call apify actor:get-input and push data back.
  • Use Case: Migrate a Crawlee project or CLI scraper to Apify by adding input/output schema files, validating against @apify/json_schemas, and securely managing APIFY_TOKEN before running apify run and apify push.

Quick Start

Initialize the actor structure with apify init, wrap your logic with the appropriate SDK lifecycle, validate input and output schemas, test with apify run, and deploy using 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 a CLI tool to an Apify Actor for serverless deployment?

To convert a CLI tool to an Apify Actor, create CLI wrappers that call apify actor:get-input, define a structured JSON input schema, validate it, test locally with apify run, then deploy using apify push.

What is the process to actorize a Python project for the Apify cloud?

Actorizing a Python project requires embracing async with the Actor SDK, defining structured JSON input and dataset output scenarios, validating schemas, and securely handling APIFY_TOKEN before pushing to the Apify cloud.

Do I need the Apify CLI and SDK to migrate a Crawlee project to Apify?

Yes, migrating a Crawlee project requires the Apify CLI to initialize the structure and the SDK to wrap Actor.init and Actor.exit lifecycle events, ensuring reliable serverless execution and predictable dataset outputs.

How do I structure JSON input schemas when making a JavaScript app serverless on Apify?

Structuring JSON input schemas for serverless Apify Actors involves defining the expected input format, validating it against @apify/json_schemas, and ensuring the JavaScript SDK lifecycle correctly processes the data before producing dataset outputs.

Why is schema validation and secure APIFY_TOKEN handling important for Apify Actors?

Schema validation ensures structured JSON inputs produce predictable outputs without manual SDK wiring, while secure APIFY_TOKEN handling protects credentials during local testing and the apify push deployment process to the Apify platform.