domains / families / devops / apify-actorization

apify-actorization

combined

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. 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.

When to use

• 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
• Converting an existing project to run on Apify platform

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies describe the same Apify Actorization workflow, but each contains material steps the other lacks. The apify/agent-skills copy adds a required telemetry attribution flag (--user-agent apify-agent-skills/apify-actorization) on every apify command, a README-writing step for the Apify Store listing, and explicit security guidance about avoiding piped installs and token exposure. The sickn33/agentic-awesome-skills copy adds a Monetization section (Pay Per Event, Rental, Free), a detailed Pre-Deployment Checklist, and Apify MCP tool usage. Because crowning one copy would hide these real alternatives, the decision is combine.