browser-discoverylisted

# Browser Discovery Skill Detect and use browser automation tools for documentation discovery when static fetching fails. ## Variables | Variable | Default | Description | |----------|---------|-------------| | PREFERRED_TOOL | auto | `auto`, `antigravity`, `cursor`, `playwright` | | WAIT_TIMEOUT | 3 | Seconds to wait for JS rendering | | MAX_PAGES | 50 | Maximum pages to discover per site | ## Instructions **MANDATORY** - Follow the Workflow steps below when browser automation is needed. - Always try curl first unless `js_required: true` is set - Detect available browser tools before attempting automation - Prefer accessibility snapshots over screenshots for link extraction ## Quick Decision Tree ``` Do you need browser automation? │ ├─ Curl returns full content? ──────────► NO - Use curl (docs-fetch-url) │ ├─ Curl returns <1KB or 403? ───────────► YES - Continue below │ Which browser tool to use? │ ├─ browser_subagent available? ─────────► antigravity-browser.md │ ├─ In Cursor IDE? ──────────────────────► cursor-browser.md │ ├─ Chrome debugging on :9222? ──────────► playwright-browser.md (wrapper) │ └─ No browser tool? ────────────────────► See "No Browser Available" section ``` ## Red Flags - STOP and Reconsider If you're about to: - Use browser automation when curl would work - Skip tool detection and assume a specific tool exists - Take screenshots when snapshot would provide structured data - Navigate without waiting for JS rendering **STOP** -> Check the app