web-tools-guide

Guide tool selection among web_search, web_fetch, and browser automation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted attempts and inconsistent results when you need internet information by guiding the correct tool choice across web_search, web_fetch, and browser automation.

Core Features & Use Cases

  • Tiered tool selection (search → fetch → browser): Escalates from general search to URL fetching to full browser automation when pages are dynamic or require interaction.
  • Clear decision logic for known vs unknown URLs: Uses web_fetch for static URLs and browser for JS-rendered content, login-required pages, or interactive workflows.
  • Failure-safe configuration guidance: When web_search fails, it outputs the required API Key setup instructions exactly and supports a controlled fallback path.

Quick Start

Ask: “When I need to search and then read a specific article, decide whether to use web_search, web_fetch, or browser, and if web_search fails, show me the exact API Key configuration steps.”

Frequently Asked Questions about web-tools-guide

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

FAQPage Schema
How do I choose between web search and URL fetching for retrieving web content?

Use web search for finding hot topics or unknown URLs, and use URL fetching when you already have a specific static URL to read directly. This tiered strategy ensures you select the right tool to retrieve accurate web content efficiently.

When do I need browser automation instead of web fetch for reading pages?

You need browser automation for JS-rendered pages, login-gated read-only tasks, or interactive workflows. Web fetch only retrieves static content, so escalating to browser automation handles dynamic page rendering and interaction requirements.

What are the exact steps to configure the API key when web search fails?

When web search fails, the system outputs the required API key configuration instructions exactly without silent fallback. This failure-safe guidance supports a controlled path to configure keys and restore web search functionality.

Can I use browser automation to handle login-gated read-only tasks?

Yes, browser automation supports login-gated read-only tasks and interactive workflows. The tool selection logic explicitly escalates to browser automation when pages require login authentication or dynamic interaction beyond static URL fetching.

Why does the tool escalate from web search to browser automation without silent fallback?

The tiered escalation strategy enforces explicit user notification on upgrades to prevent wasted attempts and inconsistent results. This approach ensures transparent tool selection when web search fails or pages require dynamic rendering capabilities.