google-search

Execute web searches through a four-level fallback chain of APIs, SearXNG, and Tor.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill google-search-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-search
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/google-search
Command: npx skills add https://github.com/yakeworld/Synthos --skill google-search-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Web search from servers often fails due to CAPTCHAs, datacenter IP blocks, and missing API keys. This Skill provides a resilient search workflow with a strict fallback chain so queries still return structured results when primary engines fail. ## Core Features & Use Cases - Four-Level Fallback Chain: SerpAPI/Brave/Serper APIs first, then a self-hosted SearXNG instance, then Startpage over Tor, then public engines as a last resort. - Unified Output Contract: Every result is normalized to {title, url, snippet, position, engine} regardless of the underlying engine. - Deployment Troubleshooting: Documented fixes for SearXNG 2026+ pitfalls (settings.yml vs .yaml, limiter.toml schema errors, msgspec missing, worker crashes) and IP-block diagnosis via Tailscale exit nodes or Tor SOCKS5. - Use Case: A research agent on a cloud server needs literature search results, but Google and Bing block its datacenter IP. The Skill diagnoses the block, routes traffic through a Tailscale exit node, and returns 10 normalized results. ## Quick Start Search the web for "S2 API paper retrieval" using the fallback chain and return 10 structured results with title, url, snippet, position, and engine.

Frequently Asked Questions about google-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a web search when Google blocks my server IP?

Use the fallback chain: try SerpAPI, Brave, or Serper API keys first, then a self-hosted SearXNG instance, then Startpage routed through Tor SOCKS5. If all SearXNG engines time out, switch the exit IP via a Tailscale exit node or Tor proxy.

How to set up SearXNG with Docker for search API access?

Mount a settings.yml file (not .yaml) into the container, remove any limiter.toml mount, set server.limiter to false, and install msgspec before the entrypoint runs. The provided docker-compose template includes these fixes.

Why does SearXNG return empty results or ConnectTimeout on all engines?

Collective ConnectTimeout usually means the host's exit IP is blocked by Google and Bing, not a SearXNG fault. First curl an external site from the host to confirm connectivity, then switch exit IPs via Tailscale exit node or Tor SOCKS5 proxy.

Can I use SearXNG's google_scholar engine for academic search?

No, the google_scholar engine is almost always blocked by Google Scholar's anti-bot defenses and returns zero results. Use the regular Google engine to surface Scholar links indirectly, or open scholar.google.com directly in a browser.

Why does Semantic Scholar API return connection reset instead of 429?

A TCP RST from Semantic Scholar means the Tor exit IP is blocked at the TCP layer, not rate-limited. Switch to a non-Tor exit or a direct connection instead of retrying through the same Tor circuit.