openclaw-serper
v3.1.1Searches Google and extracts full page content from every result via trafilatura. Returns clean readable text, not just snippets. Use when the user needs web search, research, current events, news, factual lookups, product comparisons, technical documentation, or any question requiring up-to-date information from the internet.
⭐ 1· 2k·3 current·3 all-time
by@nesdeq
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The script performs Google searches via the Serper API and then fetches & extracts full page content with trafilatura — exactly what the name/description claim.
Instruction Scope
SKILL.md restricts behavior to a single well-formed query (max two calls) and explicitly tells agents not to re-fetch URLs. The runtime script only reads a local .env (skill root) and performs network calls to Serper and the result pages; it does not read other system files.
Install Mechanism
No install spec; the skill is instruction+script only. There are no downloads, package installs, or archive extracts performed by the skill itself (trafilatura is a normal Python dependency).
Credentials
The code requires a Serper API key (SERPER_API_KEY or SERP_API_KEY) but the registry metadata listed 'Required env vars: none'. README suggests adding the key to ~/.openclaw/.env, while the script auto-loads only the skill's own .env. This mismatch (and ambiguous instructions about where to store the key) is an inconsistency you should clear up before use.
Persistence & Privilege
The skill does not request permanent/always-on inclusion and does not modify other skills or system-wide settings. It only auto-loads a .env file from its own skill directory.
What to consider before installing
This skill appears to do what it says (search via Serper and extract page text with trafilatura), but I found some inconsistencies you should address before installing:
- Environment variable mismatch: The script requires SERPER_API_KEY (or SERP_API_KEY) but the published metadata claims no required env vars. Confirm you will supply a valid Serper API key and that you are comfortable storing it where the runtime will read it.
- .env location ambiguity: README suggests ~/.openclaw/.env, but the script auto-loads only .env in the skill directory. Decide where you want the key stored (system-wide vs skill-local) and update the files accordingly.
- Network behavior: The script will fetch arbitrary result URLs (concurrent, 3s timeout) and extract their full HTML text. This is necessary for the stated purpose, but be aware it means the agent runtime will make outbound requests to third-party sites and temporarily download page content.
- Operational considerations: Ensure the runtime environment has trafilatura installed for the Python interpreter that will run the script, and that outbound network access to google.serper.dev and result sites is acceptable. Review Serper's rate limits and the safety of placing an API key where it will be read by the agent runtime.
If you want to proceed, ask the skill owner to (1) update the published metadata to declare the required SERPER_API_KEY, and (2) clarify .env handling so you can safely provision the key. If those are corrected, the skill looks coherent and usable.Like a lobster shell, security has layers — review code before you run it.
latestvk972psnkptca811bezrhwavf7s809zvz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
