Agent skill · software engineering · jeremylongshore
exa-upgrade-migration
Upgrade Exa SDK or API usage through a contract inventory, fixture diff, canary, and reversible dependency change. Use when operating or reviewing this Exa boundary. Trigger with "Exa upgrade migration", "review Exa upgrade migration", or "fix Exa upgrade migration".
Why this skill is useful
Adds specific migration scripts and patterns for upgrading the exa-js SDK that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa SDK and API Upgrade Migration Overview Upgrade Exa SDK or API usage through a contract inventory, fixture diff, canary, and reversible dependency change. 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 Current Search uses auto, fast, instant, deep-lite, deep, and deep-reasoning; neural is legacy terminology for new code. SDK method names and request casing differ by language, and newer product surfaces may be beta-gated. The first-party SDK specifications and changelog are the migration authority. 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. Record current dependency, lockfile, endpoint calls, types, headers, and feature flags. 2. Read the target SDK specification and Exa changelog for breaking changes. 3. Diff owned fixtures for requests, responses, errors, statuses, and costs. 4. Update only the application adapter and regenerate its lockfile deterministically. 5. Run offline contracts, then an approved synthetic canary on the target version. 6. Retain a dependency rollback and remove compatibility code only after observation. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-upgrade-migration