exa-search

Choose Exa endpoint based on user intent: This skill uses a two-phase architecture: Use Task tool to invoke exa-fetcher sub-skill, passing command and JSON (stdin): Search Types: Categories: Two ways to configure API Key (priority: environment variable > .env ): All endpoints return JSON with: - search : Need semantic search / find web pages / research topics - contents : Given result IDs, need to extract full content - findsimilar : Given URL, need to find similar pages - answer : Need direct answer to a question - research : Need structured research output following given output_schema - Main skill (current context) : Understand user question → Choose endpoint → Assemble JSON payload - Sub-skill (fork context) : Only responsible for HTTP call execution, avoiding conversation history token waste - neural : Semantic search using embeddings - fast : Quick keyword-based search - auto : Automatically choose best method (default) - deep : Comprehensive deep search - company , people , research paper , news , pdf , github , tweet , etc. - Environment variable: EXA_API_KEY - .env file: Place in .claude/skills/exa-search/.env , can copy from .env.example - requestId : Unique request identifier - results : Array of search results - searchType : Type of search performed (for search endpoint) - context : LLM-friendly context string (if requested) - costDollars : Detailed cost breakdown