exa-ci-integration
Configure Exa CI/CD integration with GitHub Actions and automated testing. Use when setting up automated testing for Exa integrations, configuring CI pipelines, or adding Exa health checks to builds. Trigger with phrases like "exa CI", "exa GitHub Actions", "exa automated tests", "CI exa", "exa pipeline". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill exa-ci-integration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Exa CI Integration ## Overview Set up CI/CD pipelines for Exa integrations with unit tests (mocked), integration tests (real API), and health checks. Uses GitHub Actions with secrets for API key management. ## Prerequisites - GitHub repository with Actions enabled - Exa API key for testing - npm/pnpm project with vitest or jest ## Instructions ### Step 1: GitHub Actions Workflow ```yaml # .github/workflows/exa-tests.yml name: Exa Integration Tests on: push: branches: [main] pull_request: branches: [main] jobs: 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 run test:unit # Unit tests use mocked Exa — no API key needed integration-tests: runs-on: ubuntu-latest # Only run if API key is available (not on forks) if: github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository env: EXA_API_KEY: ${{ secrets.EXA_API_KEY }} steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: "20" cache: "npm" - run: npm ci - run: npm run test:integration timeout-minutes: 5 exa-health-check: runs-on: ubuntu-latest env: EXA_
- Overview
- Prerequisites
- Instructions
- Step 1: GitHub Actions Workflow
- Step 2: Configure Secrets
- Step 3: Integration Test Suite
- Step 4: Release Gate with Exa Verification
- Error Handling
- Resources
- Next Steps
Add API key as repository secret gh secret set EXA_API_KEY --body "your-exa-api-key" For staging/production deployments gh secret set EXA_API_KEY_STAGING --body "staging-key" --env staging gh secret set EXA_API_KEY_PROD --body "prod-key" --env production
What does the exa-ci-integration skill do?
Configure Exa CI/CD integration with GitHub Actions and automated testing. Use when setting up automated testing for Exa integrations, configuring CI pipelines, or adding Exa health checks to builds. Trigger with phrases like "exa CI", "exa GitHub Actions", "exa automated tests", "CI exa", "exa pipeline". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill exa-ci-integration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.