← Back to Skills Marketplace

google-search-wsl

Name: google-search-wsl
Author: jesson-hh

by jesson-hh · GitHub ↗ · v1.0.0 · MIT-0

cross-platform ⚠ suspicious

121

Downloads

Stars

Active Installs

Versions

Install in OpenClaw

/install google-search-wsl

Description

Perform Google searches and retrieve web or news results via Chrome browser running in WSL using remote debugging with OpenClaw tool.

README (SKILL.md)

Google Search (WSL Chrome)

Perform Google searches through Chrome browser in WSL.

Prerequisites

google-chrome-stable or google-chrome installed in WSL
WSLg available (or X11 forwarding configured)
OpenClaw browser tool enabled

Quick Start

1. Launch Chrome

Run the startup script:

bash ~/.openclaw/scripts/google-search-chrome.sh

Or start manually:

export DISPLAY=:0
google-chrome-stable --remote-debugging-port=9222 \
  --remote-allow-origins='*' \
  --user-data-dir="$HOME/.openclaw/chrome-debug-profile" \
  --lang=zh-CN \
  --disable-gpu \
  --disable-dev-shm-usage &

2. Verify Chrome is Running

curl -s http://127.0.0.1:9222/json/version

Should return Chrome version information.

3. Search Using Browser Tool

browser action=open url="https://www.google.com/search?q=your+search+term" profile=user
browser action=snapshot targetId=\x3Creturned-targetId>

Troubleshooting

Chrome Won't Start (Missing X server)

Ensure WSLg is available, or set the DISPLAY environment variable:

export DISPLAY=:0
# Or check WSLg
ls /mnt/wslg/.X11-unix/

Port 9222 Already in Use

Check and kill the occupying process:

lsof -i :9222
kill \x3CPID>

Empty Search Results

Check network connection
Try using a proxy (if HTTP_PROXY is configured)
Wait for the page to fully load before taking a snapshot

Tips

Chinese keywords in search URLs will be automatically encoded
Use snapshot to get page content, then extract the needed information
For news search, use the tbm=nws parameter: /search?q=keyword&tbm=nws

Usage Guidance

This skill appears to do what it says: launch Chrome in WSL with remote debugging so the OpenClaw browser tool can control it. Before using it: (1) review and decide where the startup script should live (SKILL.md expects ~/.openclaw/scripts but the bundle contains scripts/google-search-chrome.sh); (2) be aware it opens a local Chromium remote-debugging port (default 9222) and writes a browser profile under $HOME/.openclaw/chrome-debug-profile — avoid exposing that port to untrusted networks and inspect the profile directory if you care about privacy; (3) the script accepts optional GOOGLE_SEARCH_* env vars (not declared in metadata) — set them if you need to change port, data dir, timeout, language, or GPU behavior; (4) only run this on machines you control and trust, since the browser tool will be able to load pages and access session data in that profile; and (5) if you need stronger assurance, run the script manually and inspect its output before allowing any automated agent to invoke the browser tool.

Capability Analysis

Type: OpenClaw Skill Name: google-search-wsl Version: 1.0.0 The skill configures Google Chrome with the `--remote-allow-origins='*'` flag in `scripts/google-search-chrome.sh`, which is a security vulnerability that allows any website visited in that browser to potentially interact with the Chrome DevTools Protocol (CDP) on port 9222. While this configuration is often used to facilitate automation, it creates a significant attack surface for cross-site exploitation. The script and instructions in `SKILL.md` otherwise appear aligned with the stated purpose of enabling web searches within a WSL environment.

Capability Assessment

✓ Purpose & Capability

The script and SKILL.md match the description: they start a Chrome/Chromium instance in WSL with remote-debugging enabled so the OpenClaw browser tool can drive searches. The script's WSL checks, data-dir usage, and Chrome flags are appropriate for that purpose.

ℹ Instruction Scope

SKILL.md tells the agent/user to run a script at ~/.openclaw/scripts/google-search-chrome.sh, but the packaged file is scripts/google-search-chrome.sh with no install step—there's a minor mismatch about where the script should live. The instructions direct starting Chrome with remote-debugging on localhost (9222) and using the browser tool; they do not instruct reading or exfiltrating unrelated files. The guidance about using HTTP_PROXY and DISPLAY is operational (not exfiltration) but SKILL.md mentions some env vars (HTTP_PROXY) while the script actually uses GOOGLE_SEARCH_* variables that are not declared in metadata.

✓ Install Mechanism

There is no install spec (instruction-only with a packaged script). That is low-risk from an install perspective because nothing is being downloaded or automatically written to disk by an installer; the script will only run if the user invokes it.

ℹ Credentials

No credentials or sensitive environment variables are requested. The script does create and use a user-data-dir under $HOME/.openclaw/chrome-debug-profile and reads optional env vars (GOOGLE_SEARCH_CHROME_PORT, GOOGLE_SEARCH_CHROME_DATA, GOOGLE_SEARCH_CHROME_TIMEOUT, GOOGLE_SEARCH_DISABLE_GPU, GOOGLE_SEARCH_LANG) which are not declared in the skill metadata. This is reasonable for a browser-launch helper but should be noted because it stores browser profile data locally.

✓ Persistence & Privilege

The skill is not always-enabled and makes no platform-wide configuration changes. It writes only to a per-user data directory and spawns a local Chrome process; it does not request elevated system privileges.

How to Use

Make sure OpenClaw is installed (local or Docker)
Run the install command in chat: /install google-search-wsl
After installation, invoke the skill by name or use /google-search-wsl
Provide required inputs per the skill's parameter spec and get structured output

Version History

v1.0.0

- Initial release of google-search-wsl skill. - Enables Google searches using Chrome browser within the WSL environment, controlled via CDP protocol. - Designed for trending news, general information lookup, and web research tasks. - Detailed setup instructions provided for launching Chrome in WSL and connecting via OpenClaw browser tool. - Troubleshooting guidance included for common issues like Chrome startup and network problems. - Tips added for effective searches, including news mode and handling of non-English keywords.

Metadata

Slug google-search-wsl

Version 1.0.0

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 1

Frequently Asked Questions

What is google-search-wsl?

Perform Google searches and retrieve web or news results via Chrome browser running in WSL using remote debugging with OpenClaw tool. It is an AI Agent Skill for Claude Code / OpenClaw, with 121 downloads so far.

How do I install google-search-wsl?

Run "/install google-search-wsl" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is google-search-wsl free?

Yes, google-search-wsl is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does google-search-wsl support?

google-search-wsl is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created google-search-wsl?

It is built and maintained by jesson-hh (@jesson-hh); the current version is v1.0.0.

More Skills