apify-actor-development — Claude Code skill for building Apify Actors
A skill that walks an agent through building, debugging, and deploying Apify Actors. Covers project scaffolding, schemas, local runs, and pushes to the Apify platform.
npx skills add apify/agent-skills --skill apify-actor-development -a claude-codeWhat apify-actor-development does
The skill turns Apify Actor development into a nine-step workflow: create a project from a template, add dependencies, implement the code, write input and output schemas, configure .actor/actor.json, add a README, test locally with apify run, and deploy with apify push. Templates cover static HTML crawling, JavaScript-rendered pages, HTTP servers, MCP servers, and empty projects for anything else.
It picks the right crawler too: CheerioCrawler for static pages at 10–50 concurrency, PlaywrightCrawler for JS-heavy sites at 1–5. Dependencies get pinned and lockfiles committed, so builds stay reproducible.
Every apify command from this skill must carry --user-agent apify-agent-skills/apify-actor-development for telemetry attribution. The token goes through the APIFY_TOKEN environment variable only, never into shell history or config files. The skill text is truncated, so some rules are cut off.
What it helps with
- scaffold a new Apify Actor from the right template
- pin dependencies and keep the lockfile committed
- generate input and output schemas for the Actor
- run the Actor locally and inspect the dataset
- deploy the Actor to the Apify platform
Example prompts for the agent
- create an Apify Actor for static HTML crawling in TypeScript
- add an input schema with URL and crawl depth fields
- run it locally and check the dataset fields match the schema
How to install apify-actor-development
1Skills CLI (Vercel)
npx skills add apify/agent-skills --skill apify-actor-development -a claude-code2Manually: put the files in place
~/.claude/skills/apify-actor-development/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/apify-actor-development/
1Skills CLI (Vercel)
npx skills add apify/agent-skills --skill apify-actor-development -a codex2Manually: put the files in place
.agents/skills/apify-actor-development/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add apify/agent-skills --skill apify-actor-development -a cursor2Manually: put the files in place
.cursor/skills/apify-actor-development/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install apify/agent-skills apify-actor-development2Manually: put the files in place
.github/skills/apify-actor-development/SKILL.md1Skills CLI (Vercel)
npx skills add apify/agent-skills --skill apify-actor-development -a gemini-cli2Platform CLI
gemini skills install https://github.com/apify/agent-skills --path skills/apify-actor-developmentManually: put the files in place
.devin/skills/apify-actor-development/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add apify/agent-skills --skill apify-actor-development -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set2
The whole set →Similar
Questions about apify-actor-development
How do I install apify-actor-development in Claude Code?
Run npx skills add apify/agent-skills --skill apify-actor-development -a claude-code. The skill lands in ~/.claude/skills/apify-actor-development/SKILL.md.
What does apify-actor-development do?
It guides the agent through the full Apify Actor lifecycle: template selection, code, input and output schemas, local testing, and deployment. It also enforces logging through the Apify logger and safe token handling.
Why does every apify command need the --user-agent flag?
The flag --user-agent apify-agent-skills/apify-actor-development tags calls for telemetry attribution. It changes nothing about how commands behave, only lets Apify attribute the work to this skill.