exa-core-workflow-a
Execute Exa neural search with contents, date filters, and domain scoping. Use when building search features, implementing RAG context retrieval, or querying the web with semantic understanding. Trigger with phrases like "exa search", "exa neural search", "search with exa", "exa searchAndContents", "exa query".
Best use case
exa-core-workflow-a is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Execute Exa neural search with contents, date filters, and domain scoping. Use when building search features, implementing RAG context retrieval, or querying the web with semantic understanding. Trigger with phrases like "exa search", "exa neural search", "search with exa", "exa searchAndContents", "exa query".
Teams using exa-core-workflow-a 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-core-workflow-a/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How exa-core-workflow-a Compares
| Feature / Agent | exa-core-workflow-a | 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?
Execute Exa neural search with contents, date filters, and domain scoping. Use when building search features, implementing RAG context retrieval, or querying the web with semantic understanding. Trigger with phrases like "exa search", "exa neural search", "search with exa", "exa searchAndContents", "exa query".
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
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Exa Core Workflow A — Neural Search
## Overview
Primary workflow for Exa: semantic web search using `search()` and `searchAndContents()`. Exa's neural search understands query meaning rather than matching keywords, making it ideal for research, RAG pipelines, and content discovery. This skill covers search types, content extraction, filtering, and categories.
## Prerequisites
- `exa-js` installed and `EXA_API_KEY` configured
- Understanding of neural vs keyword search tradeoffs
## Search Types
| Type | Latency | Best For |
|------|---------|----------|
| `auto` (default) | 300-1500ms | General queries; Exa picks best approach |
| `neural` | 500-2000ms | Conceptual/semantic queries |
| `keyword` | 200-500ms | Exact terms, names, URLs |
| `fast` | p50 < 425ms | Speed-critical applications |
| `instant` | < 150ms | Real-time autocomplete |
| `deep` | 2-5s | Maximum quality, light deep search |
| `deep-reasoning` | 5-15s | Complex research questions |
## Instructions
### Step 1: Basic Neural Search
```typescript
import Exa from "exa-js";
const exa = new Exa(process.env.EXA_API_KEY);
// Neural search: phrase your query as a statement, not a question
const results = await exa.search(
"comprehensive guide to building production RAG systems",
{
type: "neural",
numResults: 10, // max 100 for neural/deep
}
);
for (const r of results.results) {
console.log(`[${r.score.toFixed(2)}] ${r.title} — ${r.url}`);
console.log(` Published: ${r.publishedDate || "unknown"}`);
}
```
### Step 2: Search with Content Extraction
```typescript
// searchAndContents returns page text, highlights, and/or summaries
const results = await exa.searchAndContents(
"best practices for vector database selection",
{
type: "auto",
numResults: 5,
// Text: full page content as markdown
text: { maxCharacters: 2000 },
// Highlights: key excerpts relevant to a custom query
highlights: {
maxCharacters: 500,
query: "comparison of vector databases",
},
// Summary: LLM-generated summary tailored to a query
summary: { query: "which vector database should I choose?" },
}
);
for (const r of results.results) {
console.log(`## ${r.title}`);
console.log(`Summary: ${r.summary}`);
console.log(`Highlights: ${r.highlights?.join(" ... ")}`);
console.log(`Full text: ${r.text?.substring(0, 300)}...`);
}
```
### Step 3: Date and Domain Filtering
```typescript
// Filter by publication date and restrict to specific domains
const results = await exa.searchAndContents(
"TypeScript 5.5 new features",
{
type: "auto",
numResults: 10,
// Date filters use ISO 8601 format
startPublishedDate: "2024-06-01T00:00:00.000Z",
endPublishedDate: "2025-01-01T00:00:00.000Z",
// Domain filters (up to 1200 domains each)
includeDomains: ["devblogs.microsoft.com", "typescriptlang.org"],
// Text content filters (1 string, max 5 words each)
includeText: ["TypeScript"],
text: true,
}
);
```
### Step 4: Category-Scoped Search
```typescript
// Categories narrow results to specific content types
// Available: company, research paper, news, tweet, personal site,
// financial report, people
const papers = await exa.searchAndContents(
"attention mechanism improvements for long context LLMs",
{
type: "neural",
numResults: 10,
category: "research paper",
text: { maxCharacters: 3000 },
highlights: true,
}
);
const companies = await exa.search(
"AI infrastructure startup founded 2024",
{
type: "auto",
numResults: 10,
category: "company",
// Note: company and people categories do NOT support date filters
}
);
```
### Step 5: Content Freshness with LiveCrawl
```typescript
// Control whether Exa fetches fresh content or uses cache
const results = await exa.searchAndContents(
"latest AI model releases this week",
{
numResults: 5,
text: { maxCharacters: 1500 },
// maxAgeHours controls freshness (replaces deprecated livecrawl)
// 0 = always crawl fresh, -1 = never crawl, positive = max cache age
livecrawl: "preferred", // try fresh, fall back to cache
livecrawlTimeout: 10000, // 10s timeout for live crawling
}
);
```
## Output
- Ranked search results with URLs, titles, scores, and published dates
- Optional text content, highlights, and summaries per result
- Results filtered by date range, domains, categories, and text content
## Error Handling
| Error | HTTP Code | Cause | Solution |
|-------|-----------|-------|----------|
| `INVALID_REQUEST_BODY` | 400 | Invalid parameter types | Check query is string, numResults is integer |
| `INVALID_NUM_RESULTS` | 400 | numResults > 100 with highlights | Reduce numResults or remove highlights |
| Empty results array | 200 | Date filter too narrow | Widen date range or remove filter |
| Low relevance scores | 200 | Keyword-style query | Rephrase as natural language statement |
| `FETCH_DOCUMENT_ERROR` | 422 | URL content unretrievable | Use `livecrawl: "fallback"` or try without text |
## Examples
### RAG Context Retrieval
```typescript
async function getRAGContext(question: string, maxResults = 5) {
const results = await exa.searchAndContents(question, {
type: "neural",
numResults: maxResults,
text: { maxCharacters: 2000 },
highlights: { maxCharacters: 500, query: question },
});
return results.results.map((r, i) => ({
source: `[${i + 1}] ${r.title} (${r.url})`,
content: r.text,
highlights: r.highlights,
}));
}
```
## Resources
- [Exa Search Reference](https://docs.exa.ai/reference/search)
- [Exa Contents Retrieval](https://docs.exa.ai/reference/contents-retrieval)
- [Exa Search Types](https://docs.exa.ai/reference/search)
## Next Steps
For similarity search and advanced retrieval, see `exa-core-workflow-b`.Related Skills
calendar-to-workflow
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
workhuman-core-workflow-b
Workhuman core workflow b for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow b".
workhuman-core-workflow-a
Workhuman core workflow a for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow a".
wispr-core-workflow-b
Wispr Flow core workflow b for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow b".
wispr-core-workflow-a
Wispr Flow core workflow a for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow a".
windsurf-core-workflow-b
Execute Windsurf's secondary workflow: Workflows, Memories, and reusable automation. Use when creating reusable Cascade workflows, managing persistent memories, or automating repetitive development tasks. Trigger with phrases like "windsurf workflow", "windsurf automation", "windsurf memories", "cascade workflow", "windsurf slash command".
windsurf-core-workflow-a
Execute Windsurf's primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature".
webflow-core-workflow-b
Execute Webflow secondary workflows — Sites management, Pages API, Forms submissions, Ecommerce (products/orders/inventory), and Custom Code via the Data API v2. Use when managing sites, reading pages, handling form data, or working with Webflow Ecommerce products and orders. Trigger with phrases like "webflow sites", "webflow pages", "webflow forms", "webflow ecommerce", "webflow products", "webflow orders".
webflow-core-workflow-a
Execute the primary Webflow workflow — CMS content management: list collections, CRUD items, publish items, and manage content lifecycle via the Data API v2. Use when working with Webflow CMS collections and items, managing blog posts, team members, or any dynamic content. Trigger with phrases like "webflow CMS", "webflow collections", "webflow items", "create webflow content", "manage webflow CMS", "webflow content management".
veeva-core-workflow-b
Veeva Vault core workflow b for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow b".
veeva-core-workflow-a
Veeva Vault core workflow a for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow a".
vastai-core-workflow-b
Execute Vast.ai secondary workflow: multi-instance orchestration, spot recovery, and cost optimization. Use when running distributed training, handling spot preemption, or optimizing GPU spend across multiple instances. Trigger with phrases like "vastai distributed training", "vastai spot recovery", "vastai multi-gpu", "vastai cost optimization".