Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Smart Web Search
v3.1.0Smart Web Search v3.1 - Intelligent search with Baidu (China) and Google (International) as primary engines. Real-time news, ad filtering, content de-toxicat...
⭐ 1· 115·1 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description match the instructions: SKILL.md instructs fetching search engine pages (Baidu, Startpage/Google, DuckDuckGo, etc.) and performing de-duplication, ad-filtering, and summarization. This functionality would not legitimately require credentials or broad system access. However, metadata is inconsistent: registry listing at the top shows no required binaries, while _meta.json lists 'curl' under requirements. Also some docs state 'no external API' while the skill explicitly fetches external search engine pages — this is functionally coherent but the wording across files is inconsistent.
Instruction Scope
The SKILL.md is instruction-only and instructs the agent to call web_fetch(...) against many public search endpoints. It does not tell the agent to read local files or request secrets. The high-level tasks (ad-filtering, de‑tox, source verification, AI summaries) are specified conceptually but the document does not supply concrete, auditable code for those steps — meaning the agent's own logic (or other skills) will implement them. That vagueness grants the agent discretion on how to filter, summarize, and what to include in outbound requests, which is a scope/clarity concern but not manifestly malicious.
Install Mechanism
There is no install spec and no code files executed at install time; the skill is instruction-only. This minimizes install-time risk. (Files are documentation only; there is no download/extract/execute install step.)
Credentials
Declared requirements differ between sources: top-level 'Requirements' shows none, but _meta.json lists 'curl' in requirements.bins. The skill itself uses a web_fetch tool in instructions (not curl). There are no required environment variables or credentials, which is appropriate for a public-web-search skill. Still, the inconsistency about required binaries should be clarified before use.
Persistence & Privilege
The skill is not always: true, does not request persistent system-level changes, and is user-invocable. It does include guidance for feedback collection and monitoring scripts (placeholders) but nothing that forces permanent presence or modifies other skills.
What to consider before installing
Summary of things to check before installing:
- Metadata mismatch: ask the publisher to confirm required binaries (SKILL.md uses web_fetch; _meta.json lists 'curl'; top-level registry says none). Ensure your agent environment provides the expected fetch tool.
- Network/privacy: the skill will send user queries to external search engines (Baidu, Google/Startpage, DuckDuckGo, etc.). Treat searches as network requests — do not include secrets or sensitive PII in queries you don't want sent to remote servers.
- Vague processing steps: ad-filtering, de-tox, source verification and AI summaries are described but not implemented in code here; verify how your agent will perform those steps and test on non-sensitive queries first.
- Placeholder scripts: some docs contain placeholder or example scripts (monitor.sh calling https://api.example.com, TODOs in feedback_collector). Confirm these are inert or review them if you plan to run any included scripts.
- Provenance: source/homepage is unknown; repository and author links in _meta.json point to a GitHub user. If you need stronger assurance, request the real repository URL and inspect any code there.
- Safe testing: run the skill in a sandboxed/limited environment first, monitor outgoing network calls, and verify behavior matches expectations before using for sensitive tasks.
If the author can confirm/correct the curl requirement and clarify the monitoring/feedback scripts, many of the concerns are likely just documentation sloppiness rather than malicious intent.Like a lobster shell, security has layers — review code before you run it.
latestvk97e1v39fzfkbtsnkr39abg8ex832dx1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
