What problem does it solve? When the built-in web_search tool fails or returns no results, it is hard to tell whether the cause is a stale binary, a missing API key, a truncated SearXNG instance list, or an external block like a DuckDuckGo captcha. This Skill provides a repeatable test procedure and a failure-signature lookup table to pinpoint the root cause quickly. ## Core Features & Use Cases - End-to-end verification: Rebuilds the core binary, runs a known query, and checks that hits render with title, URL, and snippet. - Failure-signature diagnosis: Maps specific error strings (searx.space JSON truncation, DDG captcha, Mojeek 403, Exa/Tavily rate limits) to concrete fixes. - Provider-layer awareness: Distinguishes API-key providers (Exa, Tavily) from the scrape fallback chain (SearXNG, DDG Lite/HTML, Mojeek) and explains cooldown and quota behavior. - Use Case: After editing core/src/search_tool.rs, run this Skill to rebuild the core, execute a test query, and confirm results come from Exa or SearXNG instead of hitting an "all backends failed" error. ## Quick Start Ask the agent to test the web_search tool with a known query and diagnose any failure using the signature table.
