smart-web-search v1.0.4

Intelligent web search with region auto-detection, query intent optimization, and dual-tier content extraction.

Core features

1. Auto region detection

• Detects CN vs international via IP geolocation APIs + cn.bing.com probe
  • CN → Bing CN (HTTP first, headed cookie warm-up if needed)
  • International → DDG HTML
• Fallback: defaults to DDG on detection failure (proxy/timeout)

2. Query intent rewriting

Rewrites common natural-language queries for better search results:

• "深圳有什么好玩的" → "深圳 景点"
• "今日金价" → "金价"
• "React 教程" → "React 教程"
• "怎么做红烧肉" → "红烧肉 做法"

3. Dual-tier content fetching

After search, auto-fetches top N page contents (default 3):

• Tier 1: HTTP + cheerio (fast, no browser)
• Tier 2: Playwright headed (JS rendering fallback)

4. Low-quality filtering (opt-in)

--filter flag excludes common low-signal domains (zhidao.baidu.com, jingyan.baidu.com, etc.)

Install

All dependencies are installed upfront by the setup script. The skill never runs npm install or pip install at runtime.

Prerequisites

| Dependency | Purpose | Size | |---|---|---| | Node.js >= 18 | Runtime | — | | cheerio | HTML parsing | small | | commander | CLI arg parsing | small | | iconv-lite | GBK charset | small | | playwright | Browser automation | ~50 MB | | Chromium (Playwright) | Browser engine | ~150 MB |

One-command setup

# Linux / macOS
bash scripts/setup.sh

# Windows
powershell -File scripts/setup.ps1

Auto-detects region and uses npmmirror.com mirrors inside China.

Manual install

cd skills/smart-web-search
npm install
npx playwright install chromium

# Verify
node scripts/check-env.js

Skip 150 MB download if you have system Chrome:

export CHROMIUM_EXECUTABLE_PATH="/path/to/chrome"

Usage

# Search with auto-fetch (top 3 pages)
node scripts/search.js "白银价格"
node scripts/search.js "how to deploy docker" --max=5

# Disable fetch (search only)
node scripts/search.js "xxx" --fetch=0

# Filter low-quality domains
node scripts/search.js "深圳旅游攻略" --filter

# Fetch specific URLs
node scripts/fetch.js "https://example.com/page1" "https://example.com/page2"

Privacy & network

• Searches connect to Bing CN / DDG HTML directly from the skill runtime
• Headed cookie warm-up: When Bing HTTP returns <3 results, a headed browser context visits cn.bing.com to obtain session cookies. The browser closes immediately after cookie retrieval. Cookies are used only for the current search session and are not persisted to disk.
• No analytics, no telemetry, no third-party logging beyond search engine server logs

Known limitations

• Bing cookie warm-up adds 3–6s: Only triggered when HTTP search returns <3 results
• Query rewriting may miss intent: 80+ rules cover common patterns, but edge cases exist
• Low-quality filter is heuristic: May exclude valid results or miss spam
• Proxy interference: IP detection may misclassify; no manual override available
• JS-required pages: HTTP tier returns empty for SPA pages; headed tier catches them

Verification

node scripts/check-env.js
node scripts/search.js "OpenClaw" --max 2 --fetch 0

Common issues:

• node_modules not found → run npm install
• Executable doesn't exist → run bash scripts/setup.sh or set CHROMIUM_EXECUTABLE_PATH
• 0 results → network issue or search engine blocking; try different query