Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/apify-prod-checklist

@820dfc8
Run it yourself

Production readiness checklist for Apify Actor deployments. Use when deploying an Actor to production, preparing for launch, or validating Actor configuration, scheduling, monitoring, and rollback before going live. Trigger with "apify production", "deploy actor to prod", "apify go-live", "apify launch checklist", "actor production ready".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/apify-prod-checklist

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesexamples.md

≈476 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Apify Production Checklist — Worked Examples

Concrete examples of running the checklist against a real Actor, plus the console output each monitoring helper produces.

Example 1: First production deploy of a scraper

You have username/product-scraper passing locally. Run the checklist:

  1. Read .actor/actor.json and confirm name, title, description are set.
  2. Confirm Dockerfile pins apify/actor-node:20 (not latest).
  3. apify push, then apify builds ls to confirm the build succeeded.
  4. Smoke-test on-platform with a tiny input:
apify actors call username/product-scraper \
  --input='{"startUrls":[{"url":"https://target.com"}],"maxItems":10}'
  1. Create the daily schedule and completion webhook (see implementation.md Steps 2–3).

Example 2: Health check output

Running checkActorHealth('username/product-scraper', 24) prints:

Actor: username/product-scraper
Last 24h: 3 runs, 66.7% success
Failed: 1, Timed out: 0
Total cost: $0.4213
ALERT: Failed runs detected!

A success rate below 100% with ALERT: present is your cue to open the failed run's log in Apify Console and cross-reference the Error Handling table in SKILL.md.

Example 3: Cost guard aborting a runaway run

Calling runWithCostGuard(actorId, input, 5.0) on a job that blows past budget:

Cost guard: $5.0018 exceeds $5. Aborting.

The run is aborted mid-flight, waitForFinish() returns the aborted run object, and the poller is cleared — no orphaned interval.

Example 4: Rolling back a bad build

Build 42 shipped a regression. Roll back to build 41 without redeploying code:

apify builds ls
curl -X POST \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  "https://api.apify.com/v2/acts/username~product-scraper?build=41"

The Actor's default build pointer moves back to 41; the next scheduled run uses it.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a production readiness checklist and implementation guide for deploying Apify Actors. It utilizes the official Apify CLI and client library to manage builds, schedules, and monitoring tasks, following security best practices such as environment-based credential management.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 months ago
What it can do
Reads files Runs commands
version
1.5.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "scraping",
  "automation",
  "apify"
]
All 4 allowed tools
ReadBash(apify:*)Bash(curl:*)Bash(npm:*)
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/apify-prod-checklist