\r \r

Exa MCP Skill\r

\r

Workflow\r

1. Clarify the research goal, scope, and output format.\r
2. Select one enabled tool using the guide below: web_search_exa, web_search_advanced_exa, people_search_exa.\r
3. Prefer the hosted Exa MCP endpoint with fixed tools in the URL query.\r
4. Return concise findings with links and explicit unknowns.\r
5. On rate limits (429), reduce query breadth or require an API key.\r \r

Tool Policy\r

• Enabled now: web_search_exa, web_search_advanced_exa, people_search_exa.\r
• Keep all other Exa tools disabled unless the user explicitly asks to expand.\r \r

Tool Selection Guide\r

• Use web_search_exa for fast, broad discovery when the user asks general web research.\r Example intent: "Find the latest docs and announcements about X."\r
• Use web_search_advanced_exa for precision research when you must constrain by domains, freshness, depth, or richer query controls.\r Example intent: "Search only official docs and recent sources for X."\r
• Use people_search_exa when the task is about identifying people, roles, background, or profile-style information.\r Example intent: "Find people working on X at company Y."\r \r

Selection Rules\r

• Start with web_search_exa when speed and coverage matter more than strict filtering.\r
• Choose web_search_advanced_exa when web_search_exa returns noisy or insufficiently targeted results.\r
• Choose people_search_exa only for person-centric requests, not generic topic research.\r \r

Config Reference\r

• Read references/exa-mcp-setup.md for URL templates and generic MCP snippets.\r