nlweb-retrieval-backends skillA
nlweb-retrieval-backends is agent-read markdown (skill) from orcaqubits/agentic-commerce-skills-plugins: Choose and configure NLWeb retrieval backends — Qdrant (local + remote), Azure AI Search, Elasticsearch, OpenSearch (with/without k-NN), Postgres pgvector, Milvus, Snowflake Cortex Search, Cloudflare AutoRAG, Shopify MCP, and Bing Web Search. Covers `config_retrieval.yaml`, the single `write_endpoint` rule, parallel read-fanout with URL dedup, and per-backend setup pages. Use when picking a retrieval store, migrating between backends, or debugging "results are empty.".
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# NLWeb Retrieval Backends ## Before writing code **Fetch live docs**: 1. Fetch https://github.com/nlweb-ai/NLWeb/blob/main/docs/nlweb-retrieval.md for the architectural overview. 2. Fetch https://github.com/nlweb-ai/NLWeb/blob/main/config/config_retrieval.yaml for the **canonical list of endpoint names** and their defaults — config keys move release to release. 3. Pick the per-backend setup page from `docs/setup-*.md` (Qdrant, Azure AI Search, Elasticsearch, OpenSearch, Postgres, Snowflake, Cloudflare AutoRAG). 4. Inspect `AskAgent/python/retrieval_providers/<backend>.py` for the exact client signature and required env vars. 5. Verify the embedding dimension and metric (cosine/dot/L2) the backend expects — must match the embedding provider. ## Conceptual Architecture ### The Read-Fanout, Single-Write Pattern NLWeb does something unusual: it **reads from every enabled retrieval endpoint in parallel and deduplicates by URL**, but writes go to **exactly one** `write_endpoint`. This means: - You can run a hybrid index (e.g., local Qdrant for site content + Bing for fresh news) without code changes …
Read the whole file at its exact version.
How to install
mdr add orcaqubits/agentic-commerce-skills-plugins/nlweb-retrieval-backends@git:20260513.4751044mdr add orcaqubits/agentic-commerce-skills-plugins/nlweb-retrieval-backends@sha256:e54eba249f2586d7Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_5v3g6yh2hrjnm5hk)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8121 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
orcaqubits/agentic-commerce-skills-plugins · 39 stars · license MIT · pushed 2026-09-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5v3g6yh2hrjnm5hk GET https://markdownregistry.com/api/v1/resolve?ref=orcaqubits/agentic-commerce-skills-plugins/nlweb-retrieval-backends GET https://markdownregistry.com/api/v1/blob/e54eba249f2586d72b9ff24d908a34da87bdc9e619f072c407a06ceb48b59b75
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.