web-tools-guide

Select web_search, web_fetch, or browser tools via a tiered decision flow.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/kaifashraff/jarvis-research --skill web-tools-guide-kaifashraff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-tools-guide
Source: https://github.com/kaifashraff/jarvis-research/tree/main/skills/web-tools-guide
Command: npx skills add https://github.com/kaifashraff/jarvis-research --skill web-tools-guide-kaifashraff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web information gathering often requires choosing the right tool to minimize time and maximize relevance. This guide helps teams and agents pick the correct web tool level (search, fetch, browser) based on the task at hand.

Core Features & Use Cases

  • Tiered decision flow from web_search to web_fetch to browser, optimizing for speed and completeness.
  • Reusable playbook for online research, news tracking, and dynamic content retrieval across sites.
  • Safe, consent-driven escalation with clear prompts for user approval before performing higher-risk actions.

Quick Start

Start with web_search for keywords, switch to web_fetch when a URL is known, and escalate to browser for JS-rendered pages.

Frequently Asked Questions about web-tools-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to choose between web search, fetch, and browser automation for online research?

Web information gathering requires a tiered decision flow that starts with web_search for keywords, escalates to web_fetch for known URLs, and uses browser automation only for JS-rendered pages to optimize speed and completeness.

How do I retrieve dynamic content from JS-rendered pages during web research?

To retrieve dynamic content, escalate from web_search to web_fetch, and finally use browser automation for JS-rendered pages. This tiered strategy ensures you only use heavy browser tools when lighter fetch methods cannot render the content.

When do I need to escalate from web_fetch to full browser automation?

You need to escalate to browser automation when a target page requires JavaScript rendering that web_fetch cannot execute. The workflow uses a consent-based decision flow to prompt for user approval before performing this higher-risk action.

Does this web tool strategy require user consent before switching to browser automation?

Yes, the decision flow applies a safe, consent-driven escalation model that provides clear prompts for user approval before initiating browser automation or performing higher-risk web fetching actions across multiple sites.

Can I use this tiered web tool playbook for tracking news across multiple sites?

Yes, the playbook supports online research and news tracking across multiple sites by applying a tiered decision flow that selects the appropriate web tool level based on the specific content retrieval task.