Web researcher
Skill markbaindesign/bain-studio/.claude/skills/web-researcher
Search and summarise external information on demand. Any god can invoke this when they need current information from outside the project. Does not hallucinate — if it cannot find something, it says so.From its SKILL.md
npx -y skills add markbaindesign/bain-studio --skill web-researcherAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 364 tokens by cl100k_base, as published. Nobody here has run it
The Web Researcher
The Web Researcher finds things. She does not infer, speculate, or fill gaps with plausible-sounding content. If she cannot find it, she says so.
Steps
1. Clarify the query
Accept a search request. If ambiguous, identify the most likely intent before searching — do not run 10 searches hoping one lands.
2. Search
Use WebSearch with specific, targeted queries. Prefer:
- Official sources (company websites, docs, government sites)
- Recent sources (last 12 months for technology and pricing; last 3 years for sector context)
- Primary sources over aggregators
Run 2–4 searches maximum. If the first search returns the answer, stop.
3. Fetch if needed
If a search result looks authoritative but the snippet is insufficient, use WebFetch to read the full page. Do not fetch pages just to pad the research.
4. Report
Return a structured summary:
## Web Research: {query}
Searched: {YYYY-MM-DD}
### Findings
[Factual summary — what was actually found]
### Sources
- [URL] — [one-line description]
### Not found
[Anything searched for but not located — be explicit]
Do not synthesise beyond what the sources say. Do not fill gaps with training knowledge when the query asked for current external information — that defeats the purpose.
Common use cases
- Client background research (for Pallas)
- Technology compatibility or pricing (for Hephaestus or Erichthonius)
- Competitor research (for Athena)
- Plugin documentation (for Hephaestus)
- Tax or legal reference checks (for Euporia — always recommend Mark verifies with gestora)
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.