Openclaw-dae-skills exa-search

Neural web search for source-first research, especially official docs, API references, pricing pages, product specs, company pages, and any task where low-noise results and direct text extraction matter. Use when you need precise, high-quality, non-SEO-biased web results or extracted page text/highlights. Prefer this over generic web search for official documentation and structured source retrieval. Prefer grok-search instead for breaking news, X/Twitter dynamics, real-time sentiment, or broad multi-source live synthesis.

install

source · Clone the upstream repo

git clone https://github.com/jikssha/openclaw-dae-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/jikssha/openclaw-dae-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/exa-search" ~/.claude/skills/jikssha-openclaw-dae-skills-exa-search && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/jikssha/openclaw-dae-skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/exa-search" ~/.openclaw/skills/jikssha-openclaw-dae-skills-exa-search && rm -rf "$T"

manifest: exa-search/SKILL.md

source content

Exa Search

Use Exa for source-first retrieval.

Prefer it when the task is about:

official documentation
API/reference pages
pricing/plan details
product/company pages
extracting the text of a page instead of just finding the link
expanding from one canonical page to similar pages

Do not default to Exa for:

breaking news
X/Twitter chatter
live sentiment / fast-moving discourse
broad real-time synthesis across many fresh sources

For those, prefer

grok-search

Workflow

Start with
```
docs
```
for official documentation lookups.
Use
```
search --text
```
or
```
research
```
when you need extracted body text.
Restrict domains aggressively when the user wants official sources.
Use
```
similar
```
when you already have the best canonical page and want adjacent sources.
For official-doc-only work, prefer
```
docs
```
plus domain restriction over
```
similar
```
;
```
similar
```
is semantic, not source-pure.
Return links plus extracted evidence, not just titles.

Config

Preferred key resolution order:

```
--api-key
```
```
EXA_API_KEY
```
```
EXA_API_KEYS
```
(comma-separated)
```
config.local.json
```
```
config.json
```
```
~/.codex/config/exa-search.json
```

Recommended setup for this workspace: keep the real key inside the skill folder in

config.local.json

so the entire skill can be backed up or moved as one directory.

Single key

{
  "profiles": [
    { "id": "main", "api_key": "YOUR_EXA_API_KEY" }
  ],
  "base_url": "https://api.exa.ai",
  "timeout_seconds": 30
}

Multiple keys with auto failover

{
  "profiles": [
    { "id": "main", "api_key": "KEY_1" },
    { "id": "backup-1", "api_key": "KEY_2" },
    { "id": "backup-2", "api_key": "KEY_3" }
  ],
  "base_url": "https://api.exa.ai",
  "timeout_seconds": 30
}

Failover behavior:

profiles are tried in order
401 / 403 / 429 and quota / billing / rate-limit style errors automatically move to the next key
the output includes
```
profileId
```
and
```
attempts
```
so you can see which key was used

Commands

Official docs search

python3 scripts/exa_search.py docs --query "telegram streaming openclaw"

Official docs search with extracted text

python3 scripts/exa_search.py docs --query "model failover openclaw" --text --num 2

General source-first search

python3 scripts/exa_search.py search --query "OpenClaw Telegram streaming" --num 5

Deep extraction / research

python3 scripts/exa_search.py research --query "OpenClaw model failover" --num 3

Force a specific key/profile

python3 scripts/exa_search.py docs --query "telegram streaming openclaw" --profile main

Find similar pages

python3 scripts/exa_search.py similar --url "https://docs.openclaw.ai/channels/telegram" --num 5

Notes

```
docs
```
defaults to
```
includeDomains=docs.openclaw.ai
```
.
```
research
```
defaults to text extraction.
output is normalized JSON so downstream agents can consume it reliably.
use
```
references/query-recipes.md
```
for ready-made query patterns.