القائمة
Research current, external, or web-based information; compare products, pricing, libraries, APIs, companies, docs, releases, issues, or news; and analyze content from URLs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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. |
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.
web_fetch on those URLs first.web_search to find sources.web_fetch to inspect promising sources before making detailed claims. Do not rely only on search snippets for important facts.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.web_fetch for direct source inspection and analysis. It calls the reusable ~/.pi/agent/bin/pi-web-fetch CLI.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.Use for strict code-quality review of local changes, commits/ranges, or GitHub PRs; also for review-oriented subagents/checkpoints in orchestrated coding work.
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.
Use when compressing context for another session, agent, fork, subagent, queued item, or future continuation. Defines handoff content standards, not file/session mechanics.
Use when coordinating a long-running coding effort through plans, subagents, handoffs, reviews, queues, and checkpoints while keeping the main context small.
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.
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.