agentleFS
catalsqlb-cmdcatalsqlb-cmd/Prism-H/skills/exa-search/SKILL.md

exa-search

Skill16 starsChanged 6 months agoMITView on GitHub

AI-powered web search via Exa with content extraction. Use when user says "exa search", "web search with content", "find similar pages", or needs broad web results beyond academic databases (arXiv, Semantic Scholar).

  • Reads credentials
  • Installs packages

64 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use deepxiv, bun-runtime and 7 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.
  • raja21068Skill

    deepxiv

    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

  • tpavanipradeepSkill

    bun-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

  • niloykumarbarmanSkill

    agent-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

  • junimnjwSkill

    ralphinho-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

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • InfopibeSkill

    investor-materials

    Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.

    Also in 27 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Exa when you need results beyond academic databases, or when you want content (highlights, full text, summaries) extracted alongside …

    line 21
  2. Very specific:

    similar: If present, use find-similar mode instead of search

    line 58
  3. Very specific:

    type: Search type — auto (default), neural, fast, instant

    line 63
  4. Distinctive:

    If not found, tell the user:

    line 78
  5. Distinctive:

    After presenting results, suggest:

    line 132
  6. Very specific:

    Always check that EXA_API_KEY is set before searching

    line 165
  7. Very specific:

    Default to highlights content mode for a good balance of speed and context

    line 166
  8. Very specific:

    Use category: "research paper" when the user is clearly looking for academic content

    line 167
  9. Very specific:

    Use text content mode when the user needs full page content

    line 168

“Common” is measured: kept by at least 6 in 10 of the 63 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Exa AI-Powered Web Search

Search query: $ARGUMENTS

Role & Positioning

Exa is the broad web search source with built-in content extraction:

SkillBest for
/semantic-scholarPublished venue papers (journals, university presses), citation counts
/exa-searchBroad web search: blogs, docs, news, institutions, research papers — with content extraction

Use Exa when you need results beyond academic databases, or when you want content (highlights, full text, summaries) extracted alongside search results.

Constants

  • FETCH_SCRIPT — tools/exa_search.py relative to the current project.
  • MAX_RESULTS = 10 — Default number of results to return.

Overrides (append to arguments):

  • /exa-search "RAG pipelines" — max: 5 — top 5 results
  • /exa-search "diffusion models" — category: research paper — research papers only
  • /exa-search "startup funding" — category: news, start date: 2025-01-01 — recent news
  • /exa-search "transformer" — content: text, max chars: 8000 — full text mode
  • /exa-search "transformer" — content: summary — LLM-generated summaries
  • /exa-search "transformer" — domains: arxiv.org,huggingface.co — domain filter
  • /exa-search "https://arxiv.org/abs/2301.07041" — similar — find similar pages

Setup

Exa requires the exa-py SDK and an API key:

pip install exa-py

Set your API key:

export EXA_API_KEY=your-key-here

Get a key from exa.ai.

Workflow

Step 1: Parse Arguments

Parse $ARGUMENTS for:

  • query: The search query (required) or a URL (for find-similar mode)
  • similar: If present, use find-similar mode instead of search
  • max: Override MAX_RESULTS
  • category: research paper, news, company, personal site, financial report, people
  • content: highlights (default), text, summary, none
  • max chars: Max characters for content extraction
  • type: Search type — auto (default), neural, fast, instant
  • domains: Comma-separated include domains
  • exclude domains: Comma-separated exclude domains
  • include text: Phrase that must appear in results
  • exclude text: Phrase to exclude from results
  • start date: ISO 8601 date — only results after this
  • end date: ISO 8601 date — only results before this
  • location: Two-letter ISO country code

Step 2: Locate Script

SCRIPT=$(find tools/ -name "exa_search.py" 2>/dev/null | head -1)

If not found, tell the user:

exa_search.py not found. Make sure tools/exa_search.py exists and exa-py is installed:
pip install exa-py

Step 3: Execute Search

Standard search:

python3 "$SCRIPT" search "QUERY" --max 10 --content highlights

With filters:

python3 "$SCRIPT" search "QUERY" --max 10 \
  --category "research paper" \
  --start-date 2025-01-01 \
  --content text --max-chars 8000

Find similar pages:

python3 "$SCRIPT" find-similar "URL" --max 5 --content highlights

Get content for known URLs:

python3 "$SCRIPT" get-contents "URL1" "URL2" --content text

Step 4: Present Results

Format results as a structured table:

| # | Title | Authors | Venue/Publisher | URL | Date | Key Content |
|---|-------|---------|-----------------|-----|------|-------------|

For each result:

  • Show title and URL
  • Show published date if available
  • Show highlights, text excerpt, or summary depending on content mode
  • Flag particularly relevant results
  • For category: "research paper" hits only — also record authors (from Exa's author/authors fields, or fallback: parse from the result snippet) and venue/publisher (from publisher, source, or the domain hosting the paper). These are needed by Step 6's wiki hook; if either is unavailable for a given hit, skip wiki ingest for that one hit and log a note.

Step 5: Offer Follow-up

After presenting results, suggest:

  • Deepen: "I can fetch full text for any of these results"
  • Find similar: "I can find pages similar to any result"
  • Narrow: "I can re-search with domain/date/text filters"

Step 6: Update Research Wiki (if active, research-paper results only)

Required when research-wiki/ exists AND the search returned results of category: "research paper"; skip silently otherwise. General web results (blog posts, docs, news) are not ingested — the wiki is for papers only.

For each research paper hit, try to recover an arXiv ID from the URL (arxiv.org/abs/<id>); if present, use --arxiv-id. Otherwise fall back to manual metadata:

if [ -d research-wiki/ ] and query category was "research paper":
    for each research-paper hit in results:
        if URL matches arxiv.org/abs/<id>:
            python3 tools/research_wiki.py ingest_paper research-wiki/ \
                --arxiv-id "<id>"
        else:
            python3 tools/research_wiki.py ingest_paper research-wiki/ \
                --title "<title>" --authors "<authors joined by , >" \
                --year <year> --venue "<venue or publisher>"

The helper handles slug / dedup / page / index / log — do not handwrite papers/<slug>.md. See shared-references/integration-contract.md.

Key Rules

  • Always check that EXA_API_KEY is set before searching
  • Default to highlights content mode for a good balance of speed and context
  • Use category: "research paper" when the user is clearly looking for academic content
  • Use text content mode when the user needs full page content
  • Combine with /semantic-scholar or /research-lit for comprehensive literature coverage

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.