Run any Skill in Manus with one click

web-research

Stars9

Forks0

UpdatedJune 7, 2026 at 08:13

Research current, external, or web-based information; compare products, pricing, libraries, APIs, companies, docs, releases, issues, or news; and analyze content from URLs.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

panthomakos

panthomakos/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	web-research
description	Research current, external, or web-based information; compare products, pricing, libraries, APIs, companies, docs, releases, issues, or news; and analyze content from URLs.

Web Research

Use this skill when the user asks to research current, external, or web-based information; compare products, pricing, libraries, APIs, companies, docs, releases, issues, or news; or analyze content from one or more URLs.

Workflow

If the user provides specific URLs, use web_fetch on those URLs first.
If the user asks a broad/current question, use web_search to find sources.
Prefer primary and high-quality sources: official docs, changelogs, specs, standards, vendor pages, GitHub repositories/issues, academic or government sources, and reputable publications.
Use web_fetch to inspect promising sources before making detailed claims. Do not rely only on search snippets for important facts.
Cross-check important or surprising claims against multiple sources when practical.
Track dates: distinguish current facts from old posts, archived docs, and stale examples.
In the final answer, include source URLs for important claims and mention uncertainty or source limitations.
Be concise unless the user asks for a deep research report.

Tool Guidance

Use web_search for default discovery. It calls the reusable ~/.pi/agent/bin/pi-web-search CLI: Google curl first, then DuckDuckGo HTML fallback if Google returns JS-only/CAPTCHA/unparseable markup.
Use web_fetch for direct source inspection and analysis. It calls the reusable ~/.pi/agent/bin/pi-web-fetch CLI.
For direct URLs, skip search unless additional context or corroboration is needed.
Use agent-browser via bash only when normal fetch/search is insufficient: JS-heavy pages, clicking through interfaces, screenshots, forms, login/session workflows, or other interactive browser tasks.

More from this repository

same repository

review

panthomakos/dotfiles

Use for strict code-quality review of local changes, commits/ranges, or GitHub PRs; also for review-oriented subagents/checkpoints in orchestrated coding work.

2026-06-239

subagents

panthomakos/dotfiles

Use to delegate context-heavy or independent work to an isolated worker: broad code search, web research, multi-file exploration, long-running implementation, testing/log investigation, review, parallel analysis, or concise summarization of noisy work.

2026-06-239

handoff

panthomakos/dotfiles

Use when compressing context for another session, agent, fork, subagent, queued item, or future continuation. Defines handoff content standards, not file/session mechanics.

2026-06-169

orchestration

panthomakos/dotfiles

Use when coordinating a long-running coding effort through plans, subagents, handoffs, reviews, queues, and checkpoints while keeping the main context small.

2026-06-169

tdd

panthomakos/dotfiles

Test-driven development with red-green-refactor loop. Use by default when implementing features, fixing behavior bugs, changing public behavior, or adding integration tests; also use when user mentions testing, TDD, red-green-refactor, or test-first development.

2026-06-169

grill-me

panthomakos/dotfiles

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or says "grill me on..." or similar.

2026-06-079

name	web-research
description	Research current, external, or web-based information; compare products, pricing, libraries, APIs, companies, docs, releases, issues, or news; and analyze content from URLs.

Web Research

Workflow

If the user provides specific URLs, use web_fetch on those URLs first.
If the user asks a broad/current question, use web_search to find sources.
Prefer primary and high-quality sources: official docs, changelogs, specs, standards, vendor pages, GitHub repositories/issues, academic or government sources, and reputable publications.
Use web_fetch to inspect promising sources before making detailed claims. Do not rely only on search snippets for important facts.
Cross-check important or surprising claims against multiple sources when practical.
Track dates: distinguish current facts from old posts, archived docs, and stale examples.
In the final answer, include source URLs for important claims and mention uncertainty or source limitations.
Be concise unless the user asks for a deep research report.

Tool Guidance

Use web_search for default discovery. It calls the reusable ~/.pi/agent/bin/pi-web-search CLI: Google curl first, then DuckDuckGo HTML fallback if Google returns JS-only/CAPTCHA/unparseable markup.
Use web_fetch for direct source inspection and analysis. It calls the reusable ~/.pi/agent/bin/pi-web-fetch CLI.
For direct URLs, skip search unless additional context or corroboration is needed.
Use agent-browser via bash only when normal fetch/search is insufficient: JS-heavy pages, clicking through interfaces, screenshots, forms, login/session workflows, or other interactive browser tasks.