# exa-best-practices

Reference guide for Exa search tools. Covers tool selection, citation standards, search optimization, and troubleshooting. Also useful as background context for improving search quality.

Skill by Exa. Category: Knowledge.

## Install

Project (for this project only):

```sh
npx skills add exa-labs/exa-cursor-plugin --skill exa-best-practices
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add exa-labs/exa-cursor-plugin --skill exa-best-practices -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Warn

Installs: 9. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/exa-labs/exa-cursor-plugin/exa-best-practices)

## Source

[Open the source](https://github.com/exa-labs/exa-cursor-plugin/tree/HEAD/skills/exa-best-practices). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: exa-best-practices
description: "Reference guide for Exa search tools. Covers tool selection, citation standards, search optimization, and troubleshooting. Also useful as background context for improving search quality."
---

# Exa Best Practices

## Tool Selection

| Need | Tool | When |
|------|------|------|
| Web search | `web_search_exa` | Current info, news, research, general questions, code examples |
| Read a URL | `web_fetch_exa` | Extract content from a known URL |

## Citation Standards

When using Exa search results, always cite sources:

- **Inline citations**: Every fact or claim should reference its source
- **Source URLs**: Include the actual URL, not just the title
- **Sources section**: End responses with a list of all sources used
- **Never fabricate URLs**: Only cite URLs that appear in search results

## Search Quality Tips

1. **Natural language queries** work better than keyword stuffing
2. **Be specific** — include dates, names, versions when relevant
3. **Multiple queries** with different phrasings improve coverage
4. **Adjust result count** to match the depth needed (3-5 quick, 10-20 deep)

## Getting Started

1. Get your API key at https://dashboard.exa.ai/api-keys
2. Add the MCP server in Cursor Settings → MCP
3. Start searching with `/exa-search` or `/exa-fetch`

## Troubleshooting

- **Tools not available**: Check if the Exa MCP server is installed. If `web_search_exa` or `web_fetch_exa` are not in your tool list, stop and request the user to: (1) run `/exa-setup` in Cursor to add the MCP server, and (2) go to **Cursor Settings → Tools & MCP** and make sure Exa is toggled **on** (green).
- **No results**: Try rephrasing the query or broadening search terms
````

- Previous: [exa-web-search](https://syn4pse.dev/terminal/exa-web-search.md)
- Next: [exa-fetch](https://syn4pse.dev/terminal/exa-fetch.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
