web-research
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 s
npx skills add majiayu000/claude-skill-registry --skill web-research-existential-birds-beagle --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- When to use
- When NOT to use
- Workflow
- Hard gates (objective pass conditions)
- Inputs
- Output location
- The research plan (plan.md)
- Subagent dispatch
- Citations
- Synthesis (report.md)
- Failure modes
- Budget defaults
- Companion invocation contract
- Tone
What does the web-research skill do?
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 s
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill web-research-existential-birds-beagle --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.