Agent skill · software engineering · jeremylongshore
exa-ci-integration
Add deterministic Exa contract checks to CI while keeping live credentials, spend, and volatile web results out of ordinary pull requests. Use when operating or reviewing this Exa boundary. Trigger with "Exa ci integration", "review Exa ci integration", or "fix Exa ci integration".
Why this skill is useful
Adds a complete CI/CD pipeline configuration for Exa integrations with specific testing commands and health checks that the AI wouldn't reliably generate on its own.
What it needs
Requires gh, npm installed locally. Requires exa account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa CI Contract Verification Overview Add deterministic Exa contract checks to CI while keeping live credentials, spend, and volatile web results out of ordinary pull requests. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries. Prerequisites The target repository, environment, Exa team, product surface, and accountable owner. The workload's data classification, latency and freshness promise, cost ceiling, and retention policy. Current first-party documentation plus credentials only for a narrowly approved live check. Current Contract Offline CI can verify owned request and response schemas, error tags, webhook signatures, and redaction. A live lane should be protected, synthetic, manually or schedule authorized, tightly budgeted, and non-blocking until its reliability is understood. Authentication For normal REST work, inject EXAAPIKEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client. Instructions 1. Map the Exa adapter and enumerate contracts changed by the pull request. 2. Add sanitized fixtures for success, partial Contents status, 429, 402, and 503. 3. Verify no load-time shell commands or secret-dependent preprocessing occurs. 4. Test webhook signature verification with fixed local payloads and clocks. 5. Place a one-request live smoke lane behind protected credentials and concurrency. 6. Publish content-free gate evidence and distinguish skipped from passed live checks. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. Use Write and Edit only for approved implementation or documentation changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-ci-integration