Repository inventory

apify/agent-skills

Skills indexed from this repository, with install-style signals scoped to the repo.
6 skills384 GitHub stars0 weekly installsJavaScriptGitHubOwner profile

Overview

This skill converts existing projects into Apify Actors—serverless, Docker-packaged programs that accept JSON input and produce structured JSON output. It helps you add Apify SDK lifecycle integration to JavaScript/TypeScript and Python projects, or wrap any CLI tool as an Actor for deployment on the Apify platform. Use it to migrate existing code to a reusable, cloud-run Actor with standardized input/output and optional monetization.

How this skill works

The skill initializes the Actor scaffold via the apify CLI, injects language-specific lifecycle hooks (Actor.init()/Actor.exit() for JS/TS, async context manager for Python), and creates .actor metadata and JSON schemas. It guides you to map your project’s entry point, inputs, and outputs, validate input/output schemas, test locally with apify run, and deploy with apify push. For non-supported languages it suggests a CLI wrapper that uses apify CLI commands to read input and push results.

When to use it

  • Migrating a local project to run on Apify platform
  • Adding Apify SDK lifecycle to JS/TS or Python code
  • Wrapping a CLI tool or script as an Apify Actor
  • Standardizing input/output for automated, repeatable runs
  • Preparing a project for deployment and optional monetization

Best practices

  • Run apify init in the project root to create .actor configuration
  • Identify clear input and output contracts and define input_schema.json/output_schema.json
  • Wrap main code with the proper SDK lifecycle for your language
  • Always test with apify run (use --input or --input-file) to emulate Actor environment
  • Validate schemas using @apify/json_schemas before deploy
  • Ensure Dockerfile builds and actor.json metadata (generatedBy, name, description) are correct

Example use cases

  • Convert a web scraper to an Apify Actor that accepts startUrl and returns structured items
  • Wrap a CLI crawler so it reads input via apify actor:get-input and pushes results with apify actor:push-data
  • Migrate a Crawlee project by replacing its runner with Actor.init()/Actor.exit() and adding schemas
  • Publish a data-extraction tool to the Apify Store with PPE monetization events
  • Create a Python async Actor that manages lifecycle with async with Actor

FAQ

Yes. apify init, apify run, and apify push rely on the apify CLI. Install and authenticate the CLI before actorizing.

How do I test my Actor locally?

Use apify run with --input '{...}' or --input-file to run the Actor in a local environment that emulates Apify storage and lifecycle.

6 skills

More from this maintainer
Other repositories and skills published under the same GitHub owner.
Skills library
Jump back to the full directory or explore grouped topics.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational