Skip to content

existential-birds/beagle / plugins/beagle-analysis/skills/web-research

web-research

Verified

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.

references/report-template.md

View on GitHub
# Synthesis Skeleton

The synthesis document, saved as `report.md` under the run's output directory, uses a fixed four-section layout. Sections appear in this order, every time, even when one is short. `Gaps & Limitations` is required even when findings look complete — honest accounting of what could not be established is part of the product.

Copy the skeleton below into the synthesis file and fill each section.

## Layout

```markdown
# Research: <research question, verbatim from plan.md>

## TL;DR

- <3 to 5 bullets, highest-signal findings first>
- <each bullet stands alone — a reader should grasp the answer without scrolling further>
- <cite with [^n] when a bullet makes a specific factual claim>

## Findings

### <Subtopic or theme 1>

<Paragraphs or bullets. Every factual claim carries a [^n] footnote. Group claims by subtopic or by theme that cuts across subtopics — choose whichever reads better for this question.>

### <Subtopic or theme 2>

<...>

### <Subtopic or theme N>

<...>

## Gaps & Limitations

- <What the research could not establish, and why. One bullet per gap.>
- <Any subagent that failed or returned empty — name the subtopic and the reason from its stub file.>
- <Claims that required a freshness check (retrieval date) but were not time-stamped.>
- <Questions that surfaced during research but were out of scope for this run.>

## Sources

[^1]: **Title**: <page title>
      **URL**: <url>
      **Excerpt**: "<verbatim quote>"
      **Retrieved**: <YYYY-MM-DD, omit if absent>
      **Source type**: <official-docs | vendor | blog | forum | news | other, omit if absent>

[^2]: **Title**: <...>
      **URL**: <...>
      **Excerpt**: "<...>"

[^n]: <...>
```

## Rules

- **Title line** reproduces the research question verbatim from `plan.md`. Do not paraphrase.
- **`TL;DR`** is 3-5 bullets. Not 1, not 10. If only one thing is worth saying, the research is thin — flag it in `Gaps & Limitations`.
- **`Findings`** groups by subtopic by default. If a cross-cutting theme reads better, use that instead, but keep every claim footnoted. Structure serves the reader.
- **`Gaps & Limitations`** is never empty. At minimum, include what future work would sharpen the answer. When subagents fail, each failed subtopic gets its own bullet with the subtopic name and the reason from its stub file (see `failure-modes.md`).
- **`Sources`** uses global numbering — `[^1]` through `[^n]` across the whole document, not per-section. Citation shape per `citation-schema.md`.

## Sourcing discipline

- Every bullet in `TL;DR` that makes a specific factual claim carries a footnote. Broad synthesis statements ("the market is split between two approaches") can stand without a footnote if they summarize cited claims in `Findings`.
- Inside `Findings`, no unsourced claims. If a claim cannot be cited, either drop it or move it to `Gaps & Limitations` as something the research could not establish.
- `Sources` entries match every `[^n]` used in `TL;DR` and `Findings`. Orphan citations (listed in `Sources` but never referenced) should be removed.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall