Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
web-claude
v1.1.0Unified web search skill. Fallback order — web_search(Brave) → duckduckgo → claude.ai. Auto-cache search results (saved to memory/research/)
⭐ 1· 2k·23 current·24 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 SKILL.md describes a 3-tier search (Brave web_search, DuckDuckGo via python, and claude.ai browser automation). The skill metadata declares no required env vars, binaries, or installs, yet the instructions explicitly say a Brave API key is required for Tier 1 and the DuckDuckGo fallback uses a python package (duckduckgo_search). Those credentials/dependencies are expected for the stated functionality but are not declared in metadata — a mismatch.
Instruction Scope
Runtime instructions direct the agent to: call a built-in web_search tool, run an external python snippet, automate a browser on port 18800 to access claude.ai, and save full results to memory/research/ files. Saving to disk and automating the user's logged-in claude.ai browser session are within 'search' scope but they access filesystem and an authenticated browser session that the metadata does not mention. The instructions also recommend waits and snapshots which could expose session state; these behaviors should be explicitly declared.
Install Mechanism
There is no install spec (instruction-only), which keeps disk footprint low. However, the DuckDuckGo fallback calls a python snippet that requires the third-party duckduckgo_search package and assumes python is available. The skill does not declare that dependency or provide installation steps — a practical omission rather than an outright malicious indicator.
Credentials
The SKILL.md states Tier 1 "requires Brave API key" and Tier 3 requires a logged-in claude.ai browser, but the registry metadata lists no required environment variables, credentials, or config paths. In addition, the skill will write cached search results to memory/research/ without declaring that path as required. Requesting/using a Brave API key and access to browser sessions would be proportional for this functionality, but they must be declared — their absence is a red flag.
Persistence & Privilege
always:false and normal autonomous invocation are used. The only persistence explicitly described is auto-creating and writing search cache files under memory/research/. Writing user data to disk is within reason for caching, but users should be warned about what gets stored and where. The skill does not request system-wide or other-skills configuration changes.
Scan Findings in Context
[NO_SCAN_FINDINGS] expected: The scanner found nothing because this skill is instruction-only (no code files). Absence of regex findings is not evidence of safety — the SKILL.md itself contains the runtime behavior to evaluate.
What to consider before installing
This skill appears to do what it says (a 3-tier unified search) but it omits some important declarations and assumptions. Before installing or using it: (1) Confirm where and how you will supply a Brave API key (the SKILL.md says it's required but the skill metadata doesn't declare it). Store that key in a secure place and avoid embedding it in logs. (2) Be aware the DuckDuckGo fallback uses a python snippet that requires the duckduckgo_search package and a Python runtime — install and vet that package if you plan to rely on it. (3) Tier 3 automates your local OpenClaw browser (port 18800) and requires a logged-in claude.ai session; automation will interact with your authenticated browser and could expose session-contained data — only enable it if you trust the skill and want automated access to your session. (4) The skill auto-saves search results to memory/research/ — these files may contain sensitive queries or fetched content; review and control that folder or request an option to disable caching. (5) Ask the skill author to update metadata to explicitly list required env vars, dependencies, and the cache path (so you can audit and control them). If you need higher assurance, request a version that declares dependencies and briefly shows the exact commands it will run (or provide an install script that you can review).Like a lobster shell, security has layers — review code before you run it.
latestvk977vfz2kfa2ma3bp49yp3j7q581cn91
License
MIT-0
Free to use, modify, and redistribute. No attribution required.