SkillAgentSearch skills...

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.

Install / Use

npx skills add sickn33/agentic-awesome-skills --skill apify-actorization

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

98/100

Category

Operations

Supported Platforms

Universal

Our assessment of apify-actorization

apify-actorization scores 98/100 on our quality scale, 10th of 745 Operations skills we index (top 2%).

Its SKILL.md is 6.7 KB long, well organised into 19 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

With 49,671 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so apify-actorization is actively maintained.
  • Our last check on 2026-11-14 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

apify-actorization compared with similar skills

All 4 of these similar skills score higher than apify-actorization; compare them before choosing.

SkillScoreStarsUpdatedFormat
apify-actorization (this skill)by sickn339849.7k3d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install apify-actorization?
Run npx skills add sickn33/agentic-awesome-skills --skill apify-actorization. The install tabs above show the steps for each supported agent.
Which AI agents does apify-actorization work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is apify-actorization safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is apify-actorization still maintained?
The repository was last updated 3 days ago, so apify-actorization is actively maintained.

name: apify-actorization description: "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." risk: critical source: community date_added: "2026-09-04"

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/input_schema.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 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:

apify --help

If not installed:

brew install apify-cli

# Or: npm install -g apify-cli
# Or install from an official release package that your OS package manager verifies

Verify CLI is logged in:

apify info  # Should return your username

If not logged in, check if APIFY_TOKEN environment variable is defined. If not, ask the user to generate one at https://console.apify.com/settings/integrations, add it to their shell or secret manager without putting the literal token in command history, then run:

apify login

Actorization Checklist

Copy this checklist to track progress:

  • [ ] Step 1: Analyze project (language, entry point, inputs, outputs)
  • [ ] Step 2: Run apify init to create Actor structure
  • [ ] Step 3: Apply language-specific SDK integration
  • [ ] Step 4: Configure .actor/input_schema.json
  • [ ] Step 5: Configure .actor/output_schema.json (if applicable)
  • [ ] Step 6: Update .actor/actor.json metadata
  • [ ] Step 7: Test locally with apify run
  • [ ] Step 8: Deploy with apify push

Step 1: Analyze the Project

Before making changes, understand the project:

  1. Identify the language - JavaScript/TypeScript, Python, or other
  2. Find the entry point - The main file that starts execution
  3. Identify inputs - Command-line arguments, environment variables, config files
  4. Identify outputs - Files, console output, API responses
  5. Check for state - Does it need to persist data between runs?

Step 2: Initialize Actor Structure

Run in the project root:

apify init

This creates:

  • .actor/actor.json - Actor configuration and metadata
  • .actor/input_schema.json - Input definition for the Apify Console
  • Dockerfile (if not present) - Container image definition

Step 3: Apply Language-Specific Changes

Choose based on your project's language:

Quick Reference

| Language | Install | Wrap Code | |----------|---------|-----------| | JS/TS | npm install apify | await Actor.init() ... await Actor.exit() | | Python | pip install apify | async with Actor: | | Other | Use CLI in wrapper script | apify actor:get-input / apify actor:push-data |

Steps 4-6: Configure Schemas

See schemas-and-output.md for detailed configuration of:

  • Input schema (.actor/input_schema.json)
  • Output schema (.actor/output_schema.json)
  • Actor configuration (.actor/actor.json)
  • State management (request queues, key-value stores)

Validate schemas against @apify/json_schemas npm package.

Step 7: Test Locally

Run the actor with inline input (for JS/TS and Python actors):

apify run --input '{"startUrl": "https://example.com", "maxItems": 10}'

Or use an input file:

apify run --input-file ./test-input.json

Important: Always use apify run, not npm start or python main.py. The CLI sets up the proper environment and storage.

Step 8: Deploy

apify push

This uploads and builds your actor on the Apify platform.

Monetization (Optional)

After deploying, you can monetize your actor in the Apify Store. The recommended model is Pay Per Event (PPE):

  • Per result/item scraped
  • Per page processed
  • Per API call made

Configure PPE in the Apify Console under Actor > Monetization. Charge for events in your code with await Actor.charge('result').

Other options: Rental (monthly subscription) or Free (open source).

Pre-Deployment Checklist

  • [ ] .actor/actor.json exists with correct name and description
  • [ ] .actor/actor.json validates against @apify/json_schemas (actor.schema.json)
  • [ ] .actor/input_schema.json defines all required inputs
  • [ ] .actor/input_schema.json validates against @apify/json_schemas (input.schema.json)
  • [ ] .actor/output_schema.json defines output structure (if applicable)
  • [ ] .actor/output_schema.json validates against @apify/json_schemas (output.schema.json)
  • [ ] Dockerfile is present and builds successfully
  • [ ] Actor.init() / Actor.exit() wraps main code (JS/TS)
  • [ ] async with Actor: wraps main code (Python)
  • [ ] Inputs are read via Actor.getInput() / Actor.get_input()
  • [ ] Outputs use Actor.pushData() or key-value store
  • [ ] apify run executes successfully with test input
  • [ ] generatedBy is set in actor.json meta section

Apify MCP Tools

If MCP server is configured, use these tools for documentation:

  • search-apify-docs - Search documentation
  • fetch-apify-docs - Get full doc pages

Otherwise, the MCP Server url: https://mcp.apify.com/?tools=docs.

Resources

Limitations

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

Related Skills

View on GitHub
GitHub Stars49.7k
CategoryOperations
Updated3d ago
Forks7.2k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions