Agent skill · software engineering · jeremylongshore
exa-migration-deep-dive
Migrate a legacy web-search integration to Exa through semantic, filter, freshness, relevance, cost, and rollback comparisons. Use when operating or reviewing this Exa boundary. Trigger with "Exa migration deep dive", "review Exa migration deep dive", or "fix Exa migration deep dive".
Why this skill is useful
Adds executable scripts for migrating search APIs to Exa, including adapter code and feature comparison that aren't in public docs.
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
Legacy Search to Exa Migration Overview Migrate a legacy web-search integration to Exa through semantic, filter, freshness, relevance, cost, and rollback comparisons. 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 Exa publishes a Bing migration guide, but provider fields and ranking semantics are not one-to-one. Exa Search supports domain, date, category, location, moderation, content, and deep-synthesis controls. Migration acceptance must evaluate the application outcome rather than translate parameters mechanically. 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. Inventory legacy queries, filters, result fields, freshness, quotas, and downstream assumptions. 2. Build a consented evaluation corpus with relevance and safety judgments. 3. Map each requirement to Exa Search or a separate Contents stage. 4. Run shadow comparisons under matched result, freshness, and cost budgets. 5. Canary traffic with output-shape compatibility and a provider rollback switch. 6. Remove legacy credentials only after parity, observation, and stakeholder acceptance. 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-migration-deep-dive--bade53