web-tools-guide

To scrape dynamic content requiring JavaScript rendering, this Skill upgrades from web_search to web_fetch, then to browser automation, handling JS-rendered pages, login states, and page interactions with safe fallbacks.

For data extraction from unknown URLs, the workflow starts with web_search to locate information by keyword, then uses web_fetch on the discovered URLs to retrieve static content before escalating to browser automation if needed.

Use browser automation instead of web_fetch when the target page requires JavaScript rendering, login authentication, user interaction, or screenshots, as web_fetch is limited to static content from known URLs.

The layered workflow handles failures through clear upgrade paths and safe fallbacks, coordinating web_search, web_fetch, and browser with defined degradation configurations and rollback strategies when a lower-level tool fails.

Yes, web_fetch retrieves static content including articles, documentation, and API sources from known URLs, serving as the second layer in the search-to-fetch-to-browser workflow before any browser escalation.

Yes, the browser automation layer supports login state handling, page interactions, and screenshots, making it suitable for complex information retrieval scenarios involving dynamic websites and authenticated content.