browser-discovery

Browser-based documentation discovery automates fetching when curl or static methods fail on JavaScript-rendered sites. It detects available tools like Playwright, applies curl-first logic, and returns structured JSON with discovered pages, navigation structure, and a rendering-required indicator.

Yes. Playwright is one of several browser tools this skill automatically detects and uses for documentation discovery. The skill selects the best available tool—Playwright, Cursor, or Antigravity—based on your environment and falls back to curl when static fetches succeed.

Browser automation handles JavaScript-rendered docs by detecting when static fetches fail, then triggering dynamic rendering to extract links and sections. The skill tries curl first for efficiency, then escalates to browser tools only when needed, returning structured output with a JS-rendering indicator.

No manual configuration required. Browser-tool detection is automatic—the skill identifies Playwright, Cursor, or Antigravity availability in your environment and selects the optimal option without setup overhead.

Curl-fallback attempts static fetches first for speed and simplicity. If curl succeeds, documentation pages are extracted immediately. Only if static fetches fail or JS rendering is detected does the skill activate browser automation for dynamic content extraction.

Structured JSON output includes discovered pages, a navigation hierarchy representing site structure, and a flag indicating whether JavaScript rendering was required. This enables reliable indexing and downstream processing of online documentation portals.