Multi Search Engine

v2.1.3

Multi search engine integration with 16 engines (7 CN + 9 Global). Supports advanced search operators, time filters, site search, privacy engines, and Wolfra...

538· 114k·1.7k current·1.8k all-time
byg_pyAng@gpyangyoujun
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the actual content: SKILL.md documents composing queries against 16 search engines, advanced operators, time filters and WolframAlpha. There are no unrelated env vars, binaries, or installs requested.
Instruction Scope
Instructions are narrowly focused on performing searches and aggregating results, but they include steps to (a) set browser-like headers (user-agent spoofing) and (b) fetch search engine homepages to acquire session cookies when receiving 403/429. Those actions are coherent with the stated goal (bypass temporary blocks, maintain sessions) but increase the operational footprint and may have ToS or ethical implications; the skill claims cookies remain in-memory and are not persisted.
Install Mechanism
No install spec and no code files — instruction-only skill (lowest installation risk). Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no environment variables, no credentials, and no config paths. The actions described (HTTP fetches, in-memory cookies) do not require additional secrets, so the requested privileges are proportionate.
Persistence & Privilege
Skill is not always-enabled and doesn't request persistent presence or modify other skills. It explicitly claims transient, in-memory cookie handling and no disk persistence.
Assessment
This skill appears coherent for aggregating many search engines, but consider the following before installing: - The skill instructs the agent to set browser-like headers and to fetch homepages to obtain session cookies when blocked. While intended to recover from temporary access errors, those behaviors can skirt search engine rate limits or ToS—decide whether you accept that risk. - Although cookies are claimed to be kept in-memory and cleared after sessions, the runtime/platform may log requests or responses; avoid sending sensitive queries through the tool if you need confidentiality. - Rate limiting is recommended (1–2s delays); follow it to reduce the chance your IP is blocked. If you operate in an environment with strict network auditing, verify where web_fetch logs and telemetry are stored. - If you want stricter behavior, request a version of the skill that disables cookie acquisition and user-agent spoofing or adds explicit robots.txt enforcement code. Overall, the skill is internally consistent (benign) but has operational and policy implications you should weigh (ToS, logging, and potential IP blocking).

Like a lobster shell, security has layers — review code before you run it.

latestvk974cs0wh5ervg183hxw08rhjh84ngk4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments