exa-search
Skill0 starsChanged 2 months agoMITView on GitHub
Search the web, code, companies, and people with Exa MCP. Use when the user asks for current news, facts, code samples, API docs, company details, expert profiles, or deep web research.
- Reads credentials
66 other projects use a version of this, 18 of them edited.
Adopted by
Most recently taken up by
- runehub-ai/rune-hubtheir own version, first seen Nov 15, 2026
- compozy/compozytheir own version, first seen Nov 13, 2026
- Rojios/everything-claude-codeedited, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemonedited, first seen Nov 6, 2026
- claude-world/claude-agenttheir own version, first seen Nov 1, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use deepxiv, figure-description and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
raja21068Skilldeepxiv
Search and progressively read open-access academic papers through DeepXiv. Use when the user wants layered paper access, section-level reading, trending papers, or DeepXiv-backed literature retrieval.
Also in 4 projects that use this
raja21068Skillfigure-description
Process user-provided patent figures and generate formal drawing descriptions. Use when user says \"附图处理\", \"figure description\", \"附图说明\", \"drawings description\", or wants to describe patent figures with reference numerals.
Also in 5 projects that use this
tpavanipradeepSkillbun-runtime
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
Also in 22 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 10 projects that use this
junimnjwSkillralphinho-rfc-pipeline
RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
Also in 9 projects that use this
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
- +2 more from raja21068
Other versions66 projects use a version of this.
Word for word · 0
None found.
Edited · 18
- loulanyue/awesome-claude-notes★ 27214% same
- Fmarzochi/EGC★ 6114% same
- gongyijie85/dsh-ecc★ 813% same
- chadixearth/graphyloop★ 313% same
- get-proofpilot/claude-skills-catalog★ 114% same
- NISTALTALSON/essential-claude-skills★ 110% same
- Rojios/everything-claude-code★ 114% same
- Ronnasayd/aipp★ 110% same
- SamuelNDCE/claude-super-skill-library★ 113% same
- TironFox/everything-claude-code★ 114% same
8 more not listed
Wrote their own version · 48
- affaan-m/ECC★ 246ksame name
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19ksame name
- compozy/compozy★ 2.9ksame name
- OpenMinis/MinisSkills★ 612same name
- mxyhi/ok-skills★ 511same name
- tpavanipradeep/everything-claude-code★ 104same name
- jikssha/openclaw-dae-skills★ 98same name
- mturac/everything-openai-codex★ 89same name
- mit-network/everything-claude-code★ 76same name
- exa-labs/agent-skills★ 67same name
38 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
34 rules. 0 are common, 29 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 64 edited versions we read keep these.
29
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use Exa MCP to find web pages, code, company facts, and people.
- Distinctive: line 15
Use this skill when the user asks you to:
- Distinctive: line 22
Do web research for a coding task
- Distinctive: line 26
Do not use it when the answer is already in the files the user gave you.
- Distinctive: line 37
Do not guess a tool name or field.
- Very specific: line 41
Add the Exa MCP server to ~/.claude.json:
- Distinctive: line 55
Never print, save, or share the API key in an answer.
- Distinctive: line 57
If the server or key is missing, say what is missing.
- Distinctive: line 63
Use this tool for news, facts, companies, people, and broad web search.
- Distinctive: line 84
Use this tool for code samples and docs from sites such as GitHub, Stack Overflow, and API doc sites.
- Distinctive: line 100
Use 1000 to 2000 for a small code sample.
- Distinctive: line 106
Start with three to five results.
- Distinctive: line 107
Check dates, source names, and page text.
- Distinctive: line 108
Search again with better terms if the results are weak.
- Distinctive: line 156
Do not treat a name match as proof that two profiles are the same person.
- Distinctive: line 182
Search for fresh facts:
- Very specific: line 200
Check that the code fits Node.js 22.
- Distinctive: line 202
Add one small code sample.
- Distinctive: line 207
If there are no results, make the query shorter and remove filters.
- Distinctive: line 208
If results are off topic, add a key term, site name, date, or quoted phrase.
- Distinctive: line 209
If sources disagree, show the difference.
- Distinctive: line 210
If a page is old, do not use it as proof of a current fact.
- Distinctive: line 211
If live crawl fails, use the search text and state that the full page was not checked.
- Distinctive: line 212
If a tool rejects a field, remove that field and use only fields the server lists.
- Distinctive: line 213
If the account hits a limit, stop and tell the user.
- Distinctive: line 214
If code comes from an unknown source, treat it as an example.
- Distinctive: line 215
Do not search for private data, keys, passwords, or login details.
- Distinctive: line 216
Do not claim that search results are complete.
- Very specific: line 220
Use web_search_exa for broad web facts and fresh news.
- Very specific: line 221
Use get_code_context_exa for code and API use.
- Distinctive: line 222
Add a site name when the user wants an official source.
- Distinctive: line 223
Use quoted words only when the exact phrase matters.
- Very specific: line 224
Use site: or intitle: only if Exa supports them well for the query.
- Distinctive: line 225
Keep the first search small.
“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Exa Search
Credit: This skill comes from ECC. Keep this credit when you copy or change the skill.
Use Exa MCP to find web pages, code, company facts, and people.
When to use it
Use this skill when the user asks you to:
- Search the web
- Find recent news or facts
- Find code samples or API docs
- Study a company or its rivals
- Find experts in a field
- Do web research for a coding task
- "Search for," "look up," or "find" something
- Explain the latest news about a topic
Do not use it when the answer is already in the files the user gave you.
Before you search
Exa can change its tool names, fields, and account limits. Check the tools that the Exa MCP server lists before you call them. Use the exact tool names and fields shown there.
This skill knows these tools:
web_search_exaget_code_context_exa
Do not guess a tool name or field. If a field is not listed by the server, leave it out.
Setup
Add the Exa MCP server to ~/.claude.json:
"exa-web-search": {
"command": "npx",
"args": ["-y", "exa-mcp-server"],
"env": {
"EXA_API_KEY": "YOUR_EXA_API_KEY_HERE"
}
}Get an API key from exa.ai.
Never print, save, or share the API key in an answer.
If the server or key is missing, say what is missing. Do not make up search results.
Tools
web_search_exa
Use this tool for news, facts, companies, people, and broad web search.
web_search_exa(
query: "latest AI news",
numResults: 5
)Common fields:
| Field | Type | Default | Use |
query | string | required | What to search for |
numResults | number | 8 | How many results to get |
type | string | auto | Search mode |
livecrawl | string | fallback | Ask for fresh page text when needed |
category | string | none | Narrow the search, such as company or research paper |
get_code_context_exa
Use this tool for code samples and docs from sites such as GitHub, Stack Overflow, and API doc sites.
get_code_context_exa(
query: "Python asyncio task group example",
tokensNum: 3000
)Common fields:
| Field | Type | Default | Use |
query | string | required | The code or API topic |
tokensNum | number | 5000 | How much text to get, from 1000 to 50000 |
Use 1000 to 2000 for a small code sample. Use 5000 or more for a broad topic.
Search steps
- Turn the request into a clear search query.
- Pick the right tool.
- Start with three to five results.
- Check dates, source names, and page text.
- Search again with better terms if the results are weak.
- Answer the user in your own words.
- Link to the pages that support the answer.
- Mark any guess or weak claim as unsure.
For current news, favor pages with a clear date. Check when the event took place, not only when the page was posted.
For a key fact, try to find two good sources. Favor first-hand sources, such as official docs, company pages, public records, and research papers.
Search patterns
Quick web search
web_search_exa(
query: "Node.js 22 new features",
numResults: 3
)Code search
get_code_context_exa(
query: "Rust Result error handling examples",
tokensNum: 3000
)Company search
web_search_exa(
query: "Vercel funding and value 2026",
numResults: 3,
category: "company"
)Person search
web_search_exa(
query: "AI safety researchers at Anthropic",
numResults: 5
)Do not treat a name match as proof that two profiles are the same person. Check the job, group, location, and recent work.
Deep tech search
web_search_exa(
query: "WebAssembly component model status and use",
numResults: 5
)
get_code_context_exa(
query: "WebAssembly component model code examples",
tokensNum: 4000
)Concrete example
User request:
Find the main changes in Node.js 22 and show one code sample.Steps:
- Search for fresh facts:
web_search_exa(
query: "Node.js 22 main changes official release notes",
numResults: 4
)- Search for code:
get_code_context_exa(
query: "Node.js 22 new feature code example official docs",
tokensNum: 2000
)- Check that the code fits Node.js 22.
- Give a short list of the main changes.
- Add one small code sample.
- Link to the release notes and docs.
Edge cases
- If there are no results, make the query shorter and remove filters.
- If results are off topic, add a key term, site name, date, or quoted phrase.
- If sources disagree, show the difference. Do not hide it.
- If a page is old, do not use it as proof of a current fact.
- If live crawl fails, use the search text and state that the full page was not checked.
- If a tool rejects a field, remove that field and use only fields the server lists.
- If the account hits a limit, stop and tell the user. Do not repeat calls in a loop.
- If code comes from an unknown source, treat it as an example. Check it before you tell the user to run it.
- Do not search for private data, keys, passwords, or login details.
- Do not claim that search results are complete. Some pages may be missing.
Tips
- Use
web_search_exafor broad web facts and fresh news. - Use
get_code_context_exafor code and API use. - Add a site name when the user wants an official source.
- Use quoted words only when the exact phrase matters.
- Use
site:orintitle:only if Exa supports them well for the query. - Keep the first search small. Search again only when needed.
Related skills
deep-research: Uses Firecrawl and Exa for a full research flow.market-research: Studies a market to help with a business choice.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

