什么是 Exa AI 搜索与研究？

Exa 搜索 + 研究技能为 AI 智能体与 Exa API 交互提供了一个高性能接口。它支持利用神经和深度模式进行高级网页搜索、提取干净的页面内容以及专门的代码上下文检索。通过集成这些 Openclaw Skills，开发人员可以授权其智能体通过结构化输出和自动轮询处理复杂的、多步骤的研究工作流。

此技能专为需要不仅仅是基础搜索结果的技术工作流而设计。它支持特定类别的过滤（如公司、研究论文或新闻），并允许对子页面进行深度爬取，为大语言模型（LLM）驱动的任务收集详尽的上下文。

下载入口:https://github.com/openclaw/skills/tree/main/skills/xieshaocong33ethan/exa-full

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

Exa AI 搜索与研究 应用场景

• 为复杂的编程任务检索最新的文档或代码片段。
• 使用特定的类别过滤器（如公司或财务报告）进行深度市场研究。
• 提取全页内容并爬取子页面，为智能体推理提供全面的上下文。
• 执行需要结构化 JSON 输出和自动状态轮询的长时间运行的研究任务。

1. 通过环境变量或本地 .env 文件提供有效的 Exa API 密钥来初始化技能。
2. 根据需求选择特定脚本，例如用于查询的 search.sh 或用于提取的 content.sh。
3. 配置执行参数，如搜索类型（neural、deep、fast）和域名过滤器以优化结果。
4. 执行命令与 Exa API 交互，并接收结构化数据供智能体处理。
5. 对于研究任务，该技能负责处理创建任务和轮询最终结果的生命周期。

Exa AI 搜索与研究 配置指南

要使用此技能，请确保已安装 curl 和 jq。您必须使用以下方法之一设置 API 密钥：

export EXA_API_KEY="your-exa-api-key"

或者，在 Openclaw Skills 配置所在的同一目录下创建一个 .env 文件：

EXA_API_KEY=your-exa-api-key

Exa AI 搜索与研究 数据架构与分类体系

该技能返回针对 AI 消耗优化的结构化 JSON 数据。以下是处理的主要数据结构：

name: exa-full
version: 1.2.1
description: Exa AI search + Research API. Supports web/code search, content extraction, and async multi-step research tasks with outputSchema.
homepage: https://exa.ai
metadata: {"openclaw":{"emoji":"??","requires":{"bins":["curl","jq"],"env":["EXA_API_KEY"]}}}

Exa - Search + Research

Use this skill for web search, code-context search, URL content extraction, and async research workflows.

What This Skill Does

• Run Exa web search with optional category and domain filters.
• Retrieve full page content (and optional subpage crawling).
• Find code and docs context for programming queries.
• Run async research tasks (one-shot or create/poll workflows).
• Support optional structured outputs via outputSchema.

Setup

Set EXA_API_KEY using one of these methods.

export EXA_API_KEY="your-exa-api-key"

# .env next to SKILL.md
EXA_API_KEY=your-exa-api-key

Behavior:

• If EXA_API_KEY is missing in the environment, scripts load only EXA_API_KEY from .env.
• Other .env variables are ignored by the loader.

Safety and Data Handling

• SCHEMA_FILE content is sent to https://api.exa.ai/research/v1 as outputSchema.
• Never use sensitive local files for SCHEMA_FILE (for example: .env, key/cert files, secrets, internal confidential docs).
• research_create.sh blocks obvious sensitive paths/suffixes (for example: .env, .pem, .key, .p12, .pfx, id_rsa).

Command Quick Reference

Search

bash scripts/search.sh "query"

Main env vars:

• NUM=10 (max 100)
• TYPE=auto (auto, neural, fast, deep, instant)
• CATEGORY= (company, research paper, news, tweet, personal site, financial report, people)
• DOMAINS=domain1.com,domain2.com
• EXCLUDE=domain1.com,domain2.com
• SINCE=YYYY-MM-DD
• UNTIL=YYYY-MM-DD
• LOCATION=NL

Constraints:

• EXCLUDE is not supported when CATEGORY=company or CATEGORY=people.
• SINCE and UNTIL are not supported when CATEGORY=company or CATEGORY=people.
• When CATEGORY=people, DOMAINS accepts LinkedIn domains only (linkedin.com, www.linkedin.com, *.linkedin.com).

Content Extraction

bash scripts/content.sh "url1" "url2"

Main env vars:

• MAX_CHARACTERS=2000
• HIGHLIGHT_SENTENCES=3
• HIGHLIGHTS_PER_URL=2
• SUBPAGES=10
• SUBPAGE_TARGET="docs,reference,api"
• LIVECRAWL=preferred (preferred, always, fallback)
• LIVECRAWL_TIMEOUT=12000

Code Context Search

bash scripts/code.sh "query" [num_results]

Research (One-shot)

bash scripts/research.sh "instructions"

Main env vars:

• MODEL=exa-research or MODEL=exa-research-pro
• SCHEMA_FILE=path/to/schema.json
• POLL_INTERVAL=2
• MAX_WAIT_SECONDS=240
• EVENTS=true

Research (Create/Poll)

bash scripts/research_create.sh "instructions" | jq
bash scripts/research_poll.sh "researchId" | jq

Agent Decision Rules

Choose TYPE for Search

Use this decision order:

1. User explicitly asks for realtime or autocomplete -> TYPE=instant.
2. Task needs broad coverage or deeper synthesis -> TYPE=deep.
3. User asks for speed/quality balance -> TYPE=fast.
4. Otherwise -> TYPE=auto (default).

Fallback/escalation:

• If too slow or time-sensitive: deep -> auto -> fast -> instant.
• If too shallow: instant -> fast -> auto -> deep.
• Explicit user requirement always wins.

Recommended pattern:

TYPE=auto bash scripts/search.sh "query"

Common Pitfalls

• Do not pass sensitive files to SCHEMA_FILE.
• Do not combine CATEGORY=people|company with EXCLUDE, SINCE, or UNTIL.
• Prefer https://docs.exa.ai/ for subpage crawling seeds (more reliable than https://exa.ai/docs/reference/).

More Examples

See EXAMPLES.md for grouped command examples and edge-case workflows.