← ClaudeAtlas

researching-weblisted

Web research via platform web tools. Use for technical comparisons, recent facts, ecosystem news, best practices, standards, or questions needing grounded web evidence. NOT for API syntax lookup or code examples — use looking-up-docs for those. NOT for repo-specific questions — search local files first.
alexei-led/cc-thingz · ★ 33 · Code & Development · score 81
Install: claude install-skill alexei-led/cc-thingz
# Web Research Use web tools for grounded external research. Prefer primary sources, official docs, and current evidence. Do not answer from memory when the user asked for research. ## Scope Use this for: - comparisons and trade-offs - recent facts and release behavior - standards and external best practices - ecosystem, licensing, or market facts - vendor docs as evidence for non-syntax claims Do not use this for: - exact API syntax or code examples → `looking-up-docs` - repo-specific questions that local files can answer - private code, secrets, credentials, or proprietary data ## Tool selection Choose tools by question type: - Simple factual question: use the platform's focused answer or search tool. - Source selection: search first, then fetch or read the best official or primary sources. - Broad investigation: use deep or asynchronous research when available. - Follow-up detail on a cited source: fetch the relevant source directly. Do not hardcode one provider as the answer for every question. Use the tool that best matches the question and the available runtime. ## Workflow 1. Restate the research question and the decision it should inform. 2. Decide whether the question is simple, source-selection, or broad investigation. 3. Gather sources with the matching tool. 4. Prefer primary or official sources when they can answer the question. 5. Compare sourced facts against local project constraints before recommending changes. 6. Separate sourced facts from recom