web-researchlisted

Use when the user wants web research: gathering cited, multi-angle evidence on a specific question. Triggers on: "research X for me", "do web research on", "look up sources for", "find citations for", "gather evidence on", "what does the web say about X". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), local file search, LLM-as-judge evaluation, or paywalled/auth-gated scraping. Produces a written plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims.
existential-birds/beagle · ★ 61 · AI & Automation · score 84

Install: claude install-skill existential-birds/beagle

# Web Research Turn a sharp research question into cited, gap-flagged findings by delegating to parallel web-search subagents. The deliverable is always on disk: a written plan the caller can review, one findings file per subtopic, and a synthesized report with numbered citations. Nothing returns as inline prose, and no claim ships without a URL + title + verbatim excerpt behind it. ## When to use - A user asks for web research on a topic — "research X", "look up sources for Y", "gather evidence on Z". - Another beagle skill invokes this one programmatically as a research companion (see `references/companion-contract.md`). - The caller wants auditable output: a plan the user approved, findings files per subtopic, and a citation-backed synthesis. ## When NOT to use - Codebase lookups ("where is this function defined", "search the repo"). Use Grep/Glob. - Local file search or document extraction. Use the file tools or `artifact-analysis`. - Comparative evaluation of two implementations. Use `llm-judge`. - Paywalled or authentication-gated scraping. Out of scope — ask the caller to paste extracted content instead. - Reshaping or coaching the research question. That is the caller's job; this skill treats the incoming question as final. ## Workflow Four steps, in order. No step is skippable. 1. **Write `plan.md`** — main question verbatim, 1-5 non-overlapping subtopics, what each subtopic should establish, and how the findings will be synthesized. 2. **Plan review gate**