browser-discovery

Detect browser tools and discover documentation on JS-rendered sites.

8|1|Updated Jul 11, 2025
One-click install
npx skills add https://github.com/ViperJuice/treesitter-chunker --skill browser-discovery-viperjuice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-discovery
Source: https://github.com/ViperJuice/treesitter-chunker/tree/main/.ai-dev-kit/skills/browser-discovery
Command: npx skills add https://github.com/ViperJuice/treesitter-chunker --skill browser-discovery-viperjuice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and use browser automation tools to discover documentation when static fetching fails or JS-rendered content is required.

Core Features & Use Cases

  • Detect and evaluate available browser tools (antigravity, Cursor, Playwright) and select the best option for the task.
  • Try curl first unless js_required is true, then perform browser-based discovery.
  • Return structured data including pages, nav_structure, and js_required for downstream processing.
  • Support a workflow and decision tree to guide discovery on dynamic sites.

Quick Start

Run browser discovery using the available tool by starting with curl and switch to the detected browser tool when JS rendering is required.

Frequently Asked Questions about browser-discovery

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

FAQPage Schema
How do I discover documentation on JS-rendered pages when curl returns insufficient data?

Browser discovery automates documentation extraction on JS-rendered pages by detecting available tools like antigravity, Cursor, or Playwright to interact with dynamic content. It tries curl first, then switches to browser automation when JS rendering is required.

What is the best way to automate documentation discovery on dynamic websites?

Automating documentation discovery on dynamic websites involves detecting browser tools like Playwright or Cursor, attempting a static fetch first, and then using browser automation to extract structured page data and navigation structures when JavaScript rendering is needed.

Does browser discovery work with Playwright and Cursor for navigating dynamic content?

Yes, browser discovery detects and evaluates available browser automation tools including Playwright, Cursor, and antigravity, selecting the best option to navigate and extract documentation from dynamic, JavaScript-rendered websites.

What structured output do I get from automating browser-based documentation discovery?

Browser-based documentation discovery outputs structured data describing discovered pages, the site's navigation structure, and a flag indicating whether JavaScript rendering was required, enabling downstream processing of the extracted content.

When should I use browser automation instead of static fetching for documentation discovery?

Use browser automation for documentation discovery when static fetching with curl fails or returns insufficient data, or when the target site requires JavaScript rendering to display its navigation structure and page content dynamically.