Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

$pwd:

multi-search-engine

Name: Multi Search Engine
Author: opensquilla

// 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.

Executar no Manus

$ git log --oneline --stat

stars:2.159

forks:147

updated:6 de maio de 2026 às 22:15

Explorador de arquivos

4 arquivos

SKILL.md

readonly

name	multi-search-engine
description	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 analysis. API-key engines gate themselves on the relevant environment variable; engines requiring no key always run.
homepage
provenance	{"origin":"clawhub-mit0","license":"MIT-0","upstream_url":"https://clawhub.ai/multi-search-engine","maintained_by":"OpenSquilla"}
metadata	{"platform":{"emoji":"🔍","requires":{"anyBins":["python","python3"]}}}

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).

When to use

Broad source discovery where you want 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

When NOT to use

A single engine is sufficient — call its API directly
The user wants headless-browser-driven scraping with full 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_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_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 → baidu plus optionally sogou for cross-check
Time-sensitive (last 24h) → brave (recency filter) or tavily
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.

related-skills.json

mesmo repositório

coding-agent.md

from "opensquilla/opensquilla"

Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Prefer non-interactive CLI modes such as codex exec, claude --print, opencode run, or pi -p.

2026-05-072.2k

cron.md

from "opensquilla/opensquilla"

Use when the user asks to schedule recurring tasks, one-off reminders, timers, or cron-style jobs through the OpenSquilla cron tool.

2026-05-072.2k

memory.md

from "opensquilla/opensquilla"

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory/**/*.md.

2026-05-072.2k

tmux.md

from "opensquilla/opensquilla"

Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.

2026-05-072.2k

deep-research.md

from "opensquilla/opensquilla"

Multi-round research with explicit methodology, evidence tracking, and citation-tagged synthesis. Trigger on 'deep dive', 'research report', 'literature review', 'investigate X across sources', 'multi-round investigation'. Distinct from the `summarize` skill, which is a single-pass condensation; this skill maintains a state file across iterations, tracks coverage, and produces a long-form report with per-claim citations. Three execution stages: plan (scope into sub-questions), iterate (record evidence per round), compile (synthesize report). The skill itself does not fetch the web — it tells the host agent which fetches to perform via OpenSquilla's existing web tools, and records what comes back.

2026-05-062.2k

docx.md

from "opensquilla/opensquilla"

Read, edit, or create Microsoft Word `.docx` files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction, in-place edit-by-run (preserves styles), and create-from-scratch with python-docx. Falls back to OOXML unzip-and-patch for layout work python-docx cannot reach.

2026-05-062.2k

package.json

"author": "opensquilla"

"repository": "opensquilla/opensquilla"

Abrir repositório GitHub Ver repositórios do creator

$ install --global

$ download --local

Executar no Manus

name	multi-search-engine
description	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 analysis. API-key engines gate themselves on the relevant environment variable; engines requiring no key always run.
homepage
provenance	{"origin":"clawhub-mit0","license":"MIT-0","upstream_url":"https://clawhub.ai/multi-search-engine","maintained_by":"OpenSquilla"}
metadata	{"platform":{"emoji":"🔍","requires":{"anyBins":["python","python3"]}}}

multi-search-engine

When to use

Broad source discovery where you want 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

When NOT to use

A single engine is sufficient — call its API directly
The user wants headless-browser-driven scraping with full 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_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_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

Routing tips

The host should pick engines by language and availability:

English queries → duckduckgo, brave, bing (one or two for triangulation)
Chinese queries → baidu plus optionally sogou for cross-check
Time-sensitive (last 24h) → brave (recency filter) or tavily
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.

multi-search-engine

multi-search-engine

When to use

When NOT to use

Quick start

Engines

Routing tips

Boundaries

Mais deste repositório

multi-search-engine

When to use

When NOT to use

Quick start

Engines

Routing tips

Boundaries

Mais deste repositório