exa-ci-integration
Create CI pipelines with GitHub Actions to run unit and integration tests for Exa API integrations.
Install
mkdir -p .claude/skills/exa-ci-integration && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7117" && unzip -o skill.zip -d .claude/skills/exa-ci-integration && rm skill.zipInstalls to .claude/skills/exa-ci-integration
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Configure Exa CI/CD integration with GitHub Actions and automated testing.Key capabilities
- →Configure GitHub Actions for unit and integration tests
- →Manage Exa API keys using GitHub repository secrets
- →Verify API connectivity with health checks
- →Run integration tests with real API calls
- →Gate releases based on test success
How it works
The skill provides CI/CD workflow templates that use GitHub Actions to run unit tests and integration tests, ensuring API connectivity and code integrity.
Inputs & outputs
When to use exa-ci-integration
- →Setup GitHub Actions
- →Configure integration tests
- →Add API health checks
About this skill
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
# .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_API_KEY: ${{ secrets.EXA_API_KEY }}
steps:
- name: Verify Exa API connectivity
run: |
HTTP_CODE=$(curl -s -o /dev/null -w "%{http_code}" \
-X POST https://api.exa.ai/search \
-H "x-api-key: $EXA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"CI health check","numResults":1}')
echo "Exa API status: $HTTP_CODE"
[ "$HTTP_CODE" = "200" ] || exit 1
Step 2: Configure Secrets
# 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
Step 3: Integration Test Suite
// tests/exa.integration.test.ts
import { describe, it, expect } from "vitest";
import Exa from "exa-js";
const describeWithKey = process.env.EXA_API_KEY ? describe : describe.skip;
describeWithKey("Exa API Integration", () => {
const exa = new Exa(process.env.EXA_API_KEY!);
it("should search and return results", async () => {
const result = await exa.search("JavaScript frameworks", {
type: "auto",
numResults: 3,
});
expect(result.results.length).toBeGreaterThanOrEqual(1);
expect(result.results[0]).toHaveProperty("url");
expect(result.results[0]).toHaveProperty("title");
expect(result.results[0]).toHaveProperty("score");
}, 10000);
it("should return content with searchAndContents", async () => {
const result = await exa.searchAndContents("Node.js best practices", {
numResults: 2,
text: { maxCharacters: 500 },
highlights: { maxCharacters: 200 },
});
expect(result.results[0].text).toBeDefined();
expect(result.results[0].text!.length).toBeGreaterThan(0);
}, 15000);
it("should find similar pages", async () => {
const result = await exa.findSimilar("https://nodejs.org", {
numResults: 3,
});
expect(result.results.length).toBeGreaterThanOrEqual(1);
}, 10000);
it("should handle invalid queries gracefully", async () => {
// Empty query should return 400
await expect(
exa.search("", { numResults: 1 })
).rejects.toThrow();
}, 10000);
});
Step 4: Release Gate with Exa Verification
# .github/workflows/release.yml
on:
push:
tags: ["v*"]
jobs:
verify-and-release:
runs-on: ubuntu-latest
env:
EXA_API_KEY: ${{ secrets.EXA_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: "20"
- run: npm ci
- run: npm test
- name: Verify Exa production connectivity
run: npm run test:integration
- run: npm run build
- run: npm publish
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | gh secret set EXA_API_KEY |
| Integration tests timeout | Slow API response | Increase timeout to 15000ms |
| Tests fail on forks | No access to secrets | Skip integration tests on fork PRs |
| Rate limited in CI | Too many concurrent runs | Use unique test queries per run |
Resources
- GitHub Actions Secrets
- Vitest CI Configuration
Next Steps
For deployment patterns, see exa-deploy-integration.
When not to use it
- →When running integration tests on untrusted forks
Prerequisites
Limitations
- →Integration tests require valid API key
How it compares
It automates the validation of Exa integrations within the build pipeline rather than relying on manual verification.
Compared to similar skills
exa-ci-integration side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| exa-ci-integration (this skill) | 1 | 27d | Caution | Intermediate |
| e2e-testing-patterns | 8 | 2mo | No flags | Intermediate |
| testing-workflow | 16 | 9mo | Review | Intermediate |
| perf-lighthouse | 13 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
e2e-testing-patterns
wshobson
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
perf-lighthouse
tech-leads-club
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget.
xcodebuildmcp
cameroncooke
Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
playwright-pro
alirezarezvani
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.