Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Search, extract, and compare high-quality public sources with Exa through SandBase.
Install Exa Deep Search
$ npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sandbaseai/sandbase-skills exa-deep-search --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sandbaseai/sandbase-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/exa-deep-search .claude/skills/exa-deep-search && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "exa-deep-search" agent skill from https://github.com/sandbaseai/sandbase-skills/tree/main/marketing/exa-deep-search into .claude/skills/exa-deep-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exa-deep-search", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sandbaseai/sandbase-skills/tree/main/marketing/exa-deep-searchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sandbaseai/sandbase-skills exa-deep-search --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sandbaseai/sandbase-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/exa-deep-search .agents/skills/exa-deep-search && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "exa-deep-search" agent skill from https://github.com/sandbaseai/sandbase-skills/tree/main/marketing/exa-deep-search into .agents/skills/exa-deep-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exa-deep-search", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sandbaseai/sandbase-skills exa-deep-search --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sandbaseai/sandbase-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/exa-deep-search .cursor/skills/exa-deep-search && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "exa-deep-search" agent skill from https://github.com/sandbaseai/sandbase-skills/tree/main/marketing/exa-deep-search into .cursor/skills/exa-deep-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exa-deep-search", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sandbaseai/sandbase-skills.git --path marketing/exa-deep-search--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sandbaseai/sandbase-skills exa-deep-search --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sandbaseai/sandbase-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/exa-deep-search .gemini/skills/exa-deep-search && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "exa-deep-search" agent skill from https://github.com/sandbaseai/sandbase-skills/tree/main/marketing/exa-deep-search into .gemini/skills/exa-deep-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exa-deep-search", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sandbaseai/sandbase-skills exa-deep-searchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sandbaseai/sandbase-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/exa-deep-search .github/skills/exa-deep-search && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "exa-deep-search" agent skill from https://github.com/sandbaseai/sandbase-skills/tree/main/marketing/exa-deep-search into .github/skills/exa-deep-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exa-deep-search", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sandbaseai/sandbase-skills exa-deep-search --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sandbaseai/sandbase-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/exa-deep-search .opencode/skills/exa-deep-search && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "exa-deep-search" agent skill from https://github.com/sandbaseai/sandbase-skills/tree/main/marketing/exa-deep-search into .opencode/skills/exa-deep-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exa-deep-search", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
exa-deep-search- GitHub stars
- 203
- Token cost
- ~2k tokens
- SKILL.md length
- 1,059 words
- Files
- 4 (incl. references)
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Search, extract, and compare high-quality public sources with Exa through SandBase.
- Works in 5 steps: Frame the research question → Select and call SandBase capabilities → Search with Exa → …
- Asked for deep web research
- SKILL.md covers Operating principles, Workflow, Query crafting tips and Output, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Exa Deep Search is an agent skill from sandbaseai/sandbase-skills. Search, extract, and compare high-quality public sources with Exa through SandBase. Use when asked for deep web research, source discovery, current evidence, topic investigation, company research, or citation-ready findings.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/example-workflows.md` and `references/sandbase-api-map.md`).
It sits in Research & Science, covering Sales call preparation and Citation management. The repository describes itself as: 88 installable open-source Agent Skills for research, social intelligence, marketing, and business workflows—compatible with Codex, Claude Code, Cursor, Gemini CLI, and DeepSeek… The licence is Apache-2.0.
When your agent uses it
- Asked for deep web research
- Source discovery
- Current evidence
- Topic investigation
Example prompts
- “/exa-deep-search”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cbab581. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Exa Deep Search loads about 2k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 1,059 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sandbaseai/sandbase-skills at commit cbab581, republished under its Apache-2.0 licence (© sandbaseai). 1,059 words, ~2,022 tokens.
Download SKILL.mdSave it as
.claude/skills/exa-deep-search/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- exa-deep-search
- description
- Search, extract, and compare high-quality public sources with Exa through SandBase. Use when asked for deep web research, source discovery, current evidence, topic investigation, company research, or citation-ready findings.
Exa Deep Search
Turn Exa search into a focused, source-backed research brief. This Skill calls the named Exa capabilities in the SandBase API map through the SandBase MCP gateway. Use an authorized SandBase MCP connection and the discover → inspect → run workflow below; never request, print, or store an API key in the research output.
Read example workflows when the user needs a starting prompt or wants to understand the output.
Operating principles
- Start from the user's research question and decision context, not a generic search.
- Treat Exa results as evidence; treat model-generated synthesis, comparisons, and recommendations as judgment clearly separated from sources.
- Select search depth, time window, domains, and geography deliberately. State any assumption rather than silently defaulting.
- Optimize for source quality, recency, and relevance — not quantity.
- Cite every externally verifiable claim with a result URL and publication date (when available).
- Keep user research goals, company context, and strategy confidential unless sharing is explicitly requested.
Workflow
1. Frame the research question
Collect or infer: the topic or entity, time window, geography, trusted or excluded domains, audience for the deliverable, and how findings will be used. Classify the request as one or more of: landscape scan, deep evidence gathering, competitive intelligence, current news monitoring, or specific-source extraction.
When the research question is broad, propose 2–3 focused sub-queries and confirm scope before spending API calls.
2. Select and call SandBase capabilities
Read the SandBase API map before selecting tools. Treat each listed tool_name as a capability identifier to resolve through the SandBase gateway:
- Use
sandbase_discoverwith the provider and capability to find the current endpoint name. - Pass the returned
nametosandbase_inspect; readinputSchema, pricing, andexecute_as. - Follow
execute_asto callsandbase_runusingexecute_as.arguments.nameand schema-definedarguments. If it returns arun_id, pollsandbase_run_getwithin the task budget untilcompletedorfailed; report pending or failed runs without automatically resubmitting them. - Keep the returned endpoint name, query, search parameters, and result metadata with the returned data.
3. Search with Exa
Resolve exa_search with sandbase_discover, then map these research needs to the current inputSchema from sandbase_inspect. Use the discovered endpoint name and its execute_as template for execution:
| Research need | Search intent |
|---|---|
| Current landscape | News results within a bounded publication window, with relevant highlights |
| Deep evidence | A supported deep search mode with summaries; request full text only for selected sources |
| Trusted sources only | Restrict results to first-party, academic, or approved publisher domains |
| Competitive research | Exclude the target's own domain; use separate queries per competitor |
| Validation or quick check | A supported fast search mode with 3–5 results |
Tips:
- Write queries as natural-language statements of what a good result page would say, not short keyword strings. Exa responds best to semantic queries.
- Use the inspected schema’s supported categories to narrow result types.
- Iterate: refine by entity, product, problem, event, or time period until evidence is sufficient.
- Request relevant highlights using the inspected schema’s content options, without extracting full text for every result.
4. Extract selected sources
When deeper analysis of specific pages is needed, send selected URLs to exa_contents:
- Request full page content when analyzing structure or extracting data.
- Request focused highlights when the inspected extraction schema supports them.
- Request concise summaries when reviewing many pages, if supported.
- Include subpages only for explicit documentation, pricing, or API crawl tasks and only when supported.
- Request a live crawl only when freshness requires it and the inspected schema supports it.
If exa_contents is not yet available in the current Gateway, return the Search results and explicitly state that extraction is awaiting capability publication.
5. Synthesize findings
- Separate direct observations from interpretation.
- Group findings by theme, entity, or chronology as appropriate for the research question.
- Note disagreements between sources and evidence gaps.
- Propose follow-up queries for unresolved questions.
Show full SKILL.md (436 more words)Show less
Query crafting tips
Good Exa queries describe the content of the ideal result page:
| Poor query | Better query |
|---|---|
AI agents | How enterprises evaluate AI agent platforms for production deployment |
observability tools | Comparison of AI agent observability and tracing solutions 2025 |
competitor pricing | Pricing page for enterprise AI agent orchestration platform |
- Add temporal context: "in 2025", "since January", "latest announcement".
- Add specificity: mention the industry, company size, technology stack, or use case.
- Use the inspected schema’s domain exclusion option to avoid results you already know about.
Output
Return a structured research brief:
Source map
| # | Title | URL | Published | Relevance |
|---|---|---|---|---|
| 1 | ... | ... | ... | ... |
Key findings
Numbered findings, each citing source(s) by number.
Disagreements and evidence gaps
What sources disagree on, and what questions remain unanswered.
Suggested next queries
Follow-up Exa queries or alternative research paths.
Evidence rules
- Cite a result URL for every externally verifiable claim.
- Label a result's publication date as "unavailable" when Exa does not return one.
- Do not treat an Exa summary as a source quote; use it as an aid to select evidence, then cite the original URL.
- Do not call Exa Answer or Exa Agent endpoints. The user's Agent/LLM synthesizes the evidence.
- Do not copy long source passages; paraphrase and cite.
- Mark clearly when a finding is inferred from multiple sources vs. directly stated in one.
Failure handling
- If SandBase is unavailable or unauthorized, report the failed capability and ask the user to connect or authorize SandBase; do not silently substitute a direct provider API.
- If
exa_searchreturns few or no results, try: broader query, a different supported search mode, removed domain filters, or a wider date range. Report if the topic genuinely lacks public coverage. - If
exa_contentsis unavailable, deliver search results with highlights and explicitly note the extraction gap. - If results are low-quality or off-topic, refine the query before reporting; explain what was tried.
Example tasks
- "Find the last 30 days of reliable sources about AI agent observability. Give me a five-source brief with gaps."
- "Research how enterprise teams evaluate AI agents. Prefer company and academic sources; exclude vendor blogs."
- "Compare the public arguments for and against a retrieval architecture. Use advanced search and cite each source."
- "Find recent funding announcements in the AI developer tools space. Only include sources from the last 7 days."
- "Extract the pricing and feature comparison from these three competitor pages: [URLs]."
Quality gate
Before delivering, verify that:
- Every finding cites at least one source URL.
- Observations are separated from model-generated interpretations.
- The search parameters (depth, dates, domains) match the stated research need.
- Evidence gaps and low-confidence findings are explicitly labeled.
- The deliverable format matches what the user requested.
© sandbaseai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in marketing/exa-deep-search of sandbaseai/sandbase-skills.
- SKILL.md
- agents/openai.yaml
- references/example-workflows.md
- references/sandbase-api-map.md
Open the folder on GitHubat commit cbab581
Compare with similar skills
Exa Deep Search next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Exa Deep Search this skillsandbaseai/sandbase-skills | 203 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| NetworkxzLanqing/codex-claude-academic-skills | 4.7k | 15 repos | ~3.2k | Automated safety check: Pass | BSD-3-Clause | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence |
Similar skills
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Networkx
zLanqing/codex-claude-academic-skills
Comprehensive toolkit for creating, analyzing, and visualizing complex networks and graphs in Python.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Verification Guide
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
More from sandbaseai/sandbase-skills
All 23 skills in this repoMulti Source Search
sandbaseai/sandbase-skills
Portable multi-source research with cross-source validation and an offline evidence ledger.
Academic Research
sandbaseai/sandbase-skills
Search academic papers, scholarly articles, and research publications through SandBase.
Brand Monitoring
sandbaseai/sandbase-skills
Monitor brand mentions, sentiment, and reputation across Twitter, Reddit, news, and social platforms through SandBase.
Cash Flow Snapshot
sandbaseai/sandbase-skills
Create a 30/60/90-day cash-flow forecast from AR, AP, opening cash, payment timing, and fixed-cost data.
Competitor Monitor
sandbaseai/sandbase-skills
Monitor competitor websites, content changes, social activity, and market positioning through SandBase.
Google News Research
sandbaseai/sandbase-skills
Search and monitor news articles across Google News through SandBase.
Related
Categories
Questions about Exa Deep Search
What does Exa Deep Search do?
Search, extract, and compare high-quality public sources with Exa through SandBase. Exa Deep Search is an agent skill from sandbaseai/sandbase-skills. Search, extract, and compare high-quality public sources with Exa through SandBase.
When should I use Exa Deep Search?
Exa Deep Search fits situations like: asked for deep web research; source discovery; current evidence; topic investigation.
How do I install Exa Deep Search in Claude Code?
Run `npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a claude-code`. Or copy the skill folder (marketing/exa-deep-search in sandbaseai/sandbase-skills) into .claude/skills/exa-deep-search in your project. Claude Code loads it when a task matches its description.
How do I install Exa Deep Search in Codex?
Run `npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a codex`. Or copy the skill folder (marketing/exa-deep-search in sandbaseai/sandbase-skills) into .agents/skills/exa-deep-search in your project. Codex loads it when a task matches its description.
Can I use Exa Deep Search in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sandbaseai/sandbase-skills --skill exa-deep-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exa-deep-search, .gemini/skills/exa-deep-search, .github/skills/exa-deep-search and .opencode/skills/exa-deep-search in your project.
What does Exa Deep Search need to run?
SKILL.md names no scripts, command-line tools or credentials: Exa Deep Search is instructions for the agent only.
Does Exa Deep Search access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Exa Deep Search safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Exa Deep Search use?
Exa Deep Search is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Exa Deep Search use?
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Exa Deep Search?
Skills that share tags, products or a category with Exa Deep Search: Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars), Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars), Networkx (zLanqing/codex-claude-academic-skills, 4.7k stars) and Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Exa Deep Search?
sandbaseai (a GitHub organization) maintains it in sandbaseai/sandbase-skills, which has 203 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on September 26, 2026.
Source: sandbaseai/sandbase-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.