Web Browsing — Master Router

Invoke this skill before any browser task. It routes you to a site-specific skill when one is installed, and provides universal fallback navigation for everything else.

Step 1: Check for a Site-Specific Skill

Before opening a browser, check whether a skill exists for the target domain:

If the target domain is in this table: Invoke the matching skill immediately. Do not open a browser until you have read it.

If the target domain is not in this table: Continue to Step 2.

Step 2: Universal Navigation Protocol

For sites without a specific skill, follow this protocol to navigate efficiently with minimum screenshots.

Reconnaissance (1 screenshot max)

1. Navigate to the URL
2. Take ONE screenshot
3. Use read_page with filter="interactive" to get all clickable/input elements
4. From this single pass, identify:
   - Navigation structure (top bar, sidebar, hamburger)
   - Search capability
   - Auth state (login buttons vs user avatar)
   - Blocking overlays (cookie banners, modals, paywalls)

Clear Obstacles First

Handle these BEFORE your actual task — they block everything:

Navigate to Target

Use this priority order (fastest to slowest):

1. Direct URL — Construct and navigate directly if possible. Zero wasted clicks.
2. Search — Type query into site's search field, submit, scan results.
3. Navigation menu — Use read_page or find tool to locate nav links.
4. Scroll and scan — Last resort. Scroll methodically, screenshot to orient.

Element Finding (fastest to slowest)

Anti-patterns:

• Taking a screenshot to find a button you could find by label
• Clicking by coordinate when you have a ref_id
• Taking multiple screenshots to "make sure" (read_page confirming an element is enough)

Timing and Waiting

Detect page load without guessing: Use read_page — if it returns content, the page is ready. Check document.readyState === 'complete' via javascript_tool for heavy SPAs.

Data Extraction

Error Recovery

1. Retry once — Click didn't register? Try again. Page didn't load? Wait 2s, check again.
2. Alternative path — Button not clickable? Try keyboard shortcut. Navigation broken? Try direct URL.
3. Tell the user — Auth required, CAPTCHA blocking, site down, element truly missing.

Never silently fail or loop. Three attempts max, then escalate to the user.

Common Site Patterns

SPA (React/Vue/Angular): URL changes may not trigger real page loads. Wait for dynamic content, not just document.readyState. Use read_network_requests to detect when API calls finish.

Dashboard/Admin: Left sidebar navigation, breadcrumbs for orientation, settings under gear icon or bottom of sidebar.

E-Commerce: Products at /product/, /p/, or /dp/. Cart at /cart. Search via ?q= or ?search= parameter. Account at /account.

API-backed sites: Try site.com/api/ or check for OpenAPI spec at /openapi.json, /swagger.json, /api/docs. Programmatic API calls are always faster than browser navigation when available.

Performance Rules

1. One screenshot to orient, then use programmatic tools.
2. Construct URLs directly when possible — avoids clicking through menus.
3. Batch form inputs — read all fields once, fill all in sequence, no screenshots between.
4. Use get_page_text before screenshots for text extraction.
5. Use find before read_page before screenshots — escalate from fast to slow.
6. Never wait "just in case" — check if the page is ready, don't assume it isn't.
7. Tell the user what's happening if something is slow or broken.