Multi Search Engine
Researchmulti-search-engineMulti Search Engine is an Agent Skill for research published in the opensquilla/opensquilla repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Query the web through multiple search engines (Brave, Tavily, SerpAPI, DuckDuckGo, Bing, Baidu, Sogou, 360) with a single CLI surface. Trigger when the user asks for a research search, fact lookup, source discovery, or wants to compare engines for coverage. The skill aggregates per-engine result lists and normalizes them into a uniform JSON shape for downstream skills (deep-research is the primary consumer). API-key engines gate themselves on the relevant environment variable; engines requiring no key always run.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/opensquilla/opensquilla/blob/HEAD/src/opensquilla/skills/bundled/multi-search-engine/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/multi-search-engine, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
multi-search-engine
A unified CLI for querying several web search engines in parallel and
returning a normalized result list. Built on httpx and beautifulsoup4
(both already in OpenSquilla default dependencies, so no extra install
beyond pip install opensquilla).
Use cases
- Building a
deep-researchround with diverse engine coverage - Fact-check a claim against >1 engine
- Compare what Bing returns vs DuckDuckGo for the same query
- Search Chinese-language sources via Baidu/Sogou/360 alongside global engines
Limitations
- A single engine sufficient → call its API directly instead
- Need headless-browser DOM rendering → this skill is HTTP-only
Quick start
python {baseDir}/scripts/search.py \
--query "openclaw skill registry" \
--engines duckduckgo,brave \
--limit 10 \
--json
Output:
{
"query": "...",
"results": [
{
"engine": "duckduckgo",
"title": "...",
"url": "https://...",
"snippet": "...",
"rank": 1
}
],
"errors": [
{"engine": "brave", "reason": "BRAVE_SEARCH_API_KEY/BRAVE_API_KEY not set; skipping"}
]
}
Engines
| Engine | Needs key | Key env var | Strength |
|---|---|---|---|
duckduckgo | no | — | Privacy-friendly, no rate limit by default |
bing | no | — | HTML scrape; respect rate limits |
baidu | no | — | Chinese-language web |
sogou | no | — | Chinese-language web |
360 | no | — | Chinese-language web |
brave | yes | BRAVE_SEARCH_API_KEY or legacy BRAVE_API_KEY | High-quality results, generous free tier |
tavily | yes | TAVILY_API_KEY | Designed for AI agents, returns clean JSON |
serpapi | yes | SERPAPI_API_KEY | Aggregator across many engines |
The script never errors out when an API-key engine's key is missing — it
records a per-engine errors entry and continues with the rest. Pass
--strict to fail fast when any requested engine is unavailable.
Routing tips
The host should pick engines by language and availability:
- English queries →
duckduckgo,brave,bing(one or two for triangulation) - Chinese queries →
baiduplus optionallysogoufor cross-check - Time-sensitive (last 24h) →
brave(recency filter) ortavily - Long-tail academic → fall back to direct arXiv / Google Scholar; this skill targets general web search
engines.md has the full per-engine guidance.
Boundaries
- HTTP-only. JS-rendered pages will not be readable; use a headless-browser skill if needed.
- Scraping engines (DuckDuckGo, Bing, Baidu, Sogou, 360) are best-effort — HTML structure changes break them. The script logs parse failures individually and keeps the run going.
- Rate limiting is not handled inside the script. Calling the same engine 10x/sec from a loop will get blocked. Add jitter and back-off in the caller.
- Captcha-protected results are not bypassed. If an engine returns a challenge page, the parser will return zero results for that engine and log a warning.