thedixitjain Exa Web Search
Use Exa as the first web-search tool for matching requests.
Workflow
- Call
mcp__exa__web_search_exabefore drafting an answer that depends on online information. - Write a natural-language query describing the ideal source. Include dates, domains, or source types when they materially narrow the task.
- Request enough results to compare sources; use 5-10 for broad research and fewer for a targeted lookup.
- Call
mcp__exa__web_fetch_exaon the best URLs when search excerpts do not contain enough context, when exact attribution matters, or when the user asks to read a specific page. - For time-sensitive or consequential claims, compare multiple independent or primary sources. Prefer official documentation, original papers, first-party announcements, and source repositories.
- Cite the final source URLs close to the claims they support. Distinguish source statements from inference.
Boundaries
- Honor explicit user constraints about tools, domains, dates, languages, and source types.
- Use
rgor repository tools for local files instead of Exa. - Prefer a dedicated connected system when it is the authoritative source, such as Zotero for the user's library, Figma for a design file, or OpenAI Developer Docs for OpenAI product documentation.
- If Exa is unavailable or returns inadequate results, state that briefly and use another available web-search tool so the task still completes.
Source: hashgraph-online/awesome-codex-plugins → plugins/zlsbksdxl/codex-exa/skills/exa-web-search/SKILL.md