vike-web-researchlisted

# vike-web-research Composite playbook combining `vike web search` and `vike web fetch` for cross-source synthesis. ## Workflow ### 1. Search (gather candidate URLs) ```bash vike web search "<query>" --max 5 --json ``` Capture the top results' URLs and titles. If the response includes an `answer` field, that's often enough for simple factual queries — surface it directly and skip step 2. ### 2. Fetch (only when search snippets are insufficient) ```bash vike web fetch <top-result-url> --ask "<focused question>" --json ``` Fetch only the highest-scoring (Tavily) or most-credible (Serper) URL. Re-fetching all 5 search results burns credits and adds noise. ### 3. Synthesize > **Question:** `<user query>` > **Answer (from `<source URL>`):** `<extracted answer>` > **Other relevant sources:** `<url1>`, `<url2>` (with one-line summaries each) Always link the source URL so the user can verify. ## When to skip the workflow - **One-shot fact lookup** (price, date, contract address) → if `web search` returns it in the `answer` field, just quote that - **The user already gave you a URL** → skip search, jump to `web fetch` - **On-chain question** → don't web-research; use vike's on-chain tools (`token holders`, `wallet labels`, `perp funding`, etc.) ## Anti-patterns - Don't fetch 5 URLs and average them — pick the most authoritative - Don't quote Reddit / Twitter as primary sources for hard claims (price, dates, addresses); use them for sentiment only - Don't combine web res