multi-search-engine

Dispatch keyword queries across 17 search engines with operator and time filters.

Updated May 4, 2026
One-click install
npx skills add https://github.com/234194027-cpu/xianclaw --skill multi-search-engine-234194027-cpu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-search-engine
Source: https://github.com/234194027-cpu/xianclaw/tree/main/resources/openclaw/config/skills/multi-search-engine
Command: npx skills add https://github.com/234194027-cpu/xianclaw --skill multi-search-engine-234194027-cpu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you find higher-quality web results faster by searching the same query across multiple domestic and international search engines, including privacy-focused options and WolframAlpha knowledge queries.

Core Features & Use Cases

  • Multi-engine aggregation (17 total): Covers 8 domestic and 9 international engines to reduce blind spots and ranking bias.
  • Advanced query operators: Supports common operator patterns like site filtering, filetype search, exact match, negation, and OR logic.
  • Time filtering & privacy search: Enables recency constraints (hour/day/week/month/year) and privacy-oriented engines (e.g., DuckDuckGo/Startpage/Brave).
  • WolframAlpha knowledge queries: Performs computation/knowledge lookups such as unit conversions and math answers within the same workflow.

Quick Start

Ask your AI to perform a privacy-first search for recent AI tooling by using DuckDuckGo for the query and applying the past week time filter.

Frequently Asked Questions about multi-search-engine

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

FAQPage Schema
How do I search across multiple search engines at once to reduce ranking bias?

Multi-engine search dispatches a single keyword query across 17 domestic and international search engines simultaneously to reduce ranking bias. This cross-engine aggregation minimizes result blind spots and delivers broader research coverage.

Can I use advanced query operators like site: and filetype: for web searches?

Yes, advanced web search supports common query operators like site:, filetype:, exact match, negation, and OR logic. The system injects these operator strings into URL templates to execute precise and targeted cross-engine discovery queries.

How do I filter web search results by time constraints like past hour or past week?

To filter web search results by recency, apply optional time parameters using the tbs=qdr:{h|d|w|m|y} syntax. This constrains queries to return results from the past hour, day, week, month, or year across supported engines.

Does cross-engine discovery support privacy-oriented search providers like DuckDuckGo?

Cross-engine discovery includes privacy-oriented search providers like DuckDuckGo, Startpage, and Brave to ensure privacy-aware searching. It also supports DuckDuckGo Bang shortcuts for directly querying specific websites within your workflow.

What is the best way to compute knowledge and unit conversions during a web search?

The best way to compute knowledge and unit conversions during a web search is by integrating WolframAlpha knowledge queries. This enables direct mathematical computation and factual lookups within the same multi-engine search workflow.

When should I not use a multi-engine search approach for research discovery?

You should not use a multi-engine search approach when you only need results from a single specific index, as querying 17 engines generates broad data. For simple, highly targeted lookups, a single direct engine query is more efficient.