multi-provider-web-search

Fans out web searches across Exa, Tavily, Brave, LangSearch, and Marginalia with AI summarization and deduplication.

2|Updated Jun 1, 2017
One-click install
npx skills add https://github.com/carlos-algms/dotfiles --skill multi-provider-web-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-provider-web-search
Source: https://github.com/carlos-algms/dotfiles/tree/main/AI-configs/skills/multi-provider-web-search
Command: npx skills add https://github.com/carlos-algms/dotfiles --skill multi-provider-web-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves weak or incomplete results from a single web search provider by fanning out across multiple search backends and producing AI summaries with deduplication.

Core Features & Use Cases

  • Parallel multi-backend web search: dispatches the same query across Exa, Tavily, Brave, LangSearch, and Marginalia to broaden coverage.
  • Dedupe + AI summary: reduces repeated content and returns an AI-ready synthesized answer rather than raw links only.
  • Provider-fit and fallback guidance: emphasizes using native WebSearch first, then escalating when results are empty/weak or the user explicitly requests provider behavior; supports targeted code/docs/papers and “small/indie web” discovery patterns.

Quick Start

Use a multi-provider query with your explicit intent and ask the AI to run web-search-ai-summary for the topic you want, for example: Find recent research on retrieval-augmented generation and summarize results from multiple search providers.

Frequently Asked Questions about multi-provider-web-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve web search results when a single provider returns weak or incomplete answers?

Multi-provider web search improves answer quality by fanning out the same query across Exa, Tavily, Brave, LangSearch, and Marginalia in parallel. It deduplicates overlapping content and returns an AI-summarized answer rather than raw links.

When should I use parallel search across multiple providers instead of a standard web search?

Use multi-provider search when native web search returns empty or weak results, or when you explicitly need broader coverage for code, documentation, paper discovery, and long-tail indie web search. It applies guardrails to avoid auto-picking on generic search queries.

How do I run a multi-provider search with AI summarization for research papers?

To run parallel search, dispatch your query through the web-search-ai-summary CLI with your explicit intent, configurable result count, and timeouts. State your topic clearly, such as asking to find recent research and summarize results from multiple search providers.

Can I configure the result count and timeout for parallel web search backends?

Yes, multi-provider web search supports configurable result count and timeout settings via the web-search-ai-summary CLI. You can adjust these parameters when dispatching queries across Exa, Tavily, Brave, LangSearch, and Marginalia.

Does multi-provider search work for finding code and documentation?

Yes, multi-provider search applies to targeted code, documentation, and paper discovery patterns. By fanning out across multiple backends including Exa and Brave, it captures broader coverage for technical queries than a single provider.

What are the limitations of using multi-provider fanout search?

Multi-provider fanout search includes guardrails to avoid auto-picking on generic search queries, requiring users to explicitly request provider behavior. It also depends on parallel dispatch via the web-search-ai-summary CLI, which adds latency from querying multiple backends.