Agent skill · software engineering · jeremylongshore
exa-local-dev-loop
Build and test an Exa adapter locally using schema fixtures, recorded content-free envelopes, and an explicit opt-in live lane. Use when operating or reviewing this Exa boundary. Trigger with "Exa local dev loop", "review Exa local dev loop", or "fix Exa local dev loop".
Why this skill is useful
Provides specific project structure and mock testing patterns for Exa that the AI wouldn't reliably generate on its own.
What it needs
Requires exa-js, node, tsx, vitest 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 Deterministic Local Development Loop Overview Build and test an Exa adapter locally using schema fixtures, recorded content-free envelopes, and an explicit opt-in live lane. 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 Search results, crawl output, and rankings are time-varying. Local tests should own sanitized response fixtures for request and failure shapes, while live calls remain a separately authorized integration lane with a small budget. 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. Locate the application-owned Exa boundary and its existing tests. 2. Define typed request, response, status, and error-tag fixtures. 3. Cover Search, Contents per-URL statuses, and one retryable failure offline. 4. Inject a fake clock and deterministic retry schedule. 5. Gate any live probe behind explicit credentials and an opt-in flag. 6. Report fixture provenance, assertions, and whether a live call occurred. 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-local-dev-loop