← ClaudeAtlas

web-researchlisted

Evidence-driven web and open-source research for questions that require multiple sources, factual verification, comparisons, or an adopt/adapt/build decision. Use for substantial research in foreground sessions, the genesis-researcher subagent, and research-profile background sessions. Skip for a single stable fact or a known URL that only needs fetching.
WingedGuardian/GENesis-AGI · ★ 103 · Web & Frontend · score 78
Install: claude install-skill WingedGuardian/GENesis-AGI
# Web Research ## Frame the decision State the question, the decision it informs, the required freshness, and what would count as enough evidence. Choose the lightest depth that can answer it: - **Focused:** one narrow claim or known source. Verify directly and stop. - **Substantial:** several claims, unfamiliar subject matter, comparison, or recommendation. Decompose into independent questions and synthesize them. - **Exhaustive:** high-consequence or broad landscape work. Add coverage tracking, competing explanations, and a final gap pass. Depth follows the task. Do not add an extra pass merely because the word “research” appears. ## Gather evidence 1. Decompose substantial work into questions whose results can be checked independently. Parallelize only independent searches; follow-ups that depend on an earlier result stay sequential. 2. Search with `web_search`, then fetch the sources that carry the actual claim with `web_fetch`. Use browser tools only when interaction or rendered state is necessary. 3. For software capability questions, search for existing implementations before proposing a build. Use `recon_github_search` for public repositories and issues, then `recon_github_read` to inspect repository metadata, trees, and source. Repository search accepts GitHub query syntax; issue search treats `query` as literal text and exposes repository, state, and labels as structured filters. GitHub's code-search API requires credentials, so public-only research must disco