Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides the technical foundation for developing, debugging, and deploying Apify Actors. It assists automation builders in creating serverless programs for web scraping and data processing, while streamlining the creation of AI agent plugins and MCP bundles.
The skills focus on the lifecycle of Actor development, from writing core logic to automatically generating output schemas by analyzing source code.
WHO IT'S FOR
AI agent / automation builders
creating AI agent plugins and MCP bundles
Web scraping and automation engineers
developing serverless cloud programs for data processing
Backend / infrastructure engineers
migrating existing projects into serverless Actors
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: Adds the apify-agent-skills marketplace and installs all five documented skill plugins individually: apify-ultimate-scraper, apify-actor-development, apify-actorization, apify-generate-output-schema, and apify-integration-development. · Claude Code
Enter these slash commands in a Claude Code agent session, in order. The first command adds the marketplace; the remaining commands install its five skill plugins.
Installs: Using the documented Claude Code plugin compatibility, adds the apify-agent-skills marketplace and installs all five documented skill plugins individually. · Cursor, Windsurf
Before you start
Claude Code extension installed in Cursor or Windsurf
Enter these slash commands in the Cursor or Windsurf agent session, in order. This documented route requires the Claude Code extension. The first command adds the marketplace; the remaining commands install its five skill plugins.
Replace <SEARCH_QUERY> with the business or place query to search for.
Replace <LOCATION> with the target city, neighborhood, or area.
Apify CLI v1.5.0 or newer must be installed.
An authenticated Apify session or APIFY_TOKEN must be available.
Use the apify-ultimate-scraper skill in quick-answer mode to scrape the top 5 Google Maps results for <SEARCH_QUERY> in <LOCATION>. Return the result count and the most useful fields for each result in chat; do not start a larger pipeline or save a file unless I ask.
Inventory an Actor's outputs before generating schemas
Uses apify-generate-output-schema
Replace <ACTOR_PROJECT_PATH> with the path to an existing Actor project containing .actor/actor.json.
Provide access to the Actor source code and any existing schema or output-type files in that repository.
Use the apify-generate-output-schema skill to inspect the Actor under <ACTOR_PROJECT_PATH>. For this first pass, locate its .actor/actor.json, existing schema files, dataset writes, key-value-store writes, and output type definitions. Present the discovered fields, keys, types, and source locations before creating or changing any schema files.
Replace <PROJECT_PATH> with the existing project's root directory.
Replace <SAMPLE_INPUT_JSON> with a small representative JSON input for the project.
The apify CLI must be installed and available.
Use an authenticated Apify CLI session, or export APIFY_TOKEN when browser login is unavailable.
Use the apify-actorization skill on the existing project at <PROJECT_PATH>. Initialize it from the project root, wrap its current entry point with the appropriate SDK lifecycle, configure .actor/input_schema.json for <SAMPLE_INPUT_JSON>, and run a local test. Stop before deployment and summarize the files changed and the local test result.