domains / families / devops / apify-actor-development

apify-actor-development

combined

Create, modify, debug, and deploy Apify Actors, and write their input and output schemas. Use when building an Actor from scratch, changing or troubleshooting Actor code, generating or updating .actor schema files, or pushing an Actor to the Apify platform. To wrap an existing non-Actor project, use apify-actorization instead. Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as \"Claude Code with Claude Sonnet 4.5\". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.

When to use

When not to use

Skill page

Conflict

The apify/agent-skills copy is the more complete, structured procedure (template matrix, schema validation, local storage testing, standby mode, and a mandatory telemetry user-agent flag). The sickn33 copy adds material constraints the first lacks: explicit security guidance for untrusted crawled content, a prohibition on piping remote scripts into a shell, and a requirement to ask the user for their language preference before creating the project. The copies also disagree on template selection (detailed matrix vs. asking the user and using generic empty templates) and on the telemetry flag (required vs. absent). Crowning one would hide the security constraints and the alternative template-selection approach.