Web Research — facts from the outside world
Workflow
- Define the missing external fact. Local code, project docs and recorded
decisions do not need web corroboration; a fact already in the Wiki is
retrieved from there.
- Identify or read the primary source. If you know who owns the fact
(vendor docs, a repo, a spec, a law), open that URL directly with the
reader. Search only when the owner is unknown, then navigate from the
result to the original. Use a browser only for interactive or
dynamically rendered content.
- Prefer primary over retelling. Official documentation, original
research, source code, the standard text; check the actual version and
whether the answer applies to it.
- Cross-check where material. One authoritative source settles a narrow
fact; disputed, indirect or high-impact claims need independent evidence.
- Date the claim. State the version or date for anything time-sensitive;
say what may have changed since.
- Answer with sources. Link every external claim and name what stayed
unverified. Never fill a gap with invented facts: an unavailable source is
a reported limitation, not a licence to guess.
When access fails (403/429/captcha/paywall)
Try another legitimate source or access path — the project's own mirror, the
repo, a cached or archived copy, a different official page — without bypassing
access controls, signing up, or paying automatically. If the fact stays
unreachable, name it, list what you tried, and finish the parts the available
evidence supports.
Research depth
Use enough evidence to resolve the question, not a fixed count of queries or
pages. A definition can need one source; a comparison needs the alternatives,
their versions and any benchmark that speaks to the decision. Stop when more
search cannot change the answer.
Where the fact usually lives
| Kind of fact |
Owner to start from |
| API, library, CLI behavior |
Official docs, README, changelog, source code |
| Industry practice, adoption |
Engineering blogs, ADRs, issue threads, tech radars |
| Bug, error message |
Project issue tracker, release notes, Q&A with an accepted answer |
| Tool or approach comparison |
Reproducible benchmarks, practitioner reports with method |
| Regulation, standard, licence |
The issuing body's own text (.gov, ISO/IEC, licence file) |
Answer
- Result first line. What was found, in one sentence.
- Details with links. Each fact carries its source.
- Caveats. Unverified parts, version sensitivity, conflicting sources.
- Memory. Durable findings go through dev-wiki routing; a research run
does not create its own memory policy.
Gotchas
- The first search hit is often a retelling. Check who authored it and where
the numbers come from.
- SEO farms and AI-generated posts reproduce docs with errors. Go to the
original.
- Publication date is not the version date: a 2024 article may describe a
behavior removed in 2026.
- An unanswered issue thread is evidence of a problem, not of its fix;
read the resolution state.
1---2name: web-research3description: 'Use when a fact from outside the project is needed: "find out", "look up", "what do they say about", "how it works", "compare", "find information", "is this still true". Identify or read the primary source first — open a known URL directly, search only when the owner of the fact is unknown — then cross-check material claims, date them, and answer with links. Not for the local knowledge base or recorded project facts (use dev-wiki) or consequential tool/library decisions (use production-first-decisions).'4license: MIT5metadata:6 source: https://skillmd.com/skills/oleg494/web-research7 version: "6.1.0"8---910# Web Research — facts from the outside world1112## Workflow13141. **Define the missing external fact.** Local code, project docs and recorded15 decisions do not need web corroboration; a fact already in the Wiki is16 retrieved from there.172. **Identify or read the primary source.** If you know who owns the fact18 (vendor docs, a repo, a spec, a law), open that URL directly with the19 reader. Search only when the owner is unknown, then navigate from the20 result to the original. Use a browser only for interactive or21 dynamically rendered content.223. **Prefer primary over retelling.** Official documentation, original23 research, source code, the standard text; check the actual version and24 whether the answer applies to it.254. **Cross-check where material.** One authoritative source settles a narrow26 fact; disputed, indirect or high-impact claims need independent evidence.275. **Date the claim.** State the version or date for anything time-sensitive;28 say what may have changed since.296. **Answer with sources.** Link every external claim and name what stayed30 unverified. Never fill a gap with invented facts: an unavailable source is31 a reported limitation, not a licence to guess.3233## When access fails (403/429/captcha/paywall)3435Try another legitimate source or access path — the project's own mirror, the36repo, a cached or archived copy, a different official page — without bypassing37access controls, signing up, or paying automatically. If the fact stays38unreachable, name it, list what you tried, and finish the parts the available39evidence supports.4041## Research depth4243Use enough evidence to resolve the question, not a fixed count of queries or44pages. A definition can need one source; a comparison needs the alternatives,45their versions and any benchmark that speaks to the decision. Stop when more46search cannot change the answer.4748## Where the fact usually lives4950| Kind of fact | Owner to start from |51|---|---|52| API, library, CLI behavior | Official docs, README, changelog, source code |53| Industry practice, adoption | Engineering blogs, ADRs, issue threads, tech radars |54| Bug, error message | Project issue tracker, release notes, Q&A with an accepted answer |55| Tool or approach comparison | Reproducible benchmarks, practitioner reports with method |56| Regulation, standard, licence | The issuing body's own text (.gov, ISO/IEC, licence file) |5758## Answer5960- **Result first line.** What was found, in one sentence.61- **Details with links.** Each fact carries its source.62- **Caveats.** Unverified parts, version sensitivity, conflicting sources.63- **Memory.** Durable findings go through dev-wiki routing; a research run64 does not create its own memory policy.6566## Gotchas6768- The first search hit is often a retelling. Check who authored it and where69 the numbers come from.70- SEO farms and AI-generated posts reproduce docs with errors. Go to the71 original.72- Publication date is not the version date: a 2024 article may describe a73 behavior removed in 2026.74- An unanswered issue thread is evidence of a problem, not of its fix;75 read the resolution state.