PlugWiki

apify-actorization Skill for Claude: What It Does and How to Install It

Makes Claude convert an existing script or project into an Apify Actor: add the SDK, write the schemas and Dockerfile, test locally and deploy.

Installs
10.2K
on skills.sh
Stars
2.5K
on GitHub
Files
4
besides SKILL.md
Updated
Oct 2026
last repo commit

This is Apify's own guide for turning an existing project into an Actor, which is a program packaged as a Docker image that takes JSON input and can produce JSON output. Claude analyses the project, runs apify init, adds a Dockerfile, wraps the code with the SDK for JavaScript/TypeScript or Python, or a shell wrapper for other languages.

It then sets the input and output schemas, writes a README for Apify Store, tests with apify run and deploys with apify push. It uses your Apify login and can upload code to your Apify account, so read the safety notes.

Good for

  • Developers moving a scraper or script onto Apify
  • Teams wrapping a CLI tool as an Actor
  • Crawlee users migrating to the Apify platform

Install apify-actorization

Claude Code

  1. 1

    Copy this prompt.

    Install the apify-actorization skill in Claude Code. Run this command:
    
    /plugin marketplace add https://github.com/apify/agent-skills
    /plugin install apify-actorization@apify-agent-skills
    /plugin install apify-actor-development@apify-agent-skills
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. Each plugin's source in the marketplace file is its own skill folder. Step 7 of SKILL.md points to a README guide inside the apify-actor-development skill, so the routes here install both skills. The skill needs the Apify CLI and an Apify account, so the box has no Claude app upload. The README says Codex users can clone the repo.

From the project README. Source.

What's in the skill

When it loads

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.

Sections in SKILL.md

  1. Quick start
  2. When to use this skill
  3. Prerequisites
  4. Telemetry attribution (required)
  5. Actorization checklist
  6. Step 1: Analyze the project
  7. Step 2: Initialize Actor structure
  8. Step 3: Apply language-specific changes
  9. Quick reference
  10. Steps 4-6: Configure schemas
  11. Step 7: Write README
  12. Step 8: Test locally
  13. Step 9: Deploy
  14. Monetization (optional)
  15. Security
  16. Pre-deployment checklist

Key facts

Installs on skills.sh
10,151 (Nov 2, 2026)
Last repo commit
Oct 30, 2026

What it includes

  • Checks the apify CLI and login (apify info)

    Installs apify-cli with npm or Homebrew if missing. SKILL.md says never to install it by piping a remote script to a shell.

    Try: “Convert this Python script into an Apify Actor.”

    Runs code · Prerequisites

  • --user-agent on every apify command

    SKILL.md says the flag only tags calls for telemetry attribution and changes nothing else.

    Runs code · Telemetry attribution

  • Language, entry point, inputs, outputs, state

    Reads your project before changing anything.

    Read · Step 1: Analyze the project

  • apify init <actor-name> plus a Dockerfile

    Creates .actor/actor.json and storage/. It does not create a Dockerfile, so Claude adds one that matches the language.

    Runs code · Step 2: Initialize the Actor

  • JS/TS Actor.init/exit, Python async with Actor, CLI wrapper

    Each language has its own reference file. The Python route installs the apify package and the JS route runs npm install apify.

    Write · Step 3: Language changes

  • input_schema.json, output_schema.json, actor.json

    Validated against the @apify/json_schemas package, per schemas-and-output.md.

    Write · Steps 4 to 6: Schemas

  • Store landing page, at least 300 words

    Points to a README guide in the apify-actor-development skill.

    Write · Step 7: Write the README

  • apify run with inline input or an input file

    SKILL.md says to always use apify run, not npm start or python main.py.

    Runs code · Step 8: Test locally

  • apify push

    Uploads and builds the Actor on the Apify platform.

    Runs code · Step 9: Deploy

  • Pay Per Event, rental or free

    Describes charging with Actor.charge and setting a model in Apify Console.

    Read · Monetization

  • Untrusted crawled data, dependencies, 14-item checklist

    Rules include pinning versions, committing lockfiles and keeping APIFY_TOKEN away from data code.

    Read · Security and pre-deployment checklist

From the official docs

Permissions

Medium risk

Claude runs the Apify CLI with your sign-in, installs packages and can upload your project to your Apify account. Check what will be uploaded before you approve the push.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • apify push uploads your code

    Step 9 runs apify push, which uploads and builds the Actor on the Apify platform under your account. Check the project contents first, and keep secrets out of the folder. github.com

  • It uses your Apify login or token

    apify login stores credentials in ~/.apify, and APIFY_TOKEN can be exported instead. SKILL.md says to avoid passing tokens as command arguments and to use a scoped token. github.com

  • It installs the CLI and packages

    SKILL.md installs apify-cli with a package manager and adds npm or pip packages. It tells Claude to verify package names and pin versions. github.com

  • The CLI-wrapper example runs a downloaded script

    references/cli-actorization.md has an example Dockerfile that downloads and runs a bootstrap script from GitHub during the image build. Review it before you build. github.com

  • Every apify command carries a telemetry flag

    SKILL.md requires --user-agent apify-agent-skills/apify-actorization on every apify command and says it only tags the call for telemetry attribution. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlyNo read-only mode. Use version control.
Talks toApify platform and console (console.apify.com) through the apify CLI. mcp.apify.com for the optional docs MCP server. npm and PyPI package downloads. raw.githubusercontent.com in the CLI-wrapper example Dockerfile
Sign-in and keysapify login stores credentials in ~/.apify, and APIFY_TOKEN can be set in the environment. SKILL.md says never to log, print or embed the token.
Scopes
  • Claude can run apify init, run, push, login and info

  • Claude can install apify-cli with npm or Homebrew, and the apify package with npm or pip

  • apify push uploads and builds the Actor on the Apify platform

  • SKILL.md mentions an optional Playwright MCP server added with claude mcp add

Questions

What does the apify-actorization skill do?

It makes Claude turn an existing project into an Apify Actor. Claude adds the Apify SDK or a CLI wrapper, a Dockerfile and schemas, tests it locally and can deploy it to your Apify account.

How do I install apify-actorization?

Use the install box at the top of this page. It installs this skill together with apify-actor-development, which SKILL.md points to for the Actor README guide.

Is this skill from Apify?

Yes. It is in Apify's own repo, apify/agent-skills, which the marketplace file calls the official Apify Agent Skills.

Do I need an Apify account and API token?

You need an Apify account and a signed-in CLI. SKILL.md says to sign in with apify login, which opens a browser, or to export APIFY_TOKEN in headless or CI use.

Who pays for running it?

You, through your own Apify account. The README says a free tier is available and free tier credits come with every account, and that Actors use pay-per-result or pay-per-event pricing set by each Actor. SKILL.md's deploy step builds the Actor on your account, so check the usage and pricing pages on Apify before you push.

Which languages does it support?

JavaScript and TypeScript with the Apify SDK, Python with the Apify SDK, and any other language through a shell wrapper that uses the Apify CLI.

Does it work in the Claude app?

The install box has no Claude app upload for it, because the skill runs the Apify CLI, npm or pip and Docker-based tooling on your computer. Use Claude Code or another coding agent.

Is it safe?

It runs the Apify CLI with your login, installs packages and can upload your code to your Apify account with apify push. SKILL.md tells Claude to keep tokens out of command arguments, source and logs, and to treat crawled data as untrusted. Review each command before you approve it.

Information

updated Nov 2, 2026

Folder
skills/apify-actorization

apify/agent-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4
  1. apify-actorization SKILL.md · github.com
  2. apify/agent-skills README · github.com
  3. marketplace.json · github.com
  4. cli-actorization.md · github.com

Updated Nov 2, 2026.