SkillAgentSearch skills...

apollo-ci-integration

'Configure Apollo.io CI/CD integration.

Install / Use

npx skills add jeremylongshore/tons-of-skills-marketplace --skill apollo-ci-integration

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Automation

Supported Platforms

Claude Code

Our assessment of apollo-ci-integration

apollo-ci-integration scores 86/100 on our quality scale, 1469th of 2,746 Automation skills we index.

Its SKILL.md is 7.3 KB long, well organised into 16 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

With 2,785 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
8/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 7 days ago, so apollo-ci-integration is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

apollo-ci-integration compared with similar skills

All 4 of these similar skills score higher than apollo-ci-integration; compare them before choosing.

SkillScoreStarsUpdatedFormat
apollo-ci-integration (this skill)by jeremylongshore862.8k7d agoSKILL.md
Agent-Reachby Panniantong10086.9k15d agoCLAUDE.md
rufloby ruvnet10073.6ktodayCLAUDE.md
Scraplingby D4Vinci10084.9ktodayMCP Server
algorithmic-artby anthropics100177.9k8d agoSKILL.md

Frequently asked questions

How do I install apollo-ci-integration?
Run npx skills add jeremylongshore/tons-of-skills-marketplace --skill apollo-ci-integration. The install tabs above show the steps for each supported agent.
Which AI agents does apollo-ci-integration work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is apollo-ci-integration safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is apollo-ci-integration still maintained?
The repository was last updated 7 days ago, so apollo-ci-integration is actively maintained.

name: apollo-ci-integration description: 'Configure Apollo.io CI/CD integration.

Use when setting up automated testing, continuous integration,

or deployment pipelines for Apollo integrations.

Trigger with phrases like "apollo ci", "apollo github actions",

"apollo pipeline", "apollo ci/cd", "apollo automated tests".

' allowed-tools: Read, Write, Edit, Bash(gh:), Bash(curl:) version: 1.13.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:

  • saas
  • apollo
  • deployment
  • testing
  • ci-cd compatibility: Designed for Claude Code

Apollo CI Integration

Overview

Set up CI/CD pipelines for Apollo.io integrations with GitHub Actions. Uses MSW mocks for unit tests (zero API calls), sandbox tokens for staging, and live API tests gated to main branch only. Apollo's sandbox token returns dummy data without consuming credits.

Prerequisites

  • GitHub repository with Actions enabled
  • Apollo master API key + sandbox token
  • Node.js 18+

Instructions

Step 1: Store Secrets in GitHub

# Master API key for integration tests (main branch only)
gh secret set APOLLO_API_KEY --body "$APOLLO_API_KEY"

# Sandbox token for staging tests (safe, no credits)
gh secret set APOLLO_SANDBOX_KEY --body "$APOLLO_SANDBOX_KEY"

Step 2: GitHub Actions Workflow

# .github/workflows/apollo-ci.yml
name: Apollo CI
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  lint-and-typecheck:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: '20', cache: 'npm' }
      - run: npm ci
      - run: npm run lint
      - run: npm run typecheck

  unit-tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: '20', cache: 'npm' }
      - run: npm ci
      - run: npm test
        # Unit tests use MSW mocks — zero API calls

  integration-tests:
    runs-on: ubuntu-latest
    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
    needs: [unit-tests]
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: '20', cache: 'npm' }
      - run: npm ci
      - name: Apollo Health Check
        env:
          APOLLO_API_KEY: ${{ secrets.APOLLO_API_KEY }}
        run: |
          STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
            -H "x-api-key: $APOLLO_API_KEY" \
            "https://api.apollo.io/api/v1/auth/health")
          echo "Apollo API: HTTP $STATUS"
          [ "$STATUS" = "200" ] || exit 1
      - run: npm run test:integration
        env:
          APOLLO_API_KEY: ${{ secrets.APOLLO_API_KEY }}

  secret-scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Check for hardcoded API keys
        run: |
          if grep -rn 'x-api-key.*[a-zA-Z0-9]\{20,\}' src/ --include='*.ts' --include='*.js'; then
            echo "Potential hardcoded API key found!"
            exit 1
          fi
          echo "No hardcoded secrets"

Step 3: MSW-Based Unit Tests

// src/__tests__/apollo.test.ts
import { describe, it, expect, beforeAll, afterAll, afterEach } from 'vitest';
import { setupServer } from 'msw/node';
import { http, HttpResponse } from 'msw';

const BASE = 'https://api.apollo.io/api/v1';
const mockServer = setupServer(
  http.post(`${BASE}/mixed_people/api_search`, () =>
    HttpResponse.json({
      people: [{ id: '1', name: 'Jane Doe', title: 'VP Sales' }],
      pagination: { page: 1, per_page: 25, total_entries: 1, total_pages: 1 },
    }),
  ),
  http.post(`${BASE}/people/match`, () =>
    HttpResponse.json({
      person: { id: '1', name: 'Jane Doe', email: 'jane@test.com', title: 'VP Sales' },
    }),
  ),
  http.get(`${BASE}/auth/health`, () =>
    HttpResponse.json({ is_logged_in: true }),
  ),
);

beforeAll(() => mockServer.listen());
afterEach(() => mockServer.resetHandlers());
afterAll(() => mockServer.close());

describe('People Search', () => {
  it('returns contacts from search', async () => {
    const { searchPeople } = await import('../workflows/lead-search');
    const result = await searchPeople({ domains: ['test.com'] });
    expect(result.people).toHaveLength(1);
    expect(result.people[0].name).toBe('Jane Doe');
  });

  it('handles 429 errors', async () => {
    mockServer.use(
      http.post(`${BASE}/mixed_people/api_search`, () =>
        HttpResponse.json({ message: 'Rate limited' }, { status: 429 }),
      ),
    );
    const { searchPeople } = await import('../workflows/lead-search');
    await expect(searchPeople({ domains: ['test.com'] })).rejects.toThrow();
  });
});

Step 4: Integration Tests (Live API)

// src/__tests__/integration/apollo-live.test.ts
import { describe, it, expect } from 'vitest';
import axios from 'axios';

const SKIP = !process.env.APOLLO_API_KEY;
const client = axios.create({
  baseURL: 'https://api.apollo.io/api/v1',
  headers: { 'Content-Type': 'application/json', 'x-api-key': process.env.APOLLO_API_KEY! },
});

describe.skipIf(SKIP)('Apollo Live Integration', () => {
  it('searches for people at apollo.io', async () => {
    const { data } = await client.post('/mixed_people/api_search', {
      q_organization_domains_list: ['apollo.io'],
      per_page: 5,
    });
    expect(data.people.length).toBeGreaterThan(0);
  });

  it('enriches organization by domain', async () => {
    const { data } = await client.get('/organizations/enrich', { params: { domain: 'apollo.io' } });
    expect(data.organization).toBeDefined();
    expect(data.organization.name).toContain('Apollo');
  });
});

Output

  • GitHub Actions workflow with lint, typecheck, unit test, integration test, and secret scan jobs
  • MSW mock server for zero-API-call unit tests in PRs
  • Live integration tests gated to main branch pushes only
  • Apollo health check step before integration tests
  • Secret scanning to prevent API key commits

Examples

For a lead-search change, open a pull request with an MSW fixture that covers both a successful person search and a 429 response. The pull request runs lint, type checking, the mock-only tests, and the secret scan without exposing an Apollo credential or consuming credits. After merge, the protected main workflow performs the health check and the small live integration suite with the repository secret. If the health check is unavailable or the live request returns a non-success status, keep the change deployed only after the incident owner has either restored the provider path or explicitly disabled the live lane; do not broaden PR credentials to make the check pass.

Error Handling

| Issue | Resolution | |-------|------------| | Secret not found | gh secret list to verify, re-add with gh secret set | | Rate limited in CI | Unit tests use MSW, integration tests run only on main | | Health check fails | Check status.apollo.io; skip flaky on outage | | Hardcoded key found | Secret scan job fails the build; rotate the key immediately |

Resources

Next Steps

Proceed to apollo-deploy-integration for deployment configuration.

Related Skills

View on GitHub
GitHub Stars2.8k
CategoryAutomation
Updated7d ago
Forks404

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions