New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Apify CI Integration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Configure CI/CD pipelines for Apify Actor builds and deployments.

MITAuto-check passedDevOps & Cloud

Install Apify CI Integration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-ci-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace apify-ci-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/apify-ci-integration .claude/skills/apify-ci-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
apify-ci-integration
GitHub stars
2.8k
Token cost
~1.7k tokens
SKILL.md length
588 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Configure CI/CD pipelines for Apify Actor builds and deployments.

  • Works in 5 steps: Configure GitHub Secrets → Create the test workflow → Create the deploy workflow → …
  • Automating Actor deployment via GitHub Actions
  • SKILL.md covers Overview, Prerequisites, Authentication and Instructions, plus 5 more sections
  • Calls gh, npm and docker; reaches api.apify.com; needs APIFY_TOKEN

What it does

Apify CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/integration-tests.md` and `references/workflows.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Web scraping, CI/CD and Deployment. It works with Apify, GitHub Actions and GitHub. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Automating Actor deployment via GitHub Actions
  • Running integration tests against the live Apify API
  • Building CI/CD for scrapers that push to the Apify platform
  • Apify GitHub Actions

Example prompts

  • “apify CI”
  • “apify GitHub Actions”
  • “apify automated deploy”
  • “/apify-ci-integration”

Requirements

  • Docker
  • A credential in APIFY_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Write, Bash(gh:*), Bash(npm:*)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Configure GitHub Secrets
  2. Create the test workflow
  3. Create the deploy workflow
  4. Write integration tests
  5. Verify the Actor build

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Write
    • Bash(gh:*)
    • Bash(npm:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • npm
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.apify.com

    Also links to:

    • docs.apify.com
    • docs.github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • APIFY_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Apify CI Integration loads about 1.7k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 588 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 588 words, ~1,682 tokens.

Download SKILL.mdSave it as .claude/skills/apify-ci-integration/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
apify-ci-integration
description
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".
allowed-tools
Write, Bash(gh:*), Bash(npm:*)
compatibility
Designed for Claude Code
version
1.5.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, scraping, automation, apify

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 APIFY_TOKEN), and expose it to a job only via env: APIFY_TOKEN: ${{ secrets.APIFY_TOKEN }}.
  • The Apify CLI reads it as apify login --token $APIFY_TOKEN; the REST API and apify-client read it from the APIFY_TOKEN environment variable.
  • Use separate APIFY_TOKEN_TEST / APIFY_TOKEN_PROD secrets so integration runs never touch production data. Get tokens from Apify Console → Settings → Integrations.

Instructions

Step 1: Configure GitHub Secrets
bash
# Store Apify token for CI
gh secret set APIFY_TOKEN --body "apify_api_YOUR_CI_TOKEN"

# Optional: separate tokens for test vs production
gh secret set APIFY_TOKEN_TEST --body "apify_api_test_token"
gh secret set APIFY_TOKEN_PROD --body "apify_api_prod_token"
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:

yaml
      - name: Verify Apify connection
        run: |
          curl -sf -H "Authorization: Bearer $APIFY_TOKEN" \
            https://api.apify.com/v2/users/me | jq '.data.username'

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 workflow_dispatch). 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:

typescript
const SKIP_INTEGRATION = !process.env.APIFY_TOKEN;

describe.skipIf(SKIP_INTEGRATION)('Apify Integration', () => {
  it('should authenticate successfully', async () => {
    const user = await client.user().get();
    expect(user.username).toBeTruthy();
  });
});

The complete suite (auth, live Actor run, create/delete a named dataset with cleanup) is in references/integration-tests.md.

Step 5: Verify the Actor build

Add a verify-build.yml that docker builds the Actor image and boots it once to confirm the entry point loads. Optionally add branch-protection rules that require the CI contexts before merge. Both blocks: references/workflows.md (Actor Build Verification).

Output

Applying this skill produces committed CI/CD infrastructure in the repository:

  • .github/workflows/apify-test.yml — unit tests on every PR, integration tests on merge to main.
  • .github/workflows/apify-deploy.yml — apify push + post-deploy smoke test on merge, plus manual workflow_dispatch.
  • .github/workflows/verify-build.yml — Docker build + entry-point check on PRs.
  • tests/integration/apify.test.ts — token-gated live-API integration suite.
  • Configured GitHub secrets (APIFY_TOKEN, optional _TEST / _PROD variants) and, optionally, branch-protection requiring the CI checks to pass.

Once merged, every PR runs unit tests, every merge deploys and smoke-tests the Actor, and a failed deploy surfaces a ::error:: annotation in the run log.

Show full SKILL.md (199 more words)Show less

Error Handling

IssueCauseSolution
APIFY_TOKEN not setSecret not configuredgh secret set APIFY_TOKEN
Integration test timeoutSlow Actor runIncrease timeout, use smaller input
Docker build fails in CILocal-only depsCommit package-lock.json
apify push failsNot logged inAdd apify login --token step
Flaky integration testsExternal service issuesAdd retries, use test.retry(2)

Examples

Minimal test-on-PR gate — the smallest useful setup is Step 1 (store the secret) plus the unit-tests job from the test workflow. Every PR then runs npm ci && npm run build && npm test before it can merge.

Full deploy pipeline — add the deploy workflow so a merge to main that touches src/** builds, tests, runs apify push, then smoke-tests the new build:

yaml
      - name: Push Actor to Apify
        run: apify push

      - name: Verify deployment
        run: |
          ACTOR_ID=$(jq -r '.name' .actor/actor.json)
          apify actors call $ACTOR_ID \
            --input='{"startUrls":[{"url":"https://example.com"}],"maxItems":1}' \
            --timeout=120

apify-client app (not Actor dev) — for an app that calls Actors rather than publishing one, mock apify-client in unit tests and gate a real-token integration job to main. Full workflow: references/workflows.md (CI Configuration for apify-client Apps).

See references/workflows.md for every full workflow and references/integration-tests.md for the complete integration suite.

Resources

Next Steps

For runtime deployment patterns beyond CI wiring — release channels, versioned Actor builds, and rollback — see the apify-deploy-integration skill in this pack.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/apify-ci-integration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/integration-tests.md
  • references/workflows.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Apify CI Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Apify CI Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Apify CI Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: PassMIT
Data Scraper Agentaffaan-m/ECC277k5 repos~6.3kAutomated safety check: NotesMIT
Data Scraper Agentaffaan-m/ECC276k1 repos~5.2kAutomated safety check: NotesMIT
Data Scraper Agentaffaan-m/ECC276k—~377Automated safety check: PassMIT
AI News RadarLearnPrompt/ai-news-radar1.8k—~2.5kAutomated safety check: NotesMIT
Use Vercel Actionamondnet/vercel-action764—~2.7kAutomated safety check: PassMIT

Similar skills

  • Data Scraper Agent

    affaan-m/ECC

    Build a fully automated AI-powered data collection agent for any public source — job boards, prices, news, GitHub, sports, anything.

    277k GitHub starsUsed in 5 repos~6.3k tokens
    DevOps & CloudAuto-check: notes

  • Data Scraper Agent

    affaan-m/ECC

    构建一个全自动化的AI驱动数据收集代理，适用于任何公共来源——招聘网站、价格信息、新闻、GitHub、体育赛事等任何内容。按计划进行抓取，使用免费LLM（Gemini Flash）丰富数据，将结果存储在Notion/Sheets/Supabase中，并从用户反馈中学习。完全免费在GitHub Actions上运行。适用于用户希望自动监控、收集或跟踪任何公共数据的场景。

    276k GitHub starsUsed in 1 repo~5.2k tokens
    DevOps & CloudAuto-check: notes

  • Data Scraper Agent

    affaan-m/ECC

    任意のパブリックソース（ジョブボード、価格、ニュース、GitHub、スポーツなど）用の完全自動化されたAI搭載データ収集エージェントを構築します。スケジュールでスクレイプし、無料LLM（Gemini Flash）でデータを豊かにし、Notion/Sheets/Supabaseに結果を保存し、ユーザーフィードバックから学習します。GitHub…

    276k GitHub stars~377 tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • AI News Radar

    LearnPrompt/ai-news-radar

    A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…

    1.8k GitHub stars~2.5k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Use Vercel Action

    amondnet/vercel-action

    Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.

    764 GitHub stars~2.7k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Prepare Cloudflare Production Deployment

    LubomirGeorgiev/cloudflare-workers-nextjs-saas-template

    Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.

    786 GitHub stars~5.9k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Apify CI Integration

What does Apify CI Integration do?

Configure CI/CD pipelines for Apify Actor builds and deployments. Apify CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure CI/CD pipelines for Apify Actor builds and deployments.

When should I use Apify CI Integration?

Apify CI Integration fits situations like: automating Actor deployment via GitHub Actions; running integration tests against the live Apify API; building CI/CD for scrapers that push to the Apify platform; apify GitHub Actions.

How do I install Apify CI Integration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-ci-integration -a claude-code`. Or copy the skill folder (skills/.curated/apify-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/apify-ci-integration in your project. Claude Code loads it when a task matches its description.

How do I install Apify CI Integration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-ci-integration -a codex`. Or copy the skill folder (skills/.curated/apify-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/apify-ci-integration in your project. Codex loads it when a task matches its description.

Can I use Apify CI Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill apify-ci-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/apify-ci-integration, .gemini/skills/apify-ci-integration, .github/skills/apify-ci-integration and .opencode/skills/apify-ci-integration in your project.

What does Apify CI Integration need to run?

Going by SKILL.md and its folder, Apify CI Integration needs the command-line tools its instructions call (gh, npm and docker) and credentials named APIFY_TOKEN. Our summary lists: Docker; A credential in APIFY_TOKEN. Its frontmatter pre-approves these tools: Write, Bash(gh:*), Bash(npm:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Apify CI Integration access the network?

SKILL.md names 3 domains. In commands or code: api.apify.com; the agent is likely to contact it when it follows the instructions. As links in the text: docs.apify.com and docs.github.com. This is read from the text; nothing was executed.

Is Apify CI Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Apify CI Integration use?

Apify CI Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Apify CI Integration use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Apify CI Integration?

Skills that share tags, products or a category with Apify CI Integration: Data Scraper Agent (affaan-m/ECC, 277k stars), Data Scraper Agent (affaan-m/ECC, 276k stars), Data Scraper Agent (affaan-m/ECC, 276k stars) and AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Apify CI Integration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.