Agent skill · software engineering · jeremylongshore
apify-ci-integration
Configure CI/CD pipelines for Apify Actor builds and deployments. Use when automating Actor deployment via GitHub Actions, running integration tests against the live Apify API, or building CI/CD for scrapers that push to the Apify platform. Trigger with "apify CI", "apify GitHub Actions", "apify automated deploy", "CI apify", "apify pipeline", "auto deploy actor".
Why this skill is useful
Adds specific CI/CD workflows and integration testing patterns for deploying Apify Actors that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, gh, jq installed locally. Requires apify account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apify CI Integration Overview Automate Apify Actor builds, tests, and deployments using GitHub Actions — test-on-PR, deploy-on-merge, live-API integration testing, and Docker build verification. Three workflow files do the work (test, deploy, verify-build); full copy-paste-ready definitions live in references/workflows.md. Prerequisites GitHub repository with Actions enabled Apify API token stored as a GitHub secret Actor code in the repository Authentication CI authenticates to Apify with a personal API token, never a hard-coded credential: Store the token as a GitHub Actions secret (gh secret set APIFYTOKEN), and expose it to a job only via env: APIFYTOKEN: ${{ secrets.APIFYTOKEN }}. The Apify CLI reads it as apify login --token $APIFYTOKEN; the REST API and apify-client read it from the APIFYTOKEN environment variable. Use separate APIFYTOKENTEST / APIFYTOKENPROD secrets so integration runs never touch production data. Get tokens from Apify Console → Settings → Integrations. Instructions Step 1: Configure GitHub Secrets Step 2: Create the test workflow Add .github/workflows/apify-test.yml with two jobs — unit-tests on every PR and integration-tests gated to push (merge) events. The integration job proves connectivity before running tests: Full two-job workflow: references/workflows.md (Test Workflow). Step 3: Create the deploy workflow Add .github/workflows/apify-deploy.yml — triggered on merges that touch src/, package.json, or .actor/ (plus workflowdispatch). It builds, tests, installs the Apify CLI, apify pushes, then runs a minimal smoke call to confirm the new build actually starts. Full definition: references/workflows.md (Deploy Workflow). Step 4: Write integration tests Gate live-API tests on the token so they skip cleanly when it is absent: The complete suite (auth, live Actor run, create/delete a named dataset with cleanup) is in references/integration-tests.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apify-ci-integration