exa-migration-deep-dive
Migrate from other search APIs (Google, Bing, Tavily, Serper) to Exa neural search. Use when switching to Exa from another search provider, migrating search pipelines, or evaluating Exa as a replacement for traditional search APIs. Trigger with phrases like "migrate to exa", "switch to exa", "replace google search with exa", "exa vs tavily", "exa migration", "move to exa".
Best use case
exa-migration-deep-dive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Migrate from other search APIs (Google, Bing, Tavily, Serper) to Exa neural search. Use when switching to Exa from another search provider, migrating search pipelines, or evaluating Exa as a replacement for traditional search APIs. Trigger with phrases like "migrate to exa", "switch to exa", "replace google search with exa", "exa vs tavily", "exa migration", "move to exa".
Teams using exa-migration-deep-dive should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/exa-migration-deep-dive/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How exa-migration-deep-dive Compares
| Feature / Agent | exa-migration-deep-dive | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Migrate from other search APIs (Google, Bing, Tavily, Serper) to Exa neural search. Use when switching to Exa from another search provider, migrating search pipelines, or evaluating Exa as a replacement for traditional search APIs. Trigger with phrases like "migrate to exa", "switch to exa", "replace google search with exa", "exa vs tavily", "exa migration", "move to exa".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Exa Migration Deep Dive
## Current State
!`npm list exa-js 2>/dev/null | grep exa-js || echo 'exa-js not installed'`
!`npm list 2>/dev/null | grep -E '(google|bing|tavily|serper|serpapi)' || echo 'No competing search SDK found'`
## Overview
Migrate from traditional search APIs (Google Custom Search, Bing Web Search, Tavily, Serper) to Exa's neural search API. Key differences: Exa uses semantic/neural search instead of keyword matching, returns content (text/highlights/summary) in a single API call, and supports similarity search from a seed URL.
## API Comparison
| Feature | Google/Bing | Tavily | Exa |
|---------|-------------|--------|-----|
| Search model | Keyword | AI-enhanced | Neural embeddings |
| Content in results | Snippets only | Full text | Text + highlights + summary |
| Similarity search | No | No | `findSimilar()` by URL |
| AI answer | No | Yes | `answer()` + `streamAnswer()` |
| Categories | No | No | company, news, research paper, tweet, people |
| Date filtering | Limited | Yes | `startPublishedDate` / `endPublishedDate` |
| Domain filtering | Yes | Yes | `includeDomains` / `excludeDomains` (up to 1200) |
## Instructions
### Step 1: Install Exa SDK
```bash
set -euo pipefail
npm install exa-js
# Remove old SDK if replacing
# npm uninstall google-search-api tavily serpapi
```
### Step 2: Create Adapter Layer
```typescript
// src/search/adapter.ts
import Exa from "exa-js";
// Define a provider-agnostic search interface
interface SearchResult {
title: string;
url: string;
snippet: string;
score?: number;
publishedDate?: string;
}
interface SearchResponse {
results: SearchResult[];
query: string;
}
// Exa implementation
class ExaSearchAdapter {
private exa: Exa;
constructor(apiKey: string) {
this.exa = new Exa(apiKey);
}
async search(query: string, numResults = 10): Promise<SearchResponse> {
const response = await this.exa.searchAndContents(query, {
type: "auto",
numResults,
text: { maxCharacters: 500 },
highlights: { maxCharacters: 300, query },
});
return {
query,
results: response.results.map(r => ({
title: r.title || "Untitled",
url: r.url,
snippet: r.highlights?.join(" ") || r.text?.substring(0, 300) || "",
score: r.score,
publishedDate: r.publishedDate || undefined,
})),
};
}
// Exa-only: similarity search (no equivalent in Google/Bing)
async findSimilar(url: string, numResults = 5): Promise<SearchResponse> {
const response = await this.exa.findSimilarAndContents(url, {
numResults,
text: { maxCharacters: 500 },
excludeSourceDomain: true,
});
return {
query: url,
results: response.results.map(r => ({
title: r.title || "Untitled",
url: r.url,
snippet: r.text?.substring(0, 300) || "",
score: r.score,
})),
};
}
}
```
### Step 3: Feature Flag Traffic Shift
```typescript
// src/search/router.ts
function getSearchProvider(): "legacy" | "exa" {
const exaPercentage = Number(process.env.EXA_TRAFFIC_PERCENTAGE || "0");
return Math.random() * 100 < exaPercentage ? "exa" : "legacy";
}
async function search(query: string, numResults = 10): Promise<SearchResponse> {
const provider = getSearchProvider();
if (provider === "exa") {
return exaAdapter.search(query, numResults);
}
return legacyAdapter.search(query, numResults);
}
// Gradually increase: 0% → 10% → 50% → 100%
// EXA_TRAFFIC_PERCENTAGE=10
```
### Step 4: Query Translation
```typescript
// Exa neural search works best with natural language, not keyword syntax
function translateQuery(legacyQuery: string): string {
return legacyQuery
// Remove boolean operators (Exa doesn't use them)
.replace(/\b(AND|OR|NOT)\b/gi, " ")
// Remove quotes (Exa uses semantic matching, not exact)
.replace(/"/g, "")
// Remove site: operator (use includeDomains instead)
.replace(/site:\S+/gi, "")
// Clean up extra whitespace
.replace(/\s+/g, " ")
.trim();
}
// Extract domain filters from legacy query
function extractDomainFilter(query: string): string[] {
const domains: string[] = [];
const siteMatches = query.matchAll(/site:(\S+)/gi);
for (const match of siteMatches) {
domains.push(match[1]);
}
return domains;
}
```
### Step 5: Validation and Comparison
```typescript
async function compareResults(query: string) {
const [legacyResults, exaResults] = await Promise.all([
legacyAdapter.search(query, 5),
exaAdapter.search(query, 5),
]);
// Compare URL overlap
const legacyUrls = new Set(legacyResults.results.map(r => new URL(r.url).hostname));
const exaUrls = new Set(exaResults.results.map(r => new URL(r.url).hostname));
const overlap = [...legacyUrls].filter(u => exaUrls.has(u));
console.log(`Legacy results: ${legacyResults.results.length}`);
console.log(`Exa results: ${exaResults.results.length}`);
console.log(`Domain overlap: ${overlap.length}/${legacyUrls.size}`);
return { legacyResults, exaResults, overlapRate: overlap.length / legacyUrls.size };
}
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Lower result count | Exa filters more aggressively | Increase `numResults` |
| Different ranking | Neural vs keyword ranking | Expected — evaluate by relevance |
| Boolean queries fail | Exa doesn't support AND/OR | Translate to natural language |
| Missing `site:` filter | Different API parameter | Use `includeDomains` parameter |
## Resources
- [Exa vs Tavily Comparison](https://exa.ai/versus/tavily)
- [Exa Search Reference](https://docs.exa.ai/reference/search)
- [exa-js SDK](https://github.com/exa-labs/exa-js)
## Next Steps
For advanced troubleshooting, see `exa-advanced-troubleshooting`.Related Skills
workhuman-upgrade-migration
Workhuman upgrade migration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman upgrade migration".
wispr-upgrade-migration
Wispr Flow upgrade migration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr upgrade migration".
windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
windsurf-migration-deep-dive
Migrate to Windsurf from VS Code, Cursor, or other AI IDEs with full configuration transfer. Use when migrating a team to Windsurf, transferring Cursor rules, or evaluating Windsurf against other AI editors. Trigger with phrases like "migrate to windsurf", "switch to windsurf", "windsurf from cursor", "windsurf from copilot", "windsurf evaluation".
webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
webflow-migration-deep-dive
Execute major Webflow migrations — from other CMS platforms to Webflow CMS, between Webflow sites, or large-scale content re-architecture using the Data API v2 bulk endpoints, strangler fig pattern, and data validation. Trigger with phrases like "migrate to webflow", "webflow migration", "import into webflow", "webflow replatform", "move content to webflow", "webflow bulk import", "wordpress to webflow".
vercel-upgrade-migration
Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection. Use when upgrading Vercel CLI versions, migrating Node.js runtimes, or updating Next.js between major versions on Vercel. Trigger with phrases like "upgrade vercel", "vercel migration", "vercel breaking changes", "update vercel CLI", "next.js upgrade on vercel".
vercel-migration-deep-dive
Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".
veeva-upgrade-migration
Veeva Vault upgrade migration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva upgrade migration".
veeva-migration-deep-dive
Veeva Vault migration deep dive for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva migration deep dive".
vastai-upgrade-migration
Upgrade Vast.ai CLI, migrate API versions, and handle breaking changes. Use when upgrading vastai CLI, detecting deprecations, or migrating between API versions. Trigger with phrases like "upgrade vastai", "vastai migration", "vastai breaking changes", "update vastai CLI".
vastai-migration-deep-dive
Migrate GPU workloads to or from Vast.ai, or between GPU providers. Use when switching from AWS/GCP/Azure GPU instances to Vast.ai, migrating between GPU types, or re-platforming ML infrastructure. Trigger with phrases like "migrate to vastai", "vastai migration", "switch to vastai", "vastai from aws", "vastai from lambda".