agentleFS
NVIDIAKnown publisherNVIDIA/NeMo-Retriever/skills/nemo-retriever-mcp/SKILL.md

nemo-retriever-mcp

Skill3k starsChanged 18 days agoApache-2.0View on GitHub

Use when a task needs to search or add documents through NeMo Retriever MCP.

2 other projects use a version of this.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 0 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the NVIDIA/NeMo-Retriever repository that our weekly crawl found: only 5 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 2

    1. NVIDIA/skills★ 3.9k100% same
    2. NVIDIA/nv-ingest★ 3k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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. Very specific:

    Use the NeMo Retriever MCP tools exposed under retriever instead of the retriever CLI.

    line 9
  2. Very specific:

    Use query to search documents already available to Retriever.

    line 18
  3. Distinctive:

    Never ingest documents that are already searchable, including documents in a prebuilt index.

    line 19
  4. Very specific:

    Use ingest_documents only when required documents are not yet searchable and server-readable paths are explicitly available.

    line 21
  5. Very specific:

    After ingestion completes, use query to retrieve evidence from the added documents.

    line 24
  6. Very specific:

    Start with top_k=5 and format="hits".

    line 26
  7. Distinctive:

    Read evidence hits from the tool response and ground your answer in them.

    line 28
  8. Very specific:

    If query fails, inspect the error and retry with corrected parameters or a shorter equivalent query.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

NeMo Retriever MCP

Use the NeMo Retriever MCP tools exposed under retriever instead of the retriever CLI.

The server exposes MCP tools, not MCP resources. Do not call list_mcp_resources to discover documents or decide whether Retriever is available; an empty MCP resource list is expected.

Workflow

  • Use query to search documents already available to Retriever.
  • Never ingest documents that are already searchable, including documents in a prebuilt index.
  • Use ingest_documents only when required documents are not yet searchable and server-readable paths are explicitly available. Do not assume that paths visible to the agent are also readable by the Retriever server.
  • After ingestion completes, use query to retrieve evidence from the added documents.
  • Start with top_k=5 and format="hits". Request more only when the first successful response does not contain enough evidence to answer the task.
  • Read evidence hits from the tool response and ground your answer in them.
  • Preserve available document identifiers such as document_id, source_id, or pdf_basename, along with page numbers, when the task requests citations or structured output.
  • If query fails, inspect the error and retry with corrected parameters or a shorter equivalent query. If it still fails, report the error before using another retrieval method.

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.