smithery.ai

exa-search-ops

Use when Codex needs semantic web search, news reconnaissance, or citation gathering through the Exa MCP server.

First seen Apr 28, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,437 B
  • docs SUMMARY.md 134 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Exa Search Ops

Purpose

Coordinate Exa-based semantic searches for discovery tasks, including link gathering, trend monitoring, and citation harvesting, using the remote configuration defined in servers/exa.

Setup Checklist

  1. Set EXAENDPOINT, EXAAPIKEY, and (optionally) EXADEFAULT_REGION.
  2. Verify the exa entry exists in mcp.json with maxResults metadata tuned to the task.
  3. Track the current request quota under the Exa dashboard before kicking off large searches.

Workflow

  1. Frame the question – clarify keywords, negative keywords, date windows, and desired number of results.
  2. Search – call the search tool with structured parameters (topic, start/end date, numResults). Use follow-up expansion judiciously.
  3. Digest – parse the returned snippets, grouping them by theme and ranking by score.
  4. Cite+Store – log the title, url, and score for each item you surface downstream. Consider persisting curated lists under docs/exa/.

Notes

  • Enforce deduplication by comparing normalized URLs before presenting results.
  • Use chronological filters instead of multi calls when researching within a known time range.
  • If Exa responds with rate_limited, wait 10 seconds and retry once before escalating.